{"version":"2.1.323","anchor":"resume-after-crash-warns-about-anthropic-profile","canonical_anchor":"resume-after-crash-warns-about-anthropic-profile","heading":"A crashed session that was not restarted now explains how to resume it","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/resume-after-crash-warns-about-anthropic-profile","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### A crashed session that was not restarted now explains how to resume it\n\nIf a crashed session is not restarted because that could change its profile, Claude Code says to resume it the same way you started it\n\n**What**\n\nClaude Code now shows a message when a session crashed and was not restarted automatically. It explains that restarting could have changed which profile the session uses. A profile here means the set of credentials Claude Code signs in with.\n\nThe message tells you to run `claude --resume` the same way you started the session: with the same launcher, or with the same `ANTHROPIC_PROFILE` value.\n\n**Why**\n\nIt gives you a clear way to get back into the crashed session without it quietly switching to a different account or profile.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}