Claude Autocontinue — Development skill for Claude Code

claude-autocontinue

[](https://github.com/prezis/claude-autocontinue/actions/workflows/ci.yml) [](LICENSE)

A zero-dependency bash script that watches your tmux panes and automatically types `continue` into Claude Code sessions when their rate limit resets.

One file. No daemon. No config. Runs in any tmux pane.

$ claude-autocontinue &
[07:20:10] claude-autocontinue 1.1.0 starting
[07:20:10] poll=300s cooldown=60s server-cooldown=120s scrollback=200 tail=30
[07:20:15] sudo (%5): rate-limited, resets in 54m (2am)
[07:20:15]   sleeping 3270s until reset
[08:14:47] sudo (%5): reset time (2am) passed — sending continue
[08:14:47] sudo (%5): sending continue
[09:31:02] fibo (%7): server rate-limit (transient) — sending continue
[09:31:02] fibo (%7): sending continue

The problem

When you run Claude Code heavily — especially across several parallel tmux panes — you hit one of two distinct rate-limit screens that both stall the session until you manually type `continue`:

**1. Personal usage limit** (resets at a known time):

You've hit your limit · resets 2am (Europe/London)
/extra-usage to finish what you're working on.

**2. Transient server rate limit** (Anthropic backend overload, no reset time):

API Error: Server is temporarily limiting requests (not your usage limit) · Rate limited

You then have to remember to come back later (or right now) and type `continue`. If you have six Claude sessions in six panes, that's six manual resumes for either failure mode.

The approach

• Polls every tmux pane every 5 minutes. Uses tmux list-panes -a so every session is covered, not just the current one.
• Detects Claude Code by TUI signature, not window name. The /rename command inside Claude Code changes the pane title, not the tmux window name — so filtering by window name