{"version":"2.1.323","anchor":"session-sign-inprofile-persistence-on-resume","canonical_anchor":"session-sign-inprofile-persistence-on-resume","heading":"Resuming a session now checks you are signed in the same way as before","tier":"notice","area":"Resume","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/session-sign-inprofile-persistence-on-resume","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Resuming a session now checks you are signed in the same way as before\n\nClaude Code now records which sign-in each session used and refuses to resume it under a different one\n\n**What**\n\nEach session now keeps a record of which sign-in it was started with. A session is one conversation with Claude Code. The sign-in can be one of these:\n\n- a profile\n\n- an API key\n\n- a token\n\n- a workload identity\n\nIf you try to resume a session with `--resume` under a different sign-in, Claude Code refuses. It tells you that the session was on another sign-in and asks you to run `claude --resume` the same way you started it. If Claude Code cannot update which profile the session belongs to, it says so and leaves the session where it is.\n\n**Why**\n\nA resume that worked before can now be refused when your current sign-in does not match the one the session started with. Start Claude Code with the same account, key or profile you first used.\n\n- Area: Resume\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}