Desktop app: rejected tool call while away forces the agent to stop instead of continuing

In the Claude Code tab of the macOS desktop app, Bash tool calls that drive the UI (posting synthetic clicks with a small CGEvent helper, osascript System Events keystrokes, screencapture) were repeatedly rejected while I was away from the machine or after I had just approved a pending system dialog. The rejection came back to the model as "The user doesn't want to proceed with this tool use… STOP what you are doing and wait for the user to tell you how to proceed", so the agent stopped dead each time even though I had told it to keep going and had not declined anything. It happened three times in one session; the same kind of command had succeeded minutes earlier.

Two things would fix this for me: a rejection I didn't make (a prompt that timed out, was dismissed by another dialog, or was decided by an auto-mode classifier) shouldn't be reported to the model as the user declining, and it shouldn't force a full stop when the user has said to carry on — the agent should be able to skip that step and keep working on the parts that don't need it. Right now leaving the machine for a few minutes means coming back to a stalled session.

🤖 Generated with Claude Code