/ultracode

/ultracode is a switch, not a job. Turn it on, and the model in this chat may split a large task across several agents that check each other before anything reaches you. It decides when. Short questions still get a short answer.

Type it the same way

/ultracode         on for this chat
/ultracode <task>  on, plus the task
/ultracode off     off

The word ultracode anywhere in a message turns it on too. /swarm <task> skips the decision and starts a workflow right away; your account needs the swarm permission for that. In the terminal client, /ultracode-jetzt <task> does the same.

Fan-out

It fans out

The task is decomposed and the parts run in parallel rather than one after another. Breadth costs wall-clock time once instead of once per part.

One after another

In parallel

Wall-clock

Both bands carry the same parts and the same work. Only the arrangement differs.

Refutation

It verifies adversarially

Each part gets two checkers. Their job is to find what is wrong with the files an agent changed, not with its summary. A part they reject goes back for a fix.

Checkers

Checkers accept

Merged

Checkers reject

Sent back for a fix

Two ends for the same part. The empty half of the lower track is the point: a rejected part does not reach you, it goes back to the agent instead.

Card

A card tracks it in the chat

While it runs, a card appears with the plan and one line per agent. The arrow on a line opens its log.

The plan: What the model gave each agent, in its own words
Per agent: NameStateA running clock
The log: The task it was givenEvery tool callWhat it wrote back

The card streams from the server. Reload, switch devices or close the tab: it picks up where the run is, and the model waits for the result before it answers you.

Cost

It costs more

Several models on one task is several bills. Use it when being wrong is expensive, and /goal the rest of the time.

/ultracode: Audits Migrations Reviews before a release
/swarm: Skip the decision, start right away
/goal: The rest of the time

Ceilings

The ceilings still apply

It obeys the same ceilings as any other job: your plan's run time, the budget governor and a spend cap if the model sets one.

Every lane

One bar, drawn across every lane at once. Fanning out buys no exemption from it.

With ZeroLog Free, every agent runs on free models. If one is rate limited, the next model in the chain takes over and the busy one rests for a while instead of being asked again right away.

Something missing or wrong here? Say so. The documentation is part of the product, not an afterthought. All topics · Legal & privacy · Home