{"version":"2.1.300","anchor":"diskless-credential-store-for-hosted-sessions","canonical_anchor":"diskless-credential-store-for-hosted-sessions","heading":"Hosted sessions keep no device key on their machine","tier":"internal","area":"Hosted Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/diskless-credential-store-for-hosted-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Hosted sessions keep no device key on their machine\n\nHosted claude-code-server sessions now use a key store that never saves a device key to disk\n\n**What**\n\nA device key is a credential Claude Code can keep on a machine to identify it. A new key store saves nothing. It is used for hosted sessions run by claude-code-server, meaning Claude Code running as a service on someone else's machine.\n\nIf something tries to lock that store, Claude Code stops with the message \"This hosted session (claude-code-server) keeps no device key on its machine\".\n\n**Why**\n\nHosted sessions do not leave a device key behind on the machine they run on.\n\n- Area: Hosted Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}