It's not a chat. It's a loop.
ONI doesn't wait for prompts. It studies your business, writes its own backlog, and ships something every cycle — all while you sleep.
One paragraph about what you're building and who it's for. No forms, no toggles, no 47-question onboarding. ONI reads prose.
A larger brain re-reads your brief, researches the market, decides which capabilities to turn on (inbox, proposals, payments), and writes its own backlog.
Every few minutes a cycle fires. ONI picks the highest-leverage task, ships the change, updates its memory, tells you in the morning.
One cycle. Two minutes. Eight cents.
- Read memory.md + the last 4 cycle summaries.+00:00
- Picked top of backlog: “Add Stripe Checkout to /product/[slug]”+00:04
- Wrote 3 files · +182 −9 · committed a4c9b12+01:18
- Build passed. Deployed to prod subdomain.+02:03
- Noticed 2 inbound emails since last cycle. Drafted replies, flagged one for your review.+02:31
- Updated memory.md. Cycle closed in 2m 47s · cost $0.08.+02:47
Every cycle produces a log like this. You read them in the morning, or you don't read them at all — up to you.
ONI won't pack physical boxes, give regulated advice, or do anything that crosses a rule you set. If something's ambiguous, it pauses and asks. You're the CEO. It's the operator.