{"version":"2.1.314","anchor":"remote-unasked-questions-denied-for-person-only-asks","canonical_anchor":"remote-unasked-questions-denied-for-person-only-asks","heading":"Remote sessions can deny questions only a person could answer when nobody is there","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/remote-unasked-questions-denied-for-person-only-asks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Remote sessions can deny questions only a person could answer when nobody is there\n\nIn remote sessions, a permission question only a person can answer can be turned into a refusal when no person is present\n\n**What**\n\nIn sessions where `CLAUDE_CODE_REMOTE` is set, some permission questions are marked as ones only a person can answer. A permission question is Claude Code asking whether it may take an action. If no person is present to answer, Claude Code can now treat the question as a refusal instead of waiting.\n\nThere is also a new way for agents that run in the background to settle a question nobody was asked.\n\n**Why**\n\nThis changes what a remote agent can do on its own. An action that needs a person's approval is turned down rather than left waiting when nobody is there to approve it.\n\n- Area: Sessions\n- Names: `CLAUDE_CODE_REMOTE`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}