{"version":"2.1.323","anchor":"stop-reason-list-and-stricthuman-text-check","canonical_anchor":"stop-reason-list-and-stricthuman-text-check","heading":"Named reasons for a session stopping, and a stricter check for typed input","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/stop-reason-list-and-stricthuman-text-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Named reasons for a session stopping, and a stricter check for typed input\n\nClaude Code now has a fixed list of reasons a session can stop, and its strict check for human input also requires the text to have been typed\n\n**Unclear.** It is not clear where a reader would see these stop reasons or meet the stricter typed-text check.\n\n**What**\n\nClaude Code now has a fixed list of reasons a session can stop:\n\n- `time_limit`\n\n- `server_not_responding`\n\n- `task_unknown`\n\n- `sign_in_stopped`\n\n- `access_denied`\n\n- `answer_too_large`\n\n- `other`\n\nA separate reason, `stopped_by_person`, marks a session that a person stopped.\n\nThe strict check that decides whether input came from a human is also tighter. It now also requires that the text was typed, not supplied some other way.\n\n**Why**\n\nThese appear to be stop categories for sessions that run remotely, and a narrower definition of what counts as human input.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}