{"version":"2.1.317","anchor":"resume-asks-about-session-owner-when-a-different-account-own","canonical_anchor":"resume-asks-about-session-owner-when-a-different-account-own","heading":"Resuming a session can now check which account owns it","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/resume-asks-about-session-owner-when-a-different-account-own","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Resuming a session can now check which account owns it\n\nResuming a session now reads a recorded session owner and, when it asks about the owner, skips the stale-resume prompt and does not reconnect Remote Control\n\n**Unclear.** It is not settled exactly when Claude Code decides to ask about the session owner, so it is unclear which resumes this affects.\n\n**What**\n\nA session is one conversation with Claude Code, and resuming picks it back up later. Saved sessions can now carry a session-owner record that names the account and organization the session belongs to.\n\nWhen Claude Code decides it needs to ask about the session's owner while resuming, it now:\n\n- Skips the prompt that warns about resuming an old session\n\n- Does not switch Remote Control back on automatically, even if the session used it before\n\n- Cancels the current turn once login finishes\n\nBefore, resuming always turned Remote Control back on when the session had used it, and always showed the old-session prompt when it applied.\n\n**Why**\n\nResuming a session that was recorded under a different account now behaves differently from resuming one of your own.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}