Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.323entry #723

Claude Code v2.1.323 ·

Named reasons for a session stopping, and a stricter check for typed input

Claude 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

Under the hood Internal Changes
JSON All of v2.1.323
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SessionsArea: what it touches
Internal ChangesKind: in v2.1.323,
Internal ChangesSection of the release

Unclear It is not clear where a reader would see these stop reasons or meet the stricter typed-text check.

What

Claude Code now has a fixed list of reasons a session can stop:

  • time_limit
  • server_not_responding
  • task_unknown
  • sign_in_stopped
  • access_denied
  • answer_too_large
  • other

A separate reason, stopped_by_person, marks a session that a person stopped.

The 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.

Why

These appear to be stop categories for sessions that run remotely, and a narrower definition of what counts as human input.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear where a reader would see these stop reasons or meet the stricter typed-text check.

See this entry in the whole of v2.1.323 →

Feedback