Claude Code's usage-limit auto-continue doesn't run in Remote Control sessions. Hooks resume them.
TL;DR Claude Code's built-in auto-continue (autoContinueAtUsageLimit, on by default: it waits for the usage limit to reset, then carries on) doesn't start in Remote Control sessions. As far as I found, only the interactive-mode docs page says so, and nothing on screen tells you.
This article discusses a known issue with Claude Code's auto-continue feature in Remote Control sessions and provides a solution using custom hooks to manage session resumption and usage limits.
What happened
The article describes a problem where Claude Code's built-in auto-continue feature does not function in Remote Control sessions. The author provides a solution using custom hooks and a script to manage session resumption and usage limits, including tracking weekly usage and resuming sessions after the 5-hour reset.
Why it matters
This matters to AI developers and users who rely on Claude Code for automation and need reliable session management. The solution ensures that sessions resume automatically after usage limits reset and prevents overuse by blocking auto-continue at 85% weekly usage.
- Claude Code's auto-continue feature does not work in Remote Control sessions.
- Custom hooks and a script can be used to manage session resumption and usage limits.
- Weekly usage tracking and blocking auto-continue at 85% usage are essential for effective session management.
- The script includes logic to delay resuming sessions after the 5-hour reset.
- The solution is tested with unit tests and real sessions.
The bigger picture
The solution ensures that users can manage their Claude Code sessions effectively, preventing overuse and ensuring continuity after usage limits reset. It provides a reliable way to automate session resumption and usage tracking.
The article provides a detailed solution to a known issue with Claude Code's auto-continue feature in Remote Control sessions. By using custom hooks and a script, users can effectively manage session resumption and usage limits, ensuring reliable and efficient use of the tool.
Technical details
- Hooks like Stop, StopFailure, UserPromptSubmit, and PreToolUse are used to manage session behavior.
- The script tracks usage limits using JSON data from the statusline.
- The script uses Python 3.9 or later and relies on tools like jq and terminal-notifier.
- The script includes logic to delay resuming sessions after the 5-hour reset and to block auto-continue at 85% weekly usage.
FAQ
Why doesn't the auto-continue feature work in Remote Control sessions?
The built-in auto-continue feature in Claude Code does not start in Remote Control sessions, as documented in the interactive mode but not explicitly mentioned in the Remote Control page.
How can I resume sessions after the 5-hour usage limit resets?
A custom script with hooks like Stop and StopFailure can be used to wait for the 5-hour reset and resume the session automatically.
How does the script track weekly usage?
The script reads usage data from the statusline and tracks weekly usage, blocking auto-continue at 85% usage.
What tools are required to implement the solution?
The solution requires Python 3.9 or later, jq, and terminal-notifier for notifications.
Is the solution tested with real sessions?
The solution is tested with unit tests and real sessions, though some edge cases like real 5-hour resets and rate_limit StopFailure payloads are not tested live.
This summary and analysis were generated with AI from the original article and may contain errors. Read the original for the full story.
Read the full story
Originally published by Dev.to AI on Oct 4, 2026.
Comments
Sign in to join the discussion.