You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ResumeArea: what it touches
ImprovementsKind: in v2.1.323,
ImprovementsSection of the release
What
Each 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:
a profile
an API key
a token
a workload identity
If 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.
Why
A 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.
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeChanged claude rm and the agents view to say a session is removed from the list, not deleted; claude rm help says the conversation is kept…
