Follow Discord
Sweep 09 Oct 2026 · 17:27Z Build v2.1.296 517 read Stable v2.1.287 Latest v2.1.296 Next v2.1.296 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.296 ·

Resume handles stale permission prompts in more cases; a classifier event is dropped

Resuming now handles overdue or summarized permission prompts and rate limits, records more detail on cancelled prompts, and drops a classifier event

Group of 2 You'll notice Improvements
JSON All of v2.1.296
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ResumeArea: what it touches
ImprovementsKind: in v2.1.296,
ImprovementsSection of the release

Unclear What the new handling of overdue or summarized prompts changes for someone resuming a session is not stated.

What

When you resume a session (pick up an earlier conversation), a permission prompt left open from before may be stale. A permission prompt is Claude asking whether it may use a tool. This release changes how those prompts are handled and recorded:

  • Cancel record: the record tengu_resume_stale_prompt_cancel now carries withdrawn_at, prompt_call and other diagnostic fields. Before, only the kind was sent.
  • Overdue or summarized prompts: resume logic now handles prompts that are overdue or were summarized away, as well as rate limits (orSummarizedPrompt).
  • Answered tool calls: the list of tool calls already answered (answeredToolUseIds) is now combined with an additional set.
  • Removed event: tengu_turn_end_classifier_hold was removed from an event list. Whether the feature behind it was also removed has not been checked.

Why

This is mostly behind the scenes. Resuming a conversation that was summarized, or that hit a rate limit, now covers more cases when deciding what to do with leftover permission prompts.

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 doubtWhat the new handling of overdue or summarized prompts changes for someone resuming a session is not stated.

See this entry in the whole of v2.1.296 →

Feedback