{"version":"2.1.288","anchor":"cold-resume-clear-now-waits-for-a-queued-clear-and-finishe","canonical_anchor":"cold-resume-clear-now-waits-for-a-queued-clear-and-finishe","heading":"Resuming into a new conversation waits for a queued \/clear to apply","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/cold-resume-clear-now-waits-for-a-queued-clear-and-finishe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Resuming into a new conversation waits for a queued `\/clear` to apply\n\nWhen 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\n\n**Unclear.** When this resume path runs is not stated.\n\n**What**\n\n`\/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.\n\nIf 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.\n\n**Why**\n\nThe \"New conversation\" notice could be lost when the clear had not run yet. Claude Code now waits for the clear before adding it.\n\n- Area: Sessions\n- Names: `\/clear`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}