Follow Discord
Sweep 02 Oct 2026 · 18:55Z Build v2.1.288 509 read Stable v2.1.285 Latest v2.1.288 Next v2.1.288 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.288 ·

Resuming into a new conversation waits for a queued /clear to apply

When resuming starts a fresh conversation, Claude Code waits for a queued /clear before linking back to the old one, or reports that it never applied

You'll notice Bug Fixes
JSON All of v2.1.288
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
SessionsArea: what it touches
Bug FixesKind: in v2.1.288,
Bug FixesSection of the release
What

/clear starts a new conversation with empty context. In one path, Claude Code resumes a session and starts a new conversation with /clear. Claude Code now checks whether that /clear was queued behind other work.

If it was queued, Claude Code waits until the clear actually applies. Only then does it add the note pointing back to the previous conversation. If the clear never applies, Claude Code reports that it was not applied. Before, it checked only once, straight after submitting the command.

Why

The "New conversation" notice could be lost when the clear had not run yet. Claude Code now waits for the clear before adding it.

Read from
Names in the bundle/clear
What the documentation says
/clear Troubleshooting modified, high confidence If the error comes back after a `/clear`, run [`/context`](/docs/en/debug-your-config) and compare the `Messages` row with the rows above it: see the edit
/clear Orchestrate teams of Claude Code sessions modified, high confidence * `/compact`, `/clear`, and `/rewind` act on the lead's conversation, so Claude Code asks you to confirm before running one of them from this view. see the edit
/clear Create custom subagents modified, high confidence * `/compact`, `/clear`, and `/rewind` act on the main conversation, so Claude Code asks you to confirm before running one of them from this view. see the edit
/clear Draw in the interface with a mod modified, high confidence If your mod copies a saved value from `$.store` into `$.state` at `session.start`, it has to copy it again after `/clear`, `/resume`, or `/branch`. Those commands reset every `$.state` value to its default, and `session.start` doesn't fire… see the edit
/clear Test a mod modified, high confidence Each test starts with every `$.state` value at its default, which is how `/clear` leaves them. To test what your mod does next, skip `session.start`, fire `classic.SessionStart` with `source: 'clear'`, and check what your mod draws. see the edit
/clear Escalate hard decisions with the advisor tool modified, high confidence * If the API refuses the pairing of an advisor that Claude Code attached, Claude Code resends that request without the advisor. The conversation continues without one, so you see no error and get no advisor calls. If you then pick a differ… see the edit
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 doubtWhen this resume path runs is not stated.
Anthropic's documentation agrees/clear on Troubleshooting

See this entry in the whole of v2.1.288 →

Feedback