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.

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:

Quick start

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.

Prefer a text view? Run unsnooze config set autoDashboard off to make
status, usage, and sessions print their terminal view without opening the
full-screen dashboard. unsnooze dashboard still opens it explicitly.

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

GUI sessions (Claude Code's VS Code extension, the ChatGPT/Codex desktop app,
Claude desktop) are watched through the files they already write, by the optional
daemon. Per-agent details, OpenRouter, proxy launchers like Headroom, and Claude
Design: supported agents.

How it works

Stops are detected from agent hooks, saved session files and terminal banners,
and recorded in ~/.unsnooze/state.json with the reset time. A…