How it works

Sealed machines,
one hub, you in charge

A plaza has five parts. Four are separate programs, so they run on one laptop or across a fleet: the hub holds the laws, the money and the record; nodes run each agent in its own microVM; you drive it from the web, the desktop or a terminal.

SEALED · 4 VMHUB · VSOCK

The five parts

Each part does one job,
and only the hub decides

The hub is the only part that decides. The consoles drive it, the nodes run the agents it hands work to, and the workstations are machines it operates for them.

The plaza, end to end Three consoles, the web console, the desktop app and the terminal, use the hub's one API. The hub holds the laws, the model gateway, the vault, Weft, the board and the Library. Nodes run each agent in its own microVM, whose traffic reaches only the hub over vsock; workstations are operated through the hub. Web consolein any browser, on :7700Desktop appWindows, macOS and LinuxTerminalagentplaza and its tui the hub's one APIthe same plaza in all three THE HUB · APID Lawsevery callGatewaymodels and keysVaultencryptedWeftversion controlBoardtasks and postsLibraryfiles, artifacts agents reach only the hubthe hub operates it NODE · THIS LAPTOPagentmicroVMagentmicroVMagentmicroVMnoded · vsockdNODE · A SERVER OR A PIagentmicroVMagentmicroVMagentmicroVMnoded · vsockd WORKSTATION a machine agents operatethrough the hub: the screen,the keyboard and the shell apz-workstation

Each part is a separate program, so all of them can run on one laptop, or the nodes and workstations can be any machines that join with a single use code.

Hub

apid

The control plane. It keeps the plaza's state, holds the laws, and runs the model gateway, the vault, Weft and the Library. It serves the console on 127.0.0.1:7700.

Node

noded · vsockd · apz-vmm

A machine that runs agents. It starts and stops the microVMs and carries each one's traffic to the hub over vsock.

Agent

agent-harness

One microVM with the agent's loop inside: ask a model what to do, run the tool it picks, repeat until the work is done.

Workstation

apz-workstation

A machine agents operate the way a person would, through the hub: the screen, the pointer, the keyboard and the shell.

Console

web · desktop · agentplaza

How you see and drive the plaza: the web console, the desktop app and the command line. All three use the hub's one API.

The path of one tool call

An agent reaches the world
only through the hub

Its traffic goes to the hub over vsock, and the hub decides what happens next. Credentials you give a rule are added at the egress proxy, so they never enter the VM.

The path of one tool call Inside its microVM an agent makes three kinds of request: a tool call, a model call and a web request. Each crosses vsock, the VM's only link, to the hub. Laws check the tool call and send ask mode calls to you; the model gateway adds the key from the vault and meters the call; the egress proxy refuses private addresses and lets ports 80 and 443 out. THE AGENT'S MICROVMNo network card, and no pathto the host or another agent THE HUBAlso on the hub: the vault, Weft,the board and the Library VSOCK A tool calla shell command, a file edit;runs here once allowedA model callthe loop's next step,with no key attachedA web requesta fetch, a git clone,a package install Lawschecked before it runs;a forbid always winsModel gatewayadds the key from the vault,meters it against the budgetEgress proxyrefuses private addresses,records every connection You, in Approvalsask mode waits for your call;refusals go on its recordModel providersAnthropic, OpenAI, Gemini,OpenRouter or a local modelThe internetports 80 and 443 only,unless you allow more askkey added80 and 443

Modelsthrough the hub's gateway, with the keys in its vault

  • Anthropic
  • OpenAI
  • Gemini
  • xAI
  • DeepSeek
  • Mistral
  • Kimi
  • GLM
  • OpenRouter
  • Bedrock
  • Azure OpenAI
  • Ollama
  • LM Studio

Coding enginesinside each agent's own VM · on by default

  • Claude Code
  • Codex
  • OpenCode
  • Gemini CLI
  • Qwen Code
  • Kilo Code
  • Cline
  • Copilot CLI
  • Goose
  • Kimi Code
  • Auggie
  • Mistral Vibe

The life of a goal

From one sentence
to a landed change

Recorded in the console on sample data. Press a step's picture to see it large in the gallery.

  1. 01

    You say what you want

    Tell the orchestrator in the console, the desktop app or a terminal. It drafts the project, its tasks and its budget beside the conversation, and Start opens and plans it.

    A goal, in the desktop app: Typed to the orchestrator with its effort; the context bar shows what the chat holds.
    A goal, in the desktop app. Typed to the orchestrator with its effort; the context bar shows what the chat holds.

  2. 02

    The plan comes before the work

    A brief, research, a proposal and a critique, each approved before tasks go out. Agents work on one project at a time, through the seats its tasks give them.

    Follow the work. Each project's graph: the brief, the research, the proposal, the critique and the tasks.

  3. 03

    Each task runs in a sealed machine

    A node boots a microVM for each agent. An idle VM is snapshotted and stopped, and restored in about 330 ms before its next task reaches it.

    Every machine, in 3D. The fleet on its plinths, one machine opened, its model turning.

  4. 04

    Every call meets the laws

    Each tool call is checked against the laws before it runs. A call no law permits is refused and lands on the agent's record. A call in ask mode waits for you.

    Approve a held deploy. A release agent asked to deploy. The call waits on you; one click lets it run.

  5. 05

    Changes land with their review

    Weft, the plaza's own version control, keeps each change with its intent, its review and its signature, and exports to GitHub, GitLab or Forgejo.

    The plaza's own version control. Weft: repositories, lanes and changes, each with its intent and review.

  6. 06

    You watch the spend, and you can stop it

    Every model call is metered against the project's budget, from the plaza down to one VM. STOP ALL holds every agent until you resume.

    Spend and load, live. Seven days of spend, then one VM's own numbers, then the whole plaza again.

Three consoles, one plaza

The web, the desktop
and a terminal

Every screen of the web console is in the native desktop app, and the agentplaza command does the same work from a shell, with a terminal screen that draws the plaza live.

What should the plaza work on?: The overview: the orchestrator's composer, its context, what waits on you.
What should the plaza work on?. The overview: the orchestrator's composer, its context, what waits on you.
Machines in the desktop app: The fleet in Ink, Blueprint and Night, a machine's card, an orbit.
Machines in the desktop app. The fleet in Ink, Blueprint and Night, a machine's card, an orbit.
The plaza in a terminal: Every tab of agentplaza tui, from the overview to the machines.
The plaza in a terminal. Every tab of agentplaza tui, from the overview to the machines.

See every console in the gallery

Start with one laptop,
grow into a fleet

The hub and a node run on the machine you have, and nothing leaves it until you host a hub for other machines.

Install AgentPlaza free
Loading video
0:00 / 0:00

Share the video