Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Spinner lingers/unclear 'done' signal after response — cute verbs make it feel like Claude is still working [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52759•Fetched 2026-04-24 10:40:19
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
TuyetPhanTSTuyetPhanTS
Participants
github-actions[bot]github-actions[bot]TuyetPhanTSTuyetPhanTS
Timeline (top)
labeled ×3commented ×1

Root Cause

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.

RAW_BUFFERClick to expand / collapse

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)

  1. Stronger visual "done" signal after the final chunk streams — e.g. change spinner to a checkmark or dim the verb text.
  2. Terminal-state aware: when no tool calls are pending and streaming is complete, clear spinner immediately (may already be intended — seems flaky).
  3. 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.

extent analysis

TL;DR

Implement a stronger visual "done" signal after the final chunk streams to indicate that Claude has finished processing.

Guidance

  • Consider changing the spinner to a checkmark or dimming the verb text after the final response chunk to provide a clear visual cue.
  • Investigate the possibility of making the terminal-state aware, clearing the spinner immediately when no tool calls are pending and streaming is complete.
  • Evaluate the feasibility of splitting verbs by phase, using different verbs for different stages of processing, such as "Thinking..." or "Running <tool>..." to provide more context.

Example

No code snippet is provided as the issue does not imply a specific code change, but rather a design or implementation adjustment.

Notes

The solution may depend on the specific implementation of the Claude Code CLI and its rendering mechanism. The suggested changes aim to improve the user experience by providing a clearer signal that the processing has completed.

Recommendation

Apply a workaround, such as implementing a stronger visual "done" signal, to address the UX friction caused by the lingering spinner. This approach allows for a more explicit indication of completion, reducing the likelihood of users waiting unnecessarily.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#database connection#vector store#embedding generation#cache error#pipeline error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Spinner lingers/unclear 'done' signal after response — cute verbs make it feel like Claude is still working [1 comments, 2 participants]