{"version":"2.1.307","anchor":"clear-can-withdraw-a-resume-checkpoint-from-the-transcript","canonical_anchor":"clear-can-withdraw-a-resume-checkpoint-from-the-transcript","heading":"\/clear withdraws the resume point in the conversation it leaves","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/clear-can-withdraw-a-resume-checkpoint-from-the-transcript","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### `\/clear` withdraws the resume point in the conversation it leaves\n\nAfter `\/clear`, Claude Code removes any resume checkpoint from the old conversation so it no longer resumes to that point\n\n**What**\n\n`\/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.\n\nAfter `\/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.\n\n**Why**\n\nWhen you later go back to a cleared conversation, it should not resume to a checkpoint that is out of date.\n\n- Area: Sessions\n- Names: `\/clear`, `\/resume`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}