The night shift for your AI agents

Keep agents moving.Never outside the lines.

Sleep Mode monitors Codex, Claude Code, and CI while you step away—recovering routine stalls and guarding every permission boundary.

Built forOpenAI CodexClaude CodeGitHub Actions
Tonight's runShip signed event ingestion
Sleep mode on
Goal progress5 of 8 checkpoints verified

All systems are inside policy. One approval is waiting for morning.

CX
CodexWorking

Implementing signed event ingestion

CL
Claude CodeHeld safely

Security review of device pairing

GH
GitHub ActionsWorking

Running unit and integration checks

Routine stall recoveredCodex resumed after a stale test fixture was corrected
8-hour durable runs Immutable permission ceiling Remote approvals Complete audit trail

Your agents keep their tools.
Sleep Mode keeps the watch.

A small local companion understands each agent's native events. The cloud control plane holds the goal, policy, timeline, and recovery loop.

01

Watch every surface

One timeline for Codex, Claude Code, and CI—whether they run in a terminal, app, or hosted workflow.

02

Recover routine stalls

Detect failed checks, idle loops, and unanswered prompts. Retry or nudge only when policy says it is safe.

03

Hold the hard line

Permissions are concrete, signed, and rechecked on your device. Sleep Mode can ask for more—not grant itself more.

Choose how far the night shift can go.

Each run has a response level and a signed permission envelope. A higher level never overrides a denied action, expired budget, or provider sandbox.

Exact repositories and filesystem roots Command, network, cost, and time limits Protected actions held for a human
Read the security model
L0
Observe

Summarize and alert. Never answer an agent.

L1
Nudge

Send pre-approved prompts and status requests.

L2
Operate

Resume agents and run allowlisted tests or builds.

Recommended
L3
Delegate

Create branches or draft PRs when explicitly granted.

Wake up to evidence, not a wall of terminal output.

Verified work, decisions, spend, risks, and the exact place a human needs to take over.

Good morning, WilliamNight shift made solid progress.
5 / 8
Event ingestion implemented and tested
Device pairing threat model reviewed
Draft PR held for your approval
$8.42 spent6 safe interventions0 policy violations

One run can cross the CLI,
editor, and CI.

Each connector advertises only what its provider can support safely. Observe and Nudge are broad; Operate must be earned action by action.

Compare every integration

Not just “keep the terminal alive.”

Sleep Mode separates monitoring, recovery, approval, and incident response so an unattended run can stop safely as well as continue safely.

Know exactly what stays awake.

01Does Sleep Mode control my entire computer?

No. A per-user Rust daemon supervises explicitly armed provider processes and executes only typed, signed actions inside the selected workspace and local policy ceiling.

02Does it bypass Codex, Claude, Cursor, or other agent permissions?

No. Sleep Mode works through native structured protocols and keeps each provider's sandbox intact. Unsupported or ambiguous permission requests fail closed.

03What happens if the computer sleeps or loses its network connection?

The daemon holds an OS-native idle-sleep assertion while a run is armed and journals encrypted events locally. The cloud watchdog pauses the run after four minutes without a newly received signed event.

04Can an agent increase its own autonomy level?

Never. The run's signed permission ceiling is immutable. An agent may request one action already inside that ceiling, but only a human can arm a broader future policy.

Put your agents in Sleep Mode.

Start with observation. Earn trust one permission at a time.