{"version":"2.1.281","anchor":"session-list-exposes-pending-action-for-sessions-awaiting-in","canonical_anchor":"session-list-exposes-pending-action-for-sessions-awaiting-in","heading":"Session summaries show which tool a waiting session needs approval for","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/session-list-exposes-pending-action-for-sessions-awaiting-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Session summaries show which tool a waiting session needs approval for\n\nRemote session summaries now include pending_action naming the tool a waiting session needs, and 'needs input' tracking counts only live requests\n\n**Unclear.** The finding does not say where this session list is shown to users.\n\n**What**\n\nA remote session is a Claude Code session running somewhere other than your own terminal. When one is waiting for you to act, its session summary (the short record used in session lists) now says what it is waiting on:\n\n- When the session's `worker_status` is `requires_action` and `external_metadata.pending_action` names a tool, the summary built by `th()` now includes `pending_action: { name, request_id? }`. Here `name` is the tool's name (`tool_name`) and `request_id` is included when present.\n\n- `hasStandingPrompt`, which decides whether a session counts as having a question waiting for you, now counts only published pending-action requests that are still pending. The exception is when the flip-back flag was left by an ask that was never published. Before, it was simply `requires_action && hasPendingPrompt()`.\n\n**Why**\n\nSession lists and remote views can now show which tool a session is waiting for you to approve, not just that it needs input. The stricter check means a session is less likely to keep showing 'needs input' for a request that is no longer pending."}