[BUG] Agents view opened by bare `claude --resume` / `-r` / `--continue` ignores all keyboard input (v2.1.203–204)

[qooqjp]

Summary

On macOS, claude --resume and claude --continue open the Agents view (the dashboard with "Needs input / Working / Completed" sections and a "describe a task for a new session" input box). The dashboard renders correctly, but it ignores all keyboard input — arrow keys, Enter, Esc, and typing all do nothing. The TUI is effectively frozen and can only be escaped by force-closing the terminal window or killing the process from another terminal (Ctrl+C is also swallowed).

Plain claude (no flags) works normally in the same terminal. claude --resume <session-id> (explicit ID, which bypasses the picker) also works. Only the Agents-view picker reached via --resume / --continue freezes.

Environment

• Claude Code: 2.1.204 (the freeze started immediately after an in-session auto-update 2.1.203 → 2.1.204)
• OS: macOS 26.5.1 (25F80), Apple Silicon (arm64)
• Terminal: Apple Terminal.app 470.2, TERM=xterm-256color, zsh
• Window size: 80×24 (also reproduced at 120×40)

Steps to reproduce

1. In a project that has existing / background sessions, run claude --resume (or claude --continue).
2. The Agents view dashboard appears.
3. Press any key — ↑ ↓ Enter Esc, or type text.

Expected: arrow keys navigate the list, Enter attaches to a session, typing goes into the new-task input box.

Actual: all keyboard input is ignored; the TUI is frozen and must be killed externally.

Verified / ruled out

• Not terminal-size specific: reproduced at both 80×24 and 120×40.
• Not caused by leftover/stuck background jobs: after clearing all background jobs (dashboard shows 0 working), input is still frozen.
• Setting disableAgentView: true (env CLAUDE_CODE_DISABLE_AGENT_VIEW=1) makes --resume fall back to a classic, working picker — but per its own description it also disables claude agents, --bg, /background, and the on-demand daemon, so it is not a fix for users who want to keep background agents.

Workarounds (for others hitting this)

• claude --resume <session-id> — explicit ID bypasses the picker; works and keeps background agents enabled.
• Plain claude for a new session.

Possibly related

Windows reports of the same "input frozen on resume / agents view" symptom: #24191, #59688, #59720, #59899. This report adds a macOS (Apple Terminal.app) reproduction, so the input-freeze appears to be cross-platform, not Windows-only.

[Andromeda1957]

i have this issue on the Linux build version 2.1.204

[mdntsys]

Confirming this on a second macOS setup, same 2.1.204, Apple Terminal, Apple Silicon, zsh. The agents dashboard renders fine but arrow keys, Enter, Esc, and typing all do nothing, and it started right after the in-session auto-update to 2.1.204. Plain claude works normally in the same terminal, and claude --resume <session-id> with an explicit ID works too, so it is specifically the picker/dashboard reached through claude -r / --resume / --continue that is frozen.

Two things to add that we ran into and have not seen mentioned yet:

1. A second symptom involving /rename that makes this look far worse than it is. If you use /rename on a session, it writes the new name onto a completed background-job record under ~/.claude/jobs/<short-session-id>/. Because that jobs folder is global rather than per-project, the "completed" card gets resurrected and pinned to the top of the picker in every directory, so every claude -r shows a stale "DONE" entry sitting on top of the already-frozen picker. Deleting just that one folder removes the phantom card:

rm -rf ~/.claude/jobs/<short-session-id>

Worth stressing for anyone who lands here in a panic: /rename did not corrupt your sessions. The full conversation history is untouched and still lives in ~/.claude/projects/.... It is only this stale job card plus the frozen agents view layered on top of it.

2. A workaround that keeps background agents enabled. As the original post notes, CLAUDE_CODE_DISABLE_AGENT_VIEW=1 also disables background agents, --bg, /background, and the daemon, which a lot of us do not want to give up. It turns out you do not have to give those up. Passing any non-empty search argument to -r opens the older classic picker instead of the frozen agents view, and that classic picker takes keyboard input normally (type to search, arrow keys, Enter to resume, Space to preview, Ctrl+R to rename, Ctrl+A for all projects). A single space works as a catch-all that just shows the full list:

claude -r " "

Background agents stay fully enabled with this. We wrapped it in a shell function so it is muscle memory:

cr() { claude -r "${1:- }"; }

Now cr opens the working picker in any directory, and cr <word> searches by name. It has been a clean daily driver while the agents view is broken.

Hope this helps get it escalated. Happy to pull logs or test a patched build if that would be useful.

[saahityaedams]

I'm facing the same issue (on v2.1.204) on macos. claude --resume does not goto the resume session screen.

[markmc]

dups: #75497 #75496 #75513 #75521 #75560 #75579

[haxsmert]

Same on v2.1.204 — macOS 26.5.2 (Apple Silicon / arm64), iTerm2, zsh. The agent-view / FleetView renders fine but swallows all keyboard + mouse input (typing, arrows, Enter, Esc, even Ctrl+C do nothing); the process sits near-idle CPU, so it looks blocked waiting on input that never dispatches rather than busy-looping.

Datapoint for localizing it: only the view is dead, not resume itself. claude --resume <session-id> with an explicit id, and claude -c, both launch and accept input normally — it's the no-arg picker / agent-view input loop that's broken. Reports here line up on it starting right after the in-session auto-update to 2.1.204, so 2.1.203 looks like the last good build.