{"version":"2.1.265","anchor":"new-claude-code-state-files-device-mcp-consentjson-devic","canonical_anchor":"new-claude-code-state-files-device-mcp-consentjson-devic","heading":"New Claude Code state files: device-mcp-consent.json \/ device-mcp-snapshot.json","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/new-claude-code-state-files-device-mcp-consentjson-devic","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### New Claude Code state files: device-mcp-consent.json \/ device-mcp-snapshot.json\n\nTwo new state files, device-mcp-consent.json and device-mcp-snapshot.json, are now tracked and copied alongside other Claude config\n\n**What**\n\nTwo new per-user state files, `.claude\/state\/device-mcp-consent.json` and `.claude\/state\/device-mcp-snapshot.json`, have been added to the set of Claude-managed files that get special handling, alongside existing files like `settings.json` and `unattended-serving-consent.json`. They're also included in the list of paths that get scanned and copied across config directories.\n\n**Why**\n\nThis suggests Claude Code is building out a consent and state-tracking system specifically for MCP servers tied to a device, similar to the existing consent mechanism for unattended tool serving, though what specifically populates these files isn't detailed here.\n\n- Area: Elsewhere\n- Names: `device-mcp-consent.json`, `device-mcp-snapshot.json`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}