{"version":"2.1.321","anchor":"remote-control-enable-bearer-account-ownership-tracking-for","canonical_anchor":"remote-control-enable-bearer-account-ownership-tracking-for","heading":"Turning on Remote Control can record a bearer-token account as the transcript owner","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/remote-control-enable-bearer-account-ownership-tracking-for","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Turning on Remote Control can record a bearer-token account as the transcript owner\n\nWhen Remote Control is turned on, an account signed in with a bearer token can now be recorded as the owner of the session transcript\n\n**Unclear.** It is not clear when Claude Code uses a bearer-token account instead of your login.\n\n**What**\n\nClaude Code keeps a record of each session's transcript, the written log of the conversation. That record notes which account owns it. Before, the owner always came from your login. When you turn on Remote Control, the owner can now be an account signed in with a bearer token. A bearer token is a credential sent with each request in place of a normal login. Claude Code also takes that account into account when deciding whether the signed-in identity has changed.\n\n**Why**\n\nThe owner decides which account keeps the transcript record, or marks it removed, when Remote Control is switched on or off.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}