{"version":"2.1.317","anchor":"session-owner-support-in-the-repl-host","canonical_anchor":"session-owner-support-in-the-repl-host","heading":"Building blocks for tracking who owns a session","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/session-owner-support-in-the-repl-host","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Building blocks for tracking who owns a session\n\nClaude Code now saves a list of session owners with the transcript and can let a session's first turn skip the check against overlapping turns\n\n**Unclear.** Whether session owners are used by any feature you can reach yet is not stated.\n\n**What**\n\nA session is one conversation with Claude Code, and its transcript is the saved record of it. Claude Code now has several pieces for tracking who owns a session:\n\n- The transcript saves a list of session owners.\n\n- A run can be started with an option that skips, for the first turn only, the check that normally stops two turns running at once.\n\n- The part of Claude Code that `\/teleport` uses now takes options, including a way to add a warning to the transcript.\n\n**Why**\n\nFor now these are building blocks. They record a session's owners alongside its transcript and let the first turn of such a session start without waiting.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}