{"version":"2.1.323","anchor":"network-permission-prompt-now-reports-terminal-only-asks-to","canonical_anchor":"network-permission-prompt-now-reports-terminal-only-asks-to","heading":"Network permission prompts that only the terminal can answer are reported","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/network-permission-prompt-now-reports-terminal-only-asks-to","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Network permission prompts that only the terminal can answer are reported\n\nNetwork access prompts that can only be answered in the terminal are now reported to connected clients, and timeout records are fixed\n\n**What**\n\nClaude Code can ask your permission before Claude connects to a network address. In some cases that question can only be answered in the terminal, not from a connected client such as a remote control session. Claude Code now tells the connected client about such a question, and withdraws the notice once the question is answered or closed.\n\nA bug is also fixed in what happens when the prompt times out and in how an allowed answer is handled. Claude Code used to check for a cancelled answer before the answer had arrived, so that check could never match. It now waits for the answer first.\n\n**Why**\n\nRemote and connected clients can now see that a question is waiting in the terminal instead of looking stuck. The records made when such a prompt times out are now correct.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}