FOUNDING COHORT OPEN · REGISTER BEFORE LAUNCH CLOSES REGISTER →
ORCYX
SEARCH ⌘K DOWNLOAD
OVERVIEW SWARM AUTOMATION ENGINE PLATFORM PRICING DOCS
ORCYX SWARM V3  [ FIG.03 / TOPOLOGY ]

A team of agents builds.
A reviewer checks.

Several AI agents work on your idea at the same time. Work moves across a task board, and every finished task is scanned for leaked secrets and unsafe code before it reaches you. The merge stays your call. You also get a chat with each agent.

Directorplans · routes · budgets coder-1opus · implements coder-2gpt-5.5 · implements researchergpt-5.5 · sources Auditorruns the review gateGATE ✓main
CARDS MOVE LEFT TO RIGHT · THE AUDITOR FLAGS WHAT IT FINDS · YOU DECIDE WHAT MERGES
01 / DISPATCH

Parallel seats

The director splits the mission into cards and dispatches them to coder, researcher, and auditor seats - each in its own pane, on its own model.

> swarm dispatch --cards 5
[OK] coder-1 · coder-2 · researcher
[OK] auditor seated on review gate
02 / REVIEW GATE

Nothing merges itself

An auditor seat reviews each builder’s finished work, and every finished card is scanned for secrets, unsafe code and CSP problems - findings are bannered, never auto-passed, and the merge is yours. Footguns like bypass and broadcast stay loud in the chrome.

✓ gate scan · 0 high findings
✓ no destructive execution paths
◦ waiting on coder-2 redaction fix
03 / HANDOFF

Pointers, not paste

Agents hand off worktrees and card references - never re-stated context. Token spend stays flat as the team grows, and every handoff lands in the Vault.

handoff: card_01kt4jd0hv84
worktree …/pane-p_95e0/coder
touched: SqliteStore.cs (+3 files)
04 / SUB-SWARMS

A seat can hire its own team

An agent that finds its card too big spawns a swarm underneath it, scoped to its own directory. The tree shows which run belongs to which parent, so a nested team is never an orphan.

> swarm spawn-nested --parent coder-2
nested run sub_7f21 · own directory
parent coder-2 · 3 seats under it
05 / BUDGETS & PAUSE

Stop it mid-flight

Hourly and lifetime token caps per role, warned before they bind. Pause holds the whole roster and shows you which seats have acknowledged it - a paused run says so, it does not quietly finish the card in flight.

budget coder · approaching hourly cap
paused 00:42 · reason: cost review
ack 3/4 seats
06 / TEMPLATES & REPLAY

Why did it route that way?

Save a roster that worked and spawn it in any workspace. Afterwards, the router's dispatch timeline replays so you can answer why the coordinator sent a card where it did - without re-running the swarm to find out.

template audit-sweep · 4 roles
replay dispatch timeline · read-only
TO coder-2 · matched scope rule 3
MULTI-PROVIDER  [ FIG.02 / ROSTER ]

Any model.
Any seat.

Mix providers inside one swarm: Opus on the hard pane, a cheap model on the researcher, a custom endpoint on the auditor. On keys you bring, Orcyx adds no markup, and per-pane spend stays in the chrome where you can see it.

  • →Per-pane model, cost, and token counters
  • →Reference-based payloads - pointers, not re-stated context
  • →Broadcast & bypass stay loud in the pane chrome
PROVIDERS · BYO KEYS
Claude Anthropic
Codex OpenAI
Gemini Google
Custom any endpoint
session $1.28 · 57.1k tok 4 panes live
IN THE APP  [ SCREENS ]

Many agents, one desk.

Live recreations of two screens: the board that shows who is working, and agents reporting back side by side. Hover over them.

Home

Every agent and today's spend on one board.

Space

Two agents in parallel. Each reports back - and knows what the other is doing.

Run your first swarm.

NEXT · AUTOMATION →