Mobile: stuck on stale "usage limit reached" reply after top-up while Extra Usage is active (desktop works)

Resolved 💬 1 comment Opened Jun 1, 2026 by xelth-com Closed Jun 4, 2026

Environment

  • Claude Code on mobile (phone) vs desktop, same account
  • Plan with usage limits; Extra Usage active at time of issue

Summary

After hitting the usage/token limit and topping it up (Extra Usage shows active), the desktop Claude Code session resumes and works normally. On mobile, responses no longer come back: prompts sent from the phone do reach the backend (confirmed — the same prompts are received and acted on in the concurrent desktop session), but the mobile client only ever renders the "usage limit reached / resets at <time>" message in reply, even though Extra Usage is active.

Steps to reproduce

  1. Use Claude Code until the usage limit is hit.
  2. Top up / have Extra Usage active.
  3. Continue on desktop → works, responses return.
  4. Send prompts from the mobile app → requests are sent (and are received server-side), but the mobile UI shows only the cached "limit reached + reset time" message; assistant responses are not displayed.

Expected

Once Extra Usage is active, the mobile client should clear the limit-reached state and render responses, matching desktop behavior.

Actual

Mobile stays stuck on the limit-reached / reset-time message; no assistant responses are rendered, despite Extra Usage being active and the backend processing the requests.

Impact

Mobile Claude Code is effectively unusable after a limit top-up; the only known workaround is to switch to desktop.

_Filed on behalf of the user (GitHub: xelth-com, mail@xelth.com)._

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗