[BUG] Agent mode status shows "working" during permission prompts instead of "waiting for input"

Status Fixed / completed
Reported on v2.1.141
Maintainer reply ✓ Yes — bogini
Activity 4 comments · opened May 14, 2026 · closed May 27, 2026
💡 Likely answer: A maintainer (bogini, collaborator) responded on this thread — see the highlighted reply below.

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

In agent mode, when a permission prompt appears (e.g. file read
permissions at session start, or MCP tool approval mid-session),
the session status in the agent view stays "working" instead of
updating to indicate it's waiting for user input.

The session IS showing the permission prompt correctly — this is
purely a status indicator issue. The prompt can be answered
normally; it's just not obvious the session is blocked.

Note: there are cases where the session correctly shows
"waiting for user input" — so the state exists. It's unclear
what determines which state is shown; we suspect it may be
that permission prompts fire mid-turn before the UI gets the
signal to flip state, but this is a guess.

What Should Happen?

Session should appear in "Needs input"

Error Messages/Logs

Steps to Reproduce

  1. Open an agent mode session
  2. Trigger a permission prompt (e.g. session start with

file read permissions pending, or invoke an MCP tool
that hasn't been approved yet)

  1. Observe: session status remains "working" while permission

prompt is displayed waiting for answer

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.141

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

<img width="2000" height="702" alt="Image" src="https://github.com/user-attachments/assets/ce00104f-6923-4e39-8aa7-517514cb7ca9" />

possibly related issue: #56860 (same class — status indicator stuck — but different scenario)

View original on GitHub ↗

4 Comments

github-actions[bot] · 3 months ago

Found 1 possible duplicate issue:

  1. https://github.com/anthropics/claude-code/issues/50665

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

ReutFarkash · 3 months ago

Not a duplicate of #50665. That issue covers Claude being genuinely idle with a stuck spinner and an unresponsive stop button. This issue is specifically about permission prompts: the prompt appears correctly and can be answered normally, but the session status in the agent view stays "working" instead of updating to "needs input."

Pattern observed across multiple cases:

  • MCP tool permission prompt → stays "working" ❌ (screenshot attached)
  • Read file permission prompt → stays "working" ❌ (confirmed, multiple instances)
  • Edit/Write file permission ("do you want to overwrite X?") → correctly shows "Needs input" ✅ (screenshot attached)

This suggests the bug is scoped to read and MCP tool permission prompts. Write/edit prompts appear to go through a different flow that correctly updates the status indicator.

The two issues may share a root cause in the UI state machine, but the trigger conditions are different.

<img width="2000" height="702" alt="Image" src="https://github.com/user-attachments/assets/b1961e4e-a31a-4552-a617-11289a7f7de4" />

<img width="880" height="155" alt="Image" src="https://github.com/user-attachments/assets/082bb908-4b45-4c21-92a8-65d53ef617e7" />

bogini collaborator · 3 months ago

Addressed by a merged fix. Please reopen with a fresh repro if you still see this on a current version.

github-actions[bot] · 1 month ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.