{"version":"2.1.317","anchor":"session-owner-recorded-and-persisted-in-session-metadata","canonical_anchor":"session-owner-recorded-and-persisted-in-session-metadata","heading":"Saved sessions can record which account owns them","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/session-owner-recorded-and-persisted-in-session-metadata","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Saved sessions can record which account owns them\n\nWhen a saved session names an owning account, Claude Code now restores that owner when the session is reopened\n\n**What**\n\nA session is one conversation with Claude, which can be saved and resumed later. When a saved session records an owner with an account ID, Claude Code now sets that account as the session's owner when it restores the session. The session owner is also now part of the details Claude Code keeps about each session.\n\n**Why**\n\nSessions can now carry the account they belong to through a save and a resume.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}