Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.299 ·

Resumed sessions handle a waiting permission answer more carefully

When a session resumes with a permission question still open, Claude Code now gives more specific reasons for not reusing an earlier answer

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

A permission question that was waiting for an answer when a session stopped can be picked up again when the session resumes. Claude Code sometimes reuses an answer given earlier (an inherited answer). It now records more specific reasons when it decides not to reuse one, for example when the answer could not be read, belonged to a different tool, did not match the question, arrived after the wait ran out, or when the feature was not switched on.

When Claude Code rescues a turn that was interrupted, it now also holds back task notices (status messages from background tasks) along with the other messages it already held back. Its usage reports for this step also note whether the ending was held back and how many retired entries were in the conversation.

Why

Resumed remote sessions treat a pending permission question more cautiously, so an old or mismatched answer is less likely to be applied to the wrong request.

See this entry in the whole of v2.1.299 →

Feedback