Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.290 ·

rewind_conversation can reach summarized messages and can refuse when usage-limited

rewind_conversation gains allow_summarized_target to rewind into compacted history and refuse_if_usage_limited to decline when a usage limit is hit

Group of 2 Use it now No documentation found Improvements
JSON All of v2.1.290
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
SDKArea: what it touches
ImprovementsKind: in v2.1.290,
What probably matters to youSection of the release

Unclear What allow_summarized_target does, and which program uses these options, is not stated.

What

rewind_conversation is a request that programs driving Claude Code can send to take a conversation back to an earlier message. It accepts two new options.

  • allow_summarized_target lets the rewind aim at a message that has already been folded into a compaction summary. Compaction is when older parts of a long conversation are replaced by a shorter summary. Before, such a target gave target_not_found. Now the rewind resolves to the point just after the summary. When it still cannot find the target, it gives a more specific reason.
  • refuse_if_usage_limited checks your usage limit before rewinding. If the limit has been reached, the request is declined with usage_limited.

Why

Rewinding and retrying a turn can now work after a long conversation has been compacted, instead of failing because the original message is gone. Tools that drive Claude Code can also avoid rewinding into a turn that could not run anyway because of a usage limit.

Read from
Names in the bundlerewind_conversation
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 `allow_summarized_target` does, and which program uses these options, is not stated.

See this entry in the whole of v2.1.290 →

Feedback