{"version":"2.1.281","anchor":"hasstandingprompt-now-only-counts-published-pending-action","canonical_anchor":"hasstandingprompt-now-only-counts-published-pending-action","heading":"hasStandingPrompt now only counts published pending actions","tier":"internal","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/hasstandingprompt-now-only-counts-published-pending-action","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### `hasStandingPrompt` now only counts published pending actions\n\nThe check for whether a prompt is waiting on you now only counts published pending actions, with one fallback case\n\n**Unclear.** The finding does not say where this check is shown to users or what they would notice.\n\n**What**\n\nClaude Code has an internal check, `hasStandingPrompt()`, that decides whether something is currently waiting for your answer. It now works like this:\n\n- A new field, `flipBackLeftToUnpublishedAsk`, is set when the session state switches to `requires_action` (needing your input) without a published pending action, and is cleared on any other state.\n\n- Only while that field is set does the check fall back to the older `hasPendingPrompt()` test.\n\n- In every other case the check requires a published pending action whose request is still pending.\n\n**Why**\n\nIn practice, a request that was never published, or has already been answered, no longer counts as a prompt waiting on you, except in the one case the new field covers.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}