Spinner lingers/unclear 'done' signal after response — cute verbs make it feel like Claude is still working
What happened
The Claude Code CLI spinner shows whimsical verbs like \"Perambulating...\", \"Embellishing...\", \"Cogitating...\" while Claude is processing. These verbs are genuinely charming and I like them — this is not a request to remove them.
However, there's a UX friction: when Claude's response text finishes streaming, the spinner sometimes appears to keep spinning briefly (or the terminal/CLI render doesn't clear it immediately). Combined with the verbs being action-ish (\"perambulating\" sounds active), I catch myself waiting — thinking Claude is still doing background work and I'd interrupt it if I typed a new message.
In one recent session I explicitly asked Claude to \"stop and rest\" because I thought it was still running tasks. Claude replied that it had been idle the whole time — the spinner was just leftover animation / slow clear.
Impact
Loses time on the user side: you read Claude's full response, want to ask a follow-up, but see the spinner and wait several seconds \"just to be sure\".
With auto-mode ON, this feels worse — there's a reasonable prior that Claude might be kicking off follow-up actions, so the lingering spinner reinforces that feeling.
Suggestions (pick one)
- Stronger visual \"done\" signal after the final chunk streams — e.g. change spinner to a checkmark or dim the verb text.
- Terminal-state aware: when no tool calls are pending and streaming is complete, clear spinner immediately (may already be intended — seems flaky).
- Split verbs by phase: \"Thinking...\" during reasoning, \"Running <tool>...\" during tool calls, explicit \"Done.\" frame at turn end. Keep the cute verbs but phase-specific.
Environment
- Claude Code CLI (latest Sonnet/Opus, macOS, zsh on Darwin 24.4)
- Occurs in both tool-heavy turns and simple text-only replies
Not a priority ask
The verbs are fun, keep them! Just would like a clearer signal that the turn is actually over.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗