{"version":"2.1.290","anchor":"new-gate-tengu-quirky-sketch-for-always-loaded-device-mcp-to","canonical_anchor":"new-gate-tengu-quirky-sketch-for-always-loaded-device-mcp-to","heading":"A switch for special handling of always-loaded device tools","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/new-gate-tengu-quirky-sketch-for-always-loaded-device-mcp-to","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### A switch for special handling of always-loaded device tools\n\nClaude Code can now single out its device tools for special handling, under a server flag that is off unless switched on\n\n**Unclear.** What Claude Code does differently with a tool once this check passes is not settled.\n\n**What**\n\nClaude Code now has a check that picks out a fixed set of device tools when they are always loaded from a single MCP server:\n\n- `device_bash`\n\n- `device_commit_files`\n\n- `device_list_dir`\n\n- `device_request_delete_permission`\n\n- `device_stage_files`\n\n- `get_device_info`\n\n- `list_devices`\n\nThe check also requires an active marker whose model matches the model in use. Even then, the final answer comes from a server flag, `tengu_quirky_sketch`, which is off unless it is switched on remotely.\n\n**Why**\n\nThis lays the groundwork for treating these device tools differently from other tools, held back until the flag is turned on.\n\n- Flag `tengu_quirky_sketch`: Not enough to say (read for one account on one subscription tier against v2.1.290; this account: no value returned, anonymous baseline: no value returned, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}