Say the outcome. Boomship reads what your company knows, plans the work, does it, and hands back a receipt.
One sentence becomes a plan you can read, change, or let run. Auto picks the effort for each step.
Launch our new product.
Repositories, files, Notion, Linear, Slack, Gmail, Drive and memories, compiled into context for every step. A contradiction is shown, never averaged.
Live Build changes the rendered product. The diff, the tests and the critique come afterwards, as evidence.
Your first order in nine minutes.
Northstar v4 sets up your catalogue from last month’s invoices.
Start with an invoiceA line sent while it works is received at the next turn. When a check fails, what depends on it holds and the run waits for you.
“Lead with speed, not price, everywhere.”
received · turn 2·route changedIllustrationThe update changed the launch page’s number. Nothing goes out until a person looks.
heldthe launch pagethe Friday update
No recommendation · the receipt records which you chose
Both moves are real: resume picks the run up where it stopped, undo restores its checkpoint. A chain that stops offers its own two: queue it again from there, or skip it and queue the rest.
Fresh tests, a typecheck, a review by a model the builder did not use, a security review at high risk. What could not run says not run.
A Mission runs on the server, not in your tab. Come back to the receipt.
Claude, GPT, Gemini and OpenRouter, on your keys. Auto picks a model for each step and the receipt says why.
Intelligenceauto/implementation → balanced tier, anthropic (user key) Illustration
Each connection says exactly what it reads and writes. Nothing writes until you allow it.