Watch every surface
One timeline for Codex, Claude Code, and CI—whether they run in a terminal, app, or hosted workflow.
Sleep Mode monitors Codex, Claude Code, and CI while you step away—recovering routine stalls and guarding every permission boundary.
All systems are inside policy. One approval is waiting for morning.
Implementing signed event ingestion
Security review of device pairing
Running unit and integration checks
A small local companion understands each agent's native events. The cloud control plane holds the goal, policy, timeline, and recovery loop.
One timeline for Codex, Claude Code, and CI—whether they run in a terminal, app, or hosted workflow.
Detect failed checks, idle loops, and unanswered prompts. Retry or nudge only when policy says it is safe.
Permissions are concrete, signed, and rechecked on your device. Sleep Mode can ask for more—not grant itself more.
Verified work, decisions, spend, risks, and the exact place a human needs to take over.
Each connector advertises only what its provider can support safely. Observe and Nudge are broad; Operate must be earned action by action.
Sleep Mode separates monitoring, recovery, approval, and incident response so an unattended run can stop safely as well as continue safely.
A safety-first overnight supervisor for Codex, Claude Code, Cursor, Gemini CLI, OpenCode, Copilot CLI, and CI.
Explore use case 02 · Unified monitoringUnify local CLI agents, desktop coding tools, and GitHub Actions into a normalized, evidence-backed operations timeline.
Explore use case 03 · Remote approvalsReview exact coding-agent actions remotely with signed policy context, bounded expiry, and crash-safe one-time consumption.
Explore use case 04 · Failure recoveryDetect disconnected supervisors, repeated failed interventions, CI regressions, and exhausted budgets before they become runaway overnight jobs.
Explore use caseNo. A per-user Rust daemon supervises explicitly armed provider processes and executes only typed, signed actions inside the selected workspace and local policy ceiling.
No. Sleep Mode works through native structured protocols and keeps each provider's sandbox intact. Unsupported or ambiguous permission requests fail closed.
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.
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.
Start with observation. Earn trust one permission at a time.