AWAKE

Cursor-class. Never idle.

Fleet-first IDE for huge AFK multi-agent swarms that keep growing brands — craft, research, revenue — until you say stop.

See the shell Full product plan

No download yet. This page is the public product surface while the client is built. The trading terminal at /awake/ is a different AWAKE product.

The fleet shell

Mandate board and continuous rail are primary. Craft, research, and growth sit side by side. Editor opens when a human needs it.

AWAKE 24 ACTIVE 3 GATES LOOP ARMED

MANDATE BOARD

SHIPM-14

Sole-ship monorepo after measure green

CRAFTM-11

SaturnDesign compose → residual craft

GROWM-07

Marketing / ads automation queue

CONTINUOUS RAIL defaults preselected · no force-push

Continuous growth

The product assumes you are always building a portfolio that makes money — not a sandbox of idle agents.

Never idle Every tick improves something real or researches until there is a concrete improve to queue. “Drained” is not a stop.
Portfolio with revenue path New projects only when they make sense and have a sell / DFY / productize path — no vanity apps.
No slop Invented UI and brand work run SaturnDesign compose first. Logo test is a release gate.
Revenue first-class Marketing, ads automation, SEO, and offer craft are mandate types — equal weight to code.
Automated recursion measure → queue → claim → craft → ship → prove → arm. Repeat.
Public publish Gate Agents may draft posts. A human owns the live publish button, same as spend and credentials.

Ops continuous lanes (handoff, not client): CONTINUOUS-IMPROVE + CONTINUOUS-POLICY. CONTINUOUS-REVENUE not filed yet — when peers add it, AWAKE coordinates via claim map and does not thrash their surfaces.

Why not stock AI IDEs

Same class of product as Cursor. Different optimization target: continuous multi-agent growth of a real portfolio.

Swarm orchestration first-class Fleet pane and mandate board — not a single chat with agents bolted on.
Never-idle continuous growth Improve or research-to-improve, always. Loop arm is the product, not a script beside it.
Revenue & marketing in-shell Ads, SEO, and growth automation sit on the board next to code mandates.
Craft without slop SaturnDesign-required invent; content rule on every public claim.
Full ship→prove→arm rail One writer per surface; sole-ship; live prove; re-arm. Force-push is not a feature.
Human publish Gate Public posts, money, and credentials cannot be bypassed by the fleet.

How the loop works

01Measure — live truth (manifest, health, honest probes).
02Queue — residual craft, research→apply, growth, portfolio probes.
03Claim — one writer per surface; respect peer exclusive holds.
04Craft — code, copy, ads automation; SaturnDesign before invent.
05Ship — sole-ship only; no force-push.
06Prove — live bytes / checkable claim / health green.
07Arm — re-enter the loop; idle is failure.

Roadmap

Honest stages. Spec sheet, not vapor milestones with dates we cannot keep.

NOW MVP: This product page + durable plan (fleet shell + continuous growth law). Dogfood on Cursor + SWARM + continuous handoff docs.
NEXT V1: Thin client: Fleet, craft/research/growth mandates, claims, full continuous rail, Gate tray with public publish.
LATER V2: Ads automation workers first-class, multi-worktree map, portfolio sense+revenue wizard, residual/grow scoring.

Full plan (technical + IA + risks): docs/AWAKE-PRODUCT.md