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.307 ·

/clear withdraws the resume point in the conversation it leaves

After /clear, Claude Code removes any resume checkpoint from the old conversation so it no longer resumes to that point

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

/clear starts a new conversation with empty context. The previous conversation stays saved, and you can return to it with /resume. A saved conversation can hold a resume checkpoint, a marked point that resuming picks up from.

After /clear, Claude Code now looks through the saved record of the conversation it left behind. If that record holds a resume checkpoint, Claude Code adds an entry withdrawing it. If it cannot read the file, or finds no checkpoint, it notes that in its log and changes nothing.

Why

When you later go back to a cleared conversation, it should not resume to a checkpoint that is out of date.

Read from
Names in the bundle/clear/resume
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed a conversation cleared with /clear sometimes coming back when a cloud or self-hosted runner session restarted

See this entry in the whole of v2.1.307 →

Feedback