{"version":"2.1.317","anchor":"new-session-owner-login-message-and-session-owner-event","canonical_anchor":"new-session-owner-login-message-and-session-owner-event","heading":"Claude Code holds back messages in a session that belongs to another account","tier":"notice","area":"Sessions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/new-session-owner-login-message-and-session-owner-event","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Claude Code holds back messages in a session that belongs to another account\n\nIf a session belongs to another account, Claude Code sends nothing and asks you to send a message to choose which account to use\n\n**Unclear.** What causes this message to appear, and whether it is switched on for everyone, is not clear.\n\n**What**\n\nClaude Code now has a message for when the current session (one ongoing conversation) belongs to a different account from the one you are signed in with: \"This session belongs to another account, so nothing was sent. Send a message to choose which account to use.\" Claude Code also now records which account owns a session.\n\n**Why**\n\nThis keeps your messages from being sent under the wrong account when a session is owned by someone else's sign-in.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: yes"}