You describe the work: the hub plans it as a project, runs each task as sessions in their own microVMs, has every
change reviewed on a second model, and lands it through Weft, the plaza's own version control. One hub holds the
plaza, nodes and workstations do the work, and the web console, the desktop app and the agentplaza command all show
the same plaza. One button, STOP ALL, holds everything at once.
See it run
The console, recorded on sample data. Every flow below is the real web console against sample data. Each image
opens its recording in the gallery.
The desktop app. A goal goes to the orchestrator with its effort, and the context bar breaks down what the
conversation holds; then the agents that took the work.
The terminal. agentplaza tui shows the same plaza in a terminal: the floor, the agents, the board, the
conversations, the machines and the models, with live events, and you talk to the orchestrator as it answers.
Recorded from the desktop app and agentplaza tui against a hub with sample data. The recordings and the art
are made by the scripts in scripts/readme/.
Why AgentPlaza
- Your machines. The hub, the nodes and the workstations run on the machines you choose. The daemons bind to
loopback by default.
- One microVM per agent, with no network interface. Each agent runs in its own microVM. Its commands run only
inside that VM, and its traffic goes only to the hub, over vsock.
- Laws on every tool call. The laws are written in JHRL and checked before each tool call runs. A call is
allowed, refused, or sent to you to decide. A call that no law permits is refused.
- Budgets you set. Each project and task has a budget in dollars or tokens. Every model call is held against it
before it is sent and settled after, and a task that reaches its cap pauses and asks you.
- Every change reviewed, then landed. A task's builder works in its own VM, a reviewer on a different model checks
the change, and it lands through Weft's queue with its intent, its review and a signature.
- STOP ALL. One button holds the whole plaza. It cancels the running work, refuses model calls until you resume,
and records who pressed it.
- Any model provider, through one gateway. Agents reach models only through the hub's gateway, which covers
Anthropic, OpenAI, Azure OpenAI, Gemini, Bedrock, Vertex AI and OpenAI-compatible providers. Provider keys stay in
the encrypted vault and never enter a microVM.
- One plaza, three consoles. The web console, the desktop app and the
agentplaza command use the hub's one API
and show the same plaza.
- Workstations that agents use like a person. An agent works a machine through the hub: the screen, the pointer,
the keyboard and the shell, in a work folder. You can take over the mouse and keyboard and give them back.
Install
Linux, macOS and Raspberry Pi OS:
curl -fsSL https://agentplaza.io/install.sh | sh
This installs the macOS DMG or the Linux package for your distribution, after checking every file against the
release's SHA256SUMS.
Windows x64 and arm64:
irm https://agentplaza.io/install.ps1 | iex
This installs the MSI for your architecture.
The installer takes options as environment variables, or as flags after sh -s --. APZ_VERSION pins a release,
--dry-run shows the plan, --uninstall removes what the installer put in place, and APZ_FORMAT forces a Linux
format. For example: curl -fsSL https://agentplaza.io/install.sh | sh -s -- --dry-run.
The hub, the console and the desktop app run on every system below. Agents need a hypervisor, so they run only on the
systems marked yes:
| System | Hub and console | Agents |
|---|
| Linux x86_64, arm64 | yes | yes, with KVM (/dev/kvm) |
| Raspberry Pi 4/5, 64-bit Raspberry Pi OS | yes | yes, with KVM |
| macOS, Apple silicon | yes | yes, with Hypervisor.framework |
| macOS, Intel | yes | no: run them on a node elsewhere |
| Windows 11 (or 10 2004+), x64 | yes | yes, with the Windows Hypervisor Platform feature |
| Windows, arm64 | yes (the node link) | not yet: run them on a node elsewhere |
The desktop app is self-contained: "Start locally" and "Host a hub" start the hub and the node services themselves,
with no Docker, database server or object store to provision. The hub keeps its state in three SQLite files
(plaza.db, transcripts.db and metrics.db) and an object store in one state folder. They use the ports 7700
(hub), 8899 (noded) and 19080 (vsockd). The macOS builds are not notarized yet, and the MSI is not code-signed
yet.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
