Agent Engine · bundle landing Mobile-first · light primary · theme persists · the hero settles to "You're clear".
Blueprint decides→ RoadWork tracks→ Agent Engine executes
Agent Engine · the execution bundle

Run a room of AI agents on your own subscription.

Dispatch the work, watch a wall of agents do it, and touch only the dangerous parts. One controller drives many terminals for throughput — you stay the judgment, never the copy-paste.

See how it works ▸ Open the console
Proven · one PM terminal drove ~15 background agents with zero copy-paste (2026-07-06).
On your subscription · every terminal runs the local claude — the engine never calls the API.
Internal today · the engine AI Uni's own agents run on. No pricing yet.
ExMan · the console on your subscription
hosted on your Claude subscription · observe + drive only · no API · no shell
One engine · three surfaces

Where the work lives, how you watch it, how you drive it.

Agent Engine is a bundle. RoadWork holds the work, Pulse lets you watch it move, and ExMan is the console you drive it from at your desk. Sold together or separately.

RoadWork · tracks

The editable work board — every idea, initiative, epic, feature and task, and where each one stands. The single truth for work; if a view disagrees with RoadWork, RoadWork wins.

○ Internal today · the Work Board Where the work lives
Pulse · watches

The read-only watch surface: per-terminal heartbeat cards and the composed in-progress view. Check whether the work is still beating — including from your phone, away from the desk.

○ Internal today · a view, never changes real state See Pulse
ExMan · drives

The execution console. It hosts your Claude Code terminals on your subscription — a wall of summary cards by default, click any one to open the live terminal, and one batched tray of the things that truly need you.

◐ Two concepts · your pick pending See the ExMan path
What you can do with it

Run the room. Watch it. Touch only the dangerous parts.

Every scenario is a real job the console does, ordered by how much it changes your day. The biggest one is the animated demo up top; the next four are drawn as the path you'd walk through the real console screens; the rest are grouped at the end. Each one drills into the step that proves it.

Run a room of agents without being the message bus Killer job · shown up top

You dispatch the work and one PM terminal drives a whole wall of agents to done — the way about 15 ran with zero copy-paste on 2026-07-06 — so you stop being the wire between terminals. That's the animated demo at the top of this page.

See the whole path
Watch every terminal as summaries from one wall

A dozen live terminals collapse into one summary card each — name, task, state, last line, time — so you scan the floor instead of tabbing through streams to find the one that matters.

a dozen live terminals
>_CC1 · live scrollback…
>_CC2 · live scrollback…
+10more streams to tab through
one card each
ExMan · the wall
●CC1 · Account model4m
●CC2 · Intel refresh2m
●MULE · Design Hub1m
See the summary wall
Get asked only for the judgments that are truly yours

One batched tray surfaces just the real calls — a merge, an APPROVED, a deploy, a SQL runbook — with defaultables filtered out upstream. Its best state is empty.

your action tray
◆Merge · PIPE batch · DevOps✓ Security✓ Verifier✓
◆Approve · Account content model — schemaSO #30
you act · it clears
your action tray
✓You're clear — 0 actions
the floor is running itself
See the action tray
Drop into one live terminal the moment one needs you

Stay on summaries by default; click (or press Enter on) any card to open that terminal's actual live scrollback on purpose — opening a second closes the first, so the wall never becomes a dozen streams.

ExMan · the wall
◆CC1 · Needs you
●CC2 · Intel refresh
●MULE · Design Hub
click / Enter
CC1 · live scrollback
>drafted the account DDL runbook…
◆needs your APPROVED db-schema
the real read · no shell behind it
See click-to-open
See who's routing to whom, in one feed

A hosted hop and an external inbox hop share one message shape, so every hand-off — from, to, how, when — reads in a single honest feed, not two disjoint lists.

two transports
hostPM → CC1
inboxMEET → PM
one message shape
the routing inspector
→MEET → PM · via inbox
→PM → CC1 · via host
◆CC1 → you · needs approval8m
See the routing inspector
More the console does
Hand a MEET note to PM with zero paste

MEET writes one line to the shared inbox and the console types it into PM for you — the biggest daily copy-paste you still do, gone.

See where a dispatch enters
Trust the floor: two verbs, your subscription, never the API

Every terminal is a local Claude on your own subscription, and the console can only watch a terminal and type into it — never run a merge, a deploy, or the API itself.

See how it runs on your subscription
The line drawn on the screen

We eliminate the carry. You keep the judgment.

The engine takes over the finding, copying, pasting and tracking. It never takes over the dangerous decisions. Those stay your hands, on purpose — the machine surfaces the exact command and waits.

◆
Mergesbranch protection — you click Merge in GitHub
◆
Approvalsyou type the exact APPROVED <class> — never inferred from silence · SO #30
◆
Database changes & SQLthe runbook is surfaced; you run it · SO #30
◆
Production deploysthe exact command is surfaced; you run it · SO #30

Honest state — internal today

Agent Engine is the engine AI Uni's own agents run on. It is internal for now — the substrate every other product is built and managed on. There is no pricing and no external sign-up here yet.

This is not "Agent Platform." The external, productized-for-other-teams version is a separate, much-later product. We keep them apart on purpose so nothing blurs: what you see here is the internal control-plane, not a customer platform.