{"version":"2.1.283","anchor":"remote-control-attach-can-ask-for-device-mcp-consent","canonical_anchor":"remote-control-attach-can-ask-for-device-mcp-consent","heading":"Attaching a remote-control session can ask your consent for device MCP servers","tier":"notice","area":"Remote Control","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/remote-control-attach-can-ask-for-device-mcp-consent","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Attaching a remote-control session can ask your consent for device MCP servers\n\nWhen a session is attached through remote control, Claude Code can now ask for your consent about MCP servers on the host device\n\n**Unclear.** What the remote switch falls back to when the server sends nothing is not known.\n\n**What**\n\nRemote control lets a Claude Code session running on one machine be driven from somewhere else. When a session is attached this way, Claude Code can now ask for your consent about MCP servers on the host device. MCP servers are add-on programs that give Claude extra tools. Before, no such consent prompt existed. The prompt appears only when a remote switch for hosted dialogs is on. The flag server has returned on for this site's account.\n\n**Why**\n\nThis puts a consent step in front of MCP servers on your own machine before an attached session can use them.\n\n- Flag `tengu_violin_chinrest`: Gate removed from the code (read for one account on one subscription tier against v2.1.283; this account: on, anonymous baseline: on, compiled default: not a boolean we can read) 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: Remote Control\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}