Cavvy for Codex

It knows when Codex works.

“esc to interrupt” means working; a question asking for your approval means it needs you, and a notification says so.
It resumes after a restart.

After the background service restarts, or with cavvy restart, Cavvy runs codex resume --last when it is the only Codex session in that folder, otherwise Codex’s own list to pick from.
Your limits, offline.

Usage reads the five-hour and weekly limits from Codex’s own session files on this Mac, once a minute. Nothing goes online for it.
It knows the rules of the task.

In a task, Cavvy passes Codex the task’s rules as developer instructions: commit on the branch, don’t merge, don’t push, and how to take in other repositories with cavvy task add. When its work is finished, Codex says so with cavvy done. Codex’s questions show in the terminal; the hooks for questions above it exist only for Claude Code.
It can give the second opinion.

As the reviewer of a project, Codex reads a change in its read-only sandbox and lists findings by severity, file and line. It is the default reviewer. See Second Opinion.
On your servers, too.

Codex runs on Linux and Mac servers with the same status, rules and resuming. Install, update and sign it in there from Settings → Agents; on a server Codex signs in with a device code you enter on any device. The limits shown come from Codex on this Mac.

Start it in a task of its own

$ cavvy new --worktree feature/x -- codex