{"version":"2.1.323","anchor":"ccr-tool-calls-put-back-after-refusal-are-answered-with-tai","canonical_anchor":"ccr-tool-calls-put-back-after-refusal-are-answered-with-tai","heading":"Remote sessions explain more clearly why a held-back action did not run","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/ccr-tool-calls-put-back-after-refusal-are-answered-with-tai","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Remote sessions explain more clearly why a held-back action did not run\n\nActions held behind an unanswered permission prompt in a remote session now get specific messages, such as asking you to answer it in the terminal\n\n**What**\n\nIn a remote session, Claude may ask to run several actions at once, such as reading a file or running a command. If some of these are stuck behind a permission prompt and never sent, Claude Code now answers each with a message that fits the case. Before, they all got the same generic message.\n\nOne such message is \"Answer the permission prompt in the terminal to continue\". Claude Code also records how many actions were held back this way, and two new labels describe what a session is waiting on: a permission prompt in the terminal, and an offer to send work to a project through remote control.\n\n**Why**\n\nWhen a remote session stops, you get clearer guidance about what you need to do to let it continue.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}