Your AI coding team runs the night shift.
Schedule Claude Code and Codex on the subscriptions you already pay for — each driven to its full power, not a dumbed-down generic agent. They run unattended within a budget cap; you triage everything from one inbox.
Free while in beta. You already pay for your coding agent — ratchetAI is the night shift on top. Flat pricing at launch, never per-run.
react@19. Loop paused.Configure once. It runs itself — and stops when it shouldn't.
SCHEDULE
An objective, a cadence, a budget cap.
RUN
Your local, already-authenticated CLI runs non-interactively.
SUMMARIZE
A plain-language summary lands in your inbox.
DECIDE
It runs the next step — or escalates to you.
It runs your Claude Code and Codex — each at its max, and together.
Other tools wrap one agent. ratchetAI reads both of your setups, drives each engine to its individual best, and puts them on the same job — so the run isn't limited to one model's blind spots. Pay for only one CLI? It still works — the second engine is the upgrade, not a requirement.
KNOWS BOTH SETUPS
It detects each engine's tools, MCP servers, and permission posture — Claude and Codex — and tailors every run to what's actually on your machine.
EACH AT ITS MAX
Expert per-engine prompting — parallel subagents, your skills and MCPs, plan→verify, ship-to-live — so each CLI runs at the level a power user gets interactively, not a watered-down default.
THEY CHECK EACH OTHER
One engine builds; the other independently verifies before it's accepted — two engines cross-checking beats one grading itself. Rolling out in beta.
claude -p cron. The defensible part isn't running an agent unattended — it's understanding your Claude Code and Codex deeply enough to run each at its best and put them on the same goal together.
We pointed it at itself — and it shipped.
To test ratchetAI we gave it a deliberately vague goal — "build something more trustworthy and simpler to set up than OpenClaw or Hermes Agent; you decide what it is" — and let it run unattended. Across two chained sessions it chose a product, built it, and verified it, then stopped on its own when the acceptance criteria were met — not on a timer. This is our own dogfood, run in public.
From zero to your first night shift.
Sign up free, connect your machine with one command, and describe your first automation in plain language. It runs tonight.
npx ratchetai-runner connect --url https://ratchet-control-plane.wandering-voice-f671.workers.dev --token rt_… --cwd ~/code
Want to read it first? Browse the source on GitHub — it's built in public.