For Claude Code and Codex subscribers
Your coding-agent subscription sleeps 16 hours a day. Put it on the night shift.
You already pay for Claude Code or Codex. ampm keeps it working while you sleep — planning, building, testing and reviewing your backlog in isolated sandboxes — and when one plan hits its usage limit, work moves to your backup account with nothing lost. You wake up to pull requests.
A kanban board with four lanes — Ideating, Planning, Building and Shipping — carrying tasks from a fresh idea through to a pull request waiting for review.
What actually happens between midnight and your first coffee
- 11:47 PMYou
Two sentences and a light switch.
“The CSV export falls over on big accounts — it buffers the whole thing in memory.” You file it the way you'd tell a colleague, in whatever words you have at midnight. No template, no ticket taxonomy, no estimating poker.
- 3:12 AMThe factory
Nobody is awake. Everybody is working.
A refiner turns your sentence into acceptance criteria. A planner writes the plan. A builder implements it in an isolated sandbox, the tests run, a reviewer pushes back, the builder goes again. Three rounds. The reviewer stops finding things.
- 8:30 AMYou
One PR. One question. Coffee.
A pull request, already reviewed and tested, waiting for your yes. Beside it, one honest question: the fix changes a response's shape, and the reviewer wants you to pick. You answer it in a sentence. The rest of the night needed nothing from you at all.
Have a poke around
Your morning, in one conversation
Invented data, real mechanics. Ask what happened overnight, see the one merge that needs you with ampm's context, ask what it would do — and merge it from the chat.
Scroll a little further to load the demo
The board
Every piece of work, at the exact stage it's in. Positions aren't decoration — a card's column IS its state.
The inbox
One queue of everything blocked on you, each ask carrying the plan, the diff and the transcript behind it.
Activity
Who's working right now, on what, and what each run cost — live, with every finished run still on the record.
Engineer from anywhere
Catch up before you're out of bed
The night's work fits on a phone: what shipped, what's waiting, and the one call that's yours. Answer it before the coffee's ready, and the builder picks it up while you're still getting dressed.
From a beach chair
Scroll a little further to load the demo
Use what you pay for
Every hour of your plan, working
The subscription you already have
ampm runs Claude Code or Codex on your own plan — no API keys, no second bill for the tokens.
Limits don't stop the night
When one account hits its usage limit, work fails over to a backup account and carries on from where it was.
Workers where you want them
Agents run on your machine, a box in the closet, or a cloud server — one line connects each worker.
A morning, not a mess
Overnight work arrives as reviewed, tested pull requests and a short list of questions, never as a pile of half-finished chats.
The inbox
Nothing merges unless you want it to.
The decisions that matter — the plan before anyone writes code, the call only you can make, the merge into your main branch — wait for your yes. Not because the agents are asked politely to stop: the board simply has no way past them without an answer. Hand off the ones you trust it with; keep the rest.
Every ask arrives in one queue with its receipts attached: the plan, the diff, the PR, the full transcript of what the agent actually did. Approve it, send it back with a reason the crew has to answer, or just reply to the question. Then close the laptop again.
- planplan · diff · transcript
Is this the right approach before anyone writes code?
- questionplan · diff · transcript
Keep the old endpoint alive for a release, or cut over now?
- mergeplan · diff · transcript
Does this change go into your main branch?
Questions
What happens when I hit my usage limit overnight?
Work fails over to a backup account and continues from where it was. Nothing is lost and nothing restarts from scratch.
Do I need API keys?
No. ampm runs Claude Code or Codex on the subscription you already have.
Which coding agents does ampm work with?
Claude Code and Codex. ampm runs them on the subscription you already pay for — no API keys and no second bill for tokens — and when one account hits its usage limit, work moves to a backup account without losing anything.
Does ampm merge code on its own?
Nothing merges unless you want it to. Plans, questions and merges wait in your inbox with the plan, diff, pull request and full transcript attached, and you decide which decisions to keep and which to hand off.
Where does the code run, and is my repo safe?
Every task runs in an isolated sandbox on its own worktree, on workers you choose — your laptop, a server you own, or a cloud machine — and can only push to a branch. The output is always a pull request into your repo.
How is this different from chatting with a coding agent?
A chat forgets everything when you close the tab and needs you watching it. ampm keeps every task in a database with its plan and history, runs a real process — plan, implement, test, review, merge — and only asks you when a decision is actually yours.
Can one workspace cover several repos?
Yes. Add the repos agents should change, and add more as read-only context — a design system, an API they call, product docs — so their work matches what's around it. One change can span several repos as one piece of work.
How do I get access?
Join the wait list with Google or GitHub. We're letting people in a few at a time, in the order they joined, and we'll email you when it's your turn.
Early access
Start tonight's shift
We're letting people in a few at a time. Join the wait list with Google or GitHub and we'll email you when it's your turn. Run it on our cloud or on infrastructure you control — your repos, your subscriptions, workers on machines you choose.