For people with more ideas than time

The ideas cluttering your head, your late-night notes and your markdown docs finally do something.

Dump them into ampm as fast as they arrive — half-sentences are fine. Agents dedupe them, groom them, set priorities, work out what depends on what, and line them up in the order they can be built. Then they build them, one reviewed pull request at a time.

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.

From a 1 AM note to a merged feature, without you keeping track

  1. Mon 1:12 AMYou

    Get it out of your head.

    “recurring invoices?? monthly + yearly.” Typed on your phone, half asleep. It goes on the Roadmap, which means it's written down somewhere that will act on it — so you can stop holding it.

  2. TueThe factory

    The pile sorts itself.

    Grooming notices two of your notes are the same idea and folds them together. It spots that recurring invoices need card payments, which need stored payment methods, and orders them that way. You approve the proposal with one tap.

  3. FriYou

    The first one ships.

    Stored payment methods: planned, built, tested, reviewed, waiting for your merge. The next idea in the chain is already being refined. Nothing you wrote down was lost, and nothing waited on you to remember it.

Not another graveyard

A backlog that does the work, instead of waiting for you to

Capture
Notes and markdown docs:Wherever you were when it hit you — five apps, three docs.
ampm:One place, from anywhere, in whatever words you have.
Duplicates
Notes and markdown docs:The same idea, written four times over two years.
ampm:Deduped automatically; you confirm the merge.
Priority
Notes and markdown docs:Everything is P1 until you give up on the list.
ampm:Agents propose priorities and keep them spread out.
Order
Notes and markdown docs:You have to remember what depends on what.
ampm:Dependencies are worked out and the work is sequenced for you.
Progress
Notes and markdown docs:Nothing happens until you sit down and start.
ampm:The next ready idea is being refined, planned or built right now.

Dependencies

A web of dependencies? Fire and forget.

Dump ideas in any order. Grooming works out what waits for what, and each task starts on its own the moment the one it needs merges — or deploys. You never sequence the work by hand.

waits for mergewaits for mergewaits for mergewaits for mergewaits for mergewaits for mergewaits for mergewaits for deploywaits for merge
it-0a15Store payment methods per customerWaiting
it-0a16Invoice PDF templateWaiting
it-c2-1Reminder schedule per invoiceWaiting
it-0a12Let customers pay invoices by cardWaiting
it-c2-2Send reminder emails with the PDFWaiting
it-0a11Recurring invoices, monthly and yearlyWaiting
it-0a18Late fees on overdue invoicesWaiting
it-c2-3Unsubscribe from remindersWaiting
it-0a17Client portal: invoices and subscriptionsWaiting
0 of 9 mergedRight goes first · each starts the moment what it waits for landswaits for mergewaits for deploy

Have a poke around

Then watch the order fall into place

Invented data, real mechanics. Approve one grooming proposal in the inbox: a duplicate folds away, priorities spread out, and the rest lines up in the order it can be built — each card waiting on the one it needs.

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.

Signals from the outside world

Notes to self and voice memos become tasks

Email yourself a half-sentence or record a memo on a walk. Intake turns them into tidy Roadmap ideas, with repeats merged into what you already have. You choose what the factory builds.

Intake2 processes on · receiving signals

Processes

Notes to selfideas@ email · On every emailOn
  1. Turn each note into an idea
  2. →Merge it with ideas you already have
  3. →Suggest tasks
    Voice memosShortcuts · voice memo · On every memoOn
    1. Transcribe
    2. →Pull out anything buildable
    3. →Suggest tasks

      Suggested tasks

      Suggestions arrive once signals come in.

      Roadmap

      Sent tasks land here.

      Engineer from anywhere

      An idea on the bus becomes a task

      Ideas arrive away from the desk. Jot one down wherever you are, and intake turns it into a suggested task with its evidence attached, ready for the Roadmap.

      From a beach chair

      Intake1 process on · receiving signals

      Processes

      Notes to selfideas@ email · On every emailOn
      1. Turn each note into an idea
      2. →Merge it with ideas you already have
      3. →Suggest tasks

        Suggested tasks

        Suggestions arrive once signals come in.

        Roadmap

        Sent tasks land here.

        Have a poke around

        Turn a big idea into a plan you trust

        Press Ideate on a big idea: on a canvas, the agent researches, sketches the flow and proposes a breakdown — and nothing is created until you approve it.

        Recipe app roadmap1 ideas
        Plan meals for the weekit-i01P1On the RoadmapBig idea · shape it on a canvas

        Also in the factory: 2 being built, 0 shipped.

        Questions

        Do I have to write proper tickets?

        No. Half-sentences are fine. Ideas wait on the Roadmap, and agents refine them into acceptance criteria you approve before anything is built.

        How does ampm decide the order?

        Grooming proposes priorities, merges duplicates and works out which ideas depend on which, then sequences the backlog into Next, Soon and Backlog. You approve the proposal with one tap.

        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

        Empty your head tonight

        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.