{"version":"2.1.312","anchor":"remote-permission-requests-for-mcp-skills-are-not-shown-or-a","canonical_anchor":"remote-permission-requests-for-mcp-skills-are-not-shown-or-a","heading":"Remote sessions leave unanswerable prompts open and warn when a question is not shown","tier":"notice","area":"Remote Control","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/remote-permission-requests-for-mcp-skills-are-not-shown-or-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Remote sessions leave unanswerable prompts open and warn when a question is not shown\n\nRemote sessions now ignore MCP skill permission requests they cannot answer and add a transcript warning when a question dialog is not shown\n\n**What**\n\nIn remote and thin-client sessions, the Claude Code you are looking at is connected to work running somewhere else. Two changes cover prompts that this copy cannot show.\n\n- MCP skill permission requests: a `can_use_tool` request is how Claude asks permission before using a tool. Requests with `tool_kind` `mcp_skill`, or with an `mcp_skill` field, are now neither shown nor answered. Claude Code logs that 'this version of Claude Code cannot answer a request of its kind' and leaves the request open so another device can answer it. Before, every `can_use_tool` request appeared as a permission prompt.\n\n- Hidden questions: two session hooks gained an `onAskNotShown` callback. When a question prompt is not shown, it adds a warning message to the conversation transcript.\n\n**Why**\n\nA request this copy cannot answer stays open for another device instead of being handled wrongly here. The transcript warning tells you that a question was waiting but could not be shown, so a stalled session is easier to understand.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}