See it first, without an account
The demo shows AgentX passing a task from one agent to an agent on another machine. It runs three AgentX daemons (background services) on your own computer and needs no model account: the network connection, routing and records are real, but the model replies are scripted, so nothing calls a paid model. It doesn't touch your real agents or credentials.
You need Node.js 22.19 or newer, up to 26. Nothing else: no download of the source code, no account and no API key. If Node.js isn't installed yet, follow Install Node.js for the demo. The demo runs on macOS and Linux; on Windows, try it inside WSL.
Run the demo
- Terminal: start the demo:shThe first run downloads the AgentX package, which takes a minute or two. The terminal may stay quiet during that time, or print
npx agentix-cli demonpm warn deprecated …lines: those warnings are harmless. The demo writes its files to a folder called.agentx-demoin the folder you ran it from, and deletes it when you stop the demo (unless you use--keep). - Wait for the line
Dashboard: http://127.0.0.1:18931/live. The demo opens it in your browser. On a machine with no browser, such as a server, it printsCouldn't open a browser. Visit http://127.0.0.1:18931/liveand carries on. That address opens the Hub's Live page (/hub#page=live). - Browser: watch the Live page. The task moves from one machine to another.
- Terminal: press Enter to play the scenario again, or Ctrl-C to stop the demo.
Options
Add these after npx agentix-cli demo, for example npx agentix-cli demo --once.
| Option | What it does |
|---|---|
--once | Plays the scenario once, then stops everything. |
--no-open | Doesn't open the dashboard in your browser. |
--keep | Keeps the .agentx-demo folder when the demo stops, so you can read its logs. |
--base-port <port> | Uses other ports. The three demo machines use this port and the next two; the dashboard uses this port plus 10. The default is 18921. |
The demo also prints the command to connect a real model, written the way you started it: npx agentix-cli setup after npx, agentx setup after an npm install.
Each demo machine records every message it handles in its own intent ledger. The scenario's last line gives the command to read it, for example npx agentix-cli ledger events --cwd .agentx-demo/node-a. Run it from the folder you started the demo in, while the demo is still running (node-b and node-c are the other two machines). With --once, the folder is deleted when the demo stops, so the line is left out; add --keep to read the ledgers afterwards.
If you already have a built copy of the source code (see Install › Run from source), node dist/cli.js demo in that folder does the same.

The demo after a task has moved between machines.
The demo is a tour of routing, not a filled-in copy of a business, so some dashboard views stay empty.

The terminal after one run of the scenario.
See a filled-in demo
The filled-in demo is the one used for the screenshots on this site. It adds made-up reviews, switched-off schedules and two switched-off workflows. It never connects a real channel. Unlike the plain demo, it needs a built copy of the source code: see Install › Run from source.
- Terminal: in the AgentX source folder, start the demo and leave it running:sh
pnpm docs:demo - Terminal: open a second terminal in the same folder.
- Terminal: add the made-up data:sh
pnpm docs:seed - Browser: open
http://127.0.0.1:18931. The Hub opens. - Browser: select Workflows in the Hub's nav, under Automation. Select Draft the demo shop report, then Open in the editor.
- Browser: select Ask AI to build…, type
Build the demo report workflow, and send it. The demo answers with a fixed example.

Keep the demo between sessions (Docker)
Docker runs programs in a sealed box, called a container. The Docker version of the demo plays the scenario and adds the same made-up data once, then keeps it in a named storage area (a Docker volume) so it's still there next time.
- Terminal: start it:sh
docker compose -f docker-compose.demo.yml up --build -d - Browser: open
http://127.0.0.1:18931. The Hub opens. - Terminal: when you want a fresh demo, remove it and its stored data:sh
docker compose -f docker-compose.demo.yml down -v
Next: follow the annotated workflow walkthrough, then install AgentX to create a real team.
Check it worked
- Browser:
http://127.0.0.1:18931/liveopens the Hub's Live page, with a card for each of the three machines. - The terminal prints
A2A mesh healthy, which means the three demo machines can reach each other. - The scenario ends with a line that starts with
Resolved. That line means the demo worked from start to end. If the run stops before it, copy the line that starts withDemo failed:and theNode logs:line under it into your report.
If something is wrong
npxasksNeed to install the following packages: agentix-cli: answery. It's the download mentioned in step 1.Cannot find module … dist/cli.js: you ran the source version and the source hasn't been built. Runpnpm install, thenpnpm build. Or usenpx agentix-cli demo, which needs no build.Ports … already in use on this machine. Another demo is probably running.: the demo stopped before starting anything. Another demo, or another program, uses its ports. Stop the other demo with Ctrl-C in its terminal, or start this one on other ports withnpx agentix-cli demo --base-port 19021(the dashboard is then on port 19031).AgentX needs Node.js 22.19 or newer, up to 26: the command stopped because this Node.js is too old or too new. Install Node.js 22, check withnode --version, and run it again.- Nothing happens for a minute or two after
npx agentix-cli demo: the first run is downloading the package. Wait;npm warn deprecatedlines along the way are harmless. - The Docker demo shows old data: run
docker compose -f docker-compose.demo.yml down -vto start fresh.
