{"version":"2.1.280","anchor":"sessionrecord-remote-capability-added","canonical_anchor":"new-sessionrecord-capability-flag-default-off","heading":"New sessionRecord capability flag","tier":"soon","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/sessionrecord-remote-capability-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New sessionRecord capability flag\n\nRemote session negotiation gains a new sessionRecord capability flag, off by default\n\n**Unclear.** What sessionRecord actually does for the user (e.g. recording session activity) is not stated, only that it gates behavior.\n\n**What**\n\nThe capability map used in remote\/session negotiation gains a new `sessionRecord` entry, alongside existing entries like `controlChannel`, `modelCatalog`, `setPermissionMode`, `fanout`, `presence`, `catchupReplay`, `bashExec`, and `fileRead`. It defaults to `false`.\n\nThe flag is read in two places: an origin\/mode tracking effect and an internal remote-transport check, and both reads are further gated by a call to `vs()`.\n\n**Why**\n\nThis lets Claude Code check whether a remote session supports recording before turning related behavior on. Because the flag defaults to off, it has no effect on existing sessions until it is explicitly enabled.\n\n- Area: Remote Control\n- Names: `sessionRecord`\n- Tier: Nothing to try yet\n- Useful: 4\/5\n- Signal: 4\/5"}