[Bug]: (Does not affect normal use) Claude Code usage status stuck on "Refreshing sign-in" and does not update

Summary

Claude Code (CC) itself still works in the terminal, but Orca’s Claude usage / status-bar tracking sometimes fails to refresh. The status UI gets stuck on “Refreshing sign-in” and never recovers to live usage numbers.

Reporter confirmation: CC is usable in-terminal; the problem is specifically that usage status cannot refresh.

Environment

Orca version: 1.4.137
OS: macOS 15.7.7
Hardware: Apple M2 Pro
Claude Code version: 2.1.208

What happened

Claude usage / rate-limit status does not update in Orca.
Opening the Claude account / status UI shows a persistent Refreshing sign-in state:
- Status label: Refreshing sign-in
- Message: Claude sign-in is being refreshed. Agent sessions may still be signed in.
- Account selector shows Claude Account → System default
Claude Code sessions in the terminal continue to work (agent is signed in and usable).
Status remains stuck in this state rather than completing the refresh and showing usage percentages.

Expected behavior

Claude usage status refreshes successfully (auto or manual).
Status bar / account UI shows current usage after refresh.
Transient credential refresh should not leave the UI stuck indefinitely while agent sessions remain signed in and working.

Actual behavior

Usage tracking does not update.
UI remains stuck on Refreshing sign-in.
Terminal Claude Code continues to work, so this looks like a usage-fetch / sign-in-refresh orchestration problem rather than a full logout.

Screenshots

(Attached in follow-up comments if not inline.)

The stuck state shows:

Claude popover: Refreshing sign-in
Footer/status chip: ⚠ Refreshing sign-in
Message about agent sessions still being signed in

Notes / likely code area

Status copy for this state is mapped in src/renderer/src/components/status-bar/usage-error-copy.ts for Claude usageMetadata.failureKind values:

stale-token
refreshable-credentials-without-token
delegated-refresh-required

Those map to the exact user-visible strings:

label: Refreshing sign-in
detail: Claude sign-in is being refreshed. Agent sessions may still be signed in.

Related refresh/auth paths:

src/main/rate-limits/claude-fetcher.ts
src/main/rate-limits/claude-usage-error-classification.ts
src/main/claude-accounts/oauth-refresh.ts
src/main/claude-accounts/live-pty-gate.ts

Possible failure mode: delegated/stale-token refresh never completes (or never clears the failure kind), so usage polling keeps presenting “Refreshing sign-in” even though live Claude terminals remain authenticated.

Related (not duplicates)

Prior usage-refresh bugs that were closed after older versions:

[Bug]: Claude status bar shows "⚠ Refresh failed" after updating 1.4.65 → 1.4.68, auto-refresh stops #5355 — “Refresh failed” after update (auth path)
[Bug]: Usage status bar stops auto-refreshing after an update relaunch (focus-gated poll), separate from the #5355 auth path #5627 — usage pills stop auto-refreshing after relaunch (focus-gated poll)
[Bug]: Claude Usage Broken on Latest Update #5809 — Claude usage broken on update

This report is on 1.4.137 with a different stuck UI string (Refreshing sign-in) and confirmed working terminal CC.

Ask

Please investigate why Claude usage refresh can remain stuck in the “Refreshing sign-in” / recoverable-auth path while terminal sessions keep working, and restore reliable usage status updates.

Screenshots

Stuck on "Refreshing sign-in"

Report context (Orca 1.4.137 / macOS 15.7.7 M2 Pro / Claude Code 2.1.208)

Source gist: https://gist.github.com/AmethystLiang/9022434bb7e76ae0008dcbcad459f128

🤖 Agent handoff — reproduction kit

Status: REPRODUCED · GitHub label has_repro
Writeup (branch): docs/bug-reproductions/8974.md
Branch with tests + docs: nwparker/bug-repro-handoffs

Summary

Claude Code works in-terminal, but usage UI stays on Refreshing sign-in and never shows live percentages.

Automated re-run

git fetch origin nwparker/bug-repro-handoffs
git checkout nwparker/bug-repro-handoffs
# or: git worktree add /tmp/orca-repro-8974 origin/nwparker/bug-repro-handoffs

pnpm exec vitest run --config config/vitest.config.ts src/renderer/src/components/status-bar/repro-8974-refreshing-sign-in-stuck.test.ts

Code / evidence files

src/renderer/src/components/status-bar/repro-8974-refreshing-sign-in-stuck.test.ts

How another agent should use this

Check out nwparker/bug-repro-handoffs (or cherry-pick the repro-* test for this issue).
Run the command(s) above — green documents the bug (or cannot_repro proves current tree does not show it).
Implement the fix on a new branch from main; keep/adapt the repro test as a regression test that should flip behavior or stay as a guard.
Open a PR with: Description, Evidence, ELI5, User-regression-tradeoffs.

Posted by bug-repro orchestration so work is not trapped in a local worktree only.

Taking a focused pass on this from the has_repro handoff.

Plan: keep the short-lived “Refreshing sign-in” copy for in-flight Claude usage OAuth repair, but stamp a stable refreshingSinceMs across repeated stale-token / refreshable-credentials-without-token / delegated-refresh-required failures and escalate the status-bar/roster copy (and surface a re-auth CTA) once the refresh has been stuck past a short timeout — so the chip cannot sit on “Refreshing…” indefinitely while the terminal agent remains usable.

Will open a PR shortly.

Status — PR open

Focused fix for the stuck “Refreshing sign-in” chip (normal use unaffected; usage still recovers when OAuth repair works):

#10060

Behavior

Keep the short-lived “Refreshing sign-in” copy while Claude usage OAuth repair is in flight
If it stays stuck for ~2 minutes, escalate to “Sign-in needs refresh” so the bar doesn’t lie forever
Doesn’t interrupt a healthy terminal Claude session

Happy to adjust the timeout or copy if maintainers prefer a different threshold.

fix(status-bar): escalate stuck Claude "Refreshing sign-in" after tim…

Not sure if it needs another issue (or add another label os:linux) but it has been some time where it shows Refreshing sign-in on Linux too.
As title says, it does not affect Orca's usage.

Thanks for reporting this on Linux as well. That extends the stuck “Refreshing sign-in” status beyond the macOS report; the terminal remains usable, so this points to the usage-status refresh path.

Could you share the Orca version/build, Linux distribution and version, Claude Code version, and whether the status remains stuck after restarting Orca or re-authenticating? Please omit tokens and configuration files; version details and the visible status are enough.

My Claude subscription stopped yesterday (payment issue). I updated it and needed to re-log everywhere with it.
Now Orca finds it back so I don't have this issue anymore.

Before I always used the latest Orca build (when the update pop up appears, I update it) + Ubuntu 26.04.1 LTS (no WSL) + one of the latest Claude version (updated it today 😆 so don't remember).
Quitting the software does not change anything. Haven't tried to uninstall and reinstall.

Thanks for the follow-up. I’m glad restoring the Claude subscription and signing in again cleared the status. The Ubuntu 26.04.1 LTS details are useful context; this can stay in the existing issue, so there’s no need for a duplicate. Since the symptom cleared after re-authentication, I won’t mark it as a Linux-specific defect on this report alone. If it returns while the subscription is valid, please share the Orca build and Claude Code version from that time.

Navigation Menu

Repository navigation

[Bug]: (Does not affect normal use) Claude Code usage status stuck on "Refreshing sign-in" and does not update #8974

Summary

Environment

What happened

Expected behavior

Actual behavior

Screenshots

Notes / likely code area

Related (not duplicates)

Ask