Unsnooze

Automatically resume every limit-stopped AI coding session when its usage limit resets.

Website · Documentation · Changelog · Feedback

Claude Code · Codex CLI · Grok · Qwen · Kimi · OpenCode · Antigravity · Cursor — when they hit the 5-hour or weekly usage limit ("You've hit your usage limit"), your session just… stops. unsnooze auto-resumes them: it tracks every limit-stopped session across all your projects and wakes each one up the moment the usage limit resets — in tmux, Zellij, herdr or cmux, and on macOS, Linux and Windows, with or without a terminal multiplexer.

npm install -g unsnooze && unsnooze setup

Why unsnooze

Overnight and long-running agent work dies at the 5-hour / weekly limit, and every existing tool solves only a slice of it:

	unsnooze	claude-auto-retry	autoclaude	hydra
Multi-CLI (Claude · Codex · Grok · Qwen · Kimi · OpenCode · Antigravity · Cursor)	✅	❌ Claude only	❌ Claude only	partial
GUI sessions (VS Code ext, desktop apps)	✅ watcher daemon	❌	❌	❌
Waits for reset & resumes the same session	✅	✅	✅	❌ switches provider
All sessions at once (shared ledger + one daemon)	✅	❌ one pane	✅	✅
Revives sessions whose pane/process is gone	✅ --resume <id>	❌	❌	❌
Survives laptop sleep & weekly-scale waits	✅ epoch polling	partial	partial	n/a
Settings + first-run wizard	✅	❌	❌	❌

Quick start

npm install -g unsnooze
unsnooze setup      # pick agents; installs shell wrappers + the Claude hook

Then use claude, codex and the rest exactly as before — the wrappers run them in a watched pane. When one hits its limit, unsnooze records the stop and wakes it the moment the limit resets.

unsnooze status               # tracked sessions + reset countdowns (live dashboard on a TTY)
unsnooze preview [id]         # dry-run: what would be typed, where, and why — sends nothing
unsnooze resume-now [id|--all]
unsnooze usage                # burn rate and time-to-limit, before you hit the wall
unsnooze doctor [--fix]       # install health check

Needs Node ≥ 20.12 on macOS, Linux or Windows. tmux ≥ 3.2, Zellij, herdr ≥ 0.8 or cmux give pane-level watching; without one, unsnooze runs headless and still catches and resumes stops. Every command: command reference.

Supported agents

Agent	Detection	Revival
Claude Code	StopFailure hook + pane + transcripts; answers the limit menu safely	claude --resume <id>
Codex CLI / ChatGPT app	pane banner + rollout files (exact reset time)	codex resume <id>
Grok Build (experimental)	hook + pane	grok --resume <id>
Qwen Code (experimental)	hook + pane	qwen --resume <id>
Kimi CLI (experimental)	pane	kimi -r <id>
OpenCode (experimental)	pane (it retries by itself; unsnooze revives it if it dies)	opencode -s <id>
Antigravity agy (experimental)	pane	agy --conversation=<id>
Cursor cursor-agent (experimental)	pane; billing-cycle limit, so it probes instead of scheduling	cursor-agent --resume=<id>