claude-code - 💡(How to fix) Fix [BUG] Remote control doesn't work after you hit your limit [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

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#51999Fetched 2026-04-23 07:39:16
View on GitHub
Comments
2
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
labeled ×3commented ×2

Error Message

Error Messages/Logs

Code Example

No errors, just gets stuck.
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

  1. Start claude code CLI.
  2. Start remote control.
  3. Work from phone until I hit the plan limit
  4. The CLI stucks on "You've hit your limit · resets 4am (America/Montevideo)" and doesn't accepts any more messages from the phone, even if I send the messages AFTER the reset time.
  5. Need to go to the CLI on my computer to get it unstuck.
  6. It accepts the last message sent from mobile now.

This can't happen. The whole idea of remote control is to NOT use the CLI physically seated in the computer.

What Should Happen?

CLI shouldn't stuck and it should accept messages from mobile if the reset time has passed (4AM in my case)

Error Messages/Logs

No errors, just gets stuck.

Steps to Reproduce

Explained in the bug description.

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

No response

Claude Code Version

2.1.117

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

I'm on Linux Mint using xfce4-terminal

extent analysis

TL;DR

The issue can be potentially resolved by implementing a mechanism to automatically refresh or reset the CLI after the plan limit reset time, allowing it to accept new messages from the mobile device.

Guidance

  • Investigate the Claude Code CLI implementation to determine why it doesn't automatically reset or refresh after the plan limit reset time, potentially due to a missing timer or scheduling mechanism.
  • Verify if the Anthropic API provides any callbacks or notifications when the plan limit is reset, which could be used to trigger a refresh of the CLI.
  • Consider implementing a workaround, such as a periodic refresh or restart of the CLI, to ensure it remains functional after the plan limit reset time.
  • Review the CLI's handling of messages received after the plan limit reset time to ensure it correctly processes and accepts them.

Example

No code example is provided due to the lack of specific implementation details in the issue.

Notes

The solution may depend on the internal implementation of the Claude Code CLI and the Anthropic API, which are not fully described in the issue. Additional information about the API and CLI implementation may be necessary to provide a complete solution.

Recommendation

Apply a workaround, such as a periodic refresh or restart of the CLI, to ensure it remains functional after the plan limit reset time, as the root cause of the issue is not immediately clear and may require further investigation.

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…

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 [BUG] Remote control doesn't work after you hit your limit [2 comments, 2 participants]