{"version":"2.1.299","anchor":"device-attested-seed-signing-for-permission-mode-at-session","canonical_anchor":"device-attested-seed-signing-for-permission-mode-at-session","heading":"Remote sessions sign the starting permission mode with a device key","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/device-attested-seed-signing-for-permission-mode-at-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Remote sessions sign the starting permission mode with a device key\n\nWhen a remote session is created, its starting permission mode is now signed with a key on your device so it cannot easily be faked\n\n**Unclear.** Whether this signing is switched on for every remote session is not stated.\n\n**What**\n\nA permission mode sets how freely Claude Code may act without asking you. When a remote session (one that runs on a server instead of your own computer) is created, Claude Code now signs the instruction that sets its starting permission mode, using a key held on your device. If signing fails, the permission mode is still sent, just without a signature.\n\n**Why**\n\nA signed starting mode is harder for anyone else to forge, so a remote session is less likely to start with permissions you did not choose.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}