The dashboard
The dashboard is the AgentX website that runs on your own machine. You use it in a browser to see what agents are doing and to change settings. It is a separate program from the daemon (the AgentX background service that actually runs the agents), so the dashboard can load while the daemon is stopped.
Its home is the Hub: every task a person gave an agent is a post, with its thread, and beside the feed you see what each machine runs now.
There is no login on the computer itself
The dashboard trusts every browser on the computer it runs on. It asks for no password there. Anyone who can use that computer can open the dashboard, change settings and answer approvals. Lock the computer when you step away: that is what keeps others out. A dashboard token (dashboard.token) doesn't change this, because pages opened on the computer carry it. Other devices can't reach the dashboard unless you share it: see Open the dashboard through your own web address. With a token set, a browser on another device signs in with the token once, and its pages never carry the token: see Sign in from another device.
Open it
- Browser: go to the address printed by
agentx setup. It is normallyhttp://127.0.0.1:4202. The Hub opens; its own address is/hub. - Pick a page in the nav on the left. On a phone, the nav is a bar at the bottom, and More opens the other pages.
If nothing loads, start the dashboard yourself:
- Terminal: from the folder that holds
agentx.json, run:shagentx board serve - Keep that terminal open, and open the address again.

Scripted demo data; your team's names and machines will differ.
Where things are
The nav starts with Hub and Needs you. The other pages sit in groups, each under a small grey heading. The number next to a page counts what is on it; the page you are on is in bold.
| Page | What to look for |
|---|---|
| Hub | Every open task as a post, with its thread. Feed and List switch the view |
| Needs you | Posts that wait on your answer |
| Work | |
| Jobs | Every piece of assigned work, with one status line each |
| Live | Sessions and jobs running now, paused tasks, and each machine's card |
| Running now | One card per connected machine with what it runs at this moment |
| Projects | One card per project, with its open, blocked and closed work |
| Activity | The runs your agents made, newest first, with their outcome |
| Automation | |
| Schedules | Recurring jobs on each machine, today's totals and their value line |
| Workflows | Saved workflows, their last run, and the editor |
| Reviews | Classifications waiting for a review |
| Failures | Failed runs, scheduled jobs and workflow runs in the last 24 hours |
| Fleet | |
| Agents | Every agent, with its role and its posts this week |
| People | Who talks to the agents, their machines and what they asked for |
| Org | The org chart: who reports to whom |
| Cost | What the agents spent, per agent and per day, and monthly caps |
| Owner | |
| Settings | Agents, channels, schedules and the machines' health, for the owner only |

Select a post to open it on its own, with its thread; select a running task to watch and steer it (see Watch and steer a run). Light / dark, at the bottom of the nav, switches the colours. Some pages stay empty until the matching app (for example GitLab) is connected.
A few tools keep a page of their own: the workflow history and follow-ups, the wiki and the first-run setup. The dashboard map lists every address.
See which version is running
The right of each page's title (under the title on a phone) shows the daemon's version, its commit (the exact state of the source code it was built from) and when it started, in your time zone.

The daemon runs version 0.182.0, built from commit 4f2c9a1, and a newer version waits on disk.
When the AgentX files on disk were rebuilt or upgraded after the daemon started, the line adds Restart pending. Hover over it to read why: the code on disk is newer than the running daemon. The daemon keeps running the old code until it restarts. Select Restart pending to open the Live page, where Restart when idle is on each machine's card, or run agentx daemon restart --when-idle in a terminal (restart without losing work). The line refreshes every minute. If the dashboard cannot ask the daemon, the last answer stays, marked as of its time.
The badge looks at the folder the daemon was started from. If you install each release into a new folder and then point the service at it, a release waiting in the new folder does not show the badge.
This is the daemon the dashboard is attached to (dashboard.daemonUrl). For the full picture, with the last restart and how often the daemon restarts, run agentx daemon status.
Talk to your agents
Give an agent a task from the box at the top of the Hub's feed (see Post a task), or comment on a post. You can also talk to them through AgentX Voice, the voice assistant for your Mac, or the OpenCode terminal UI.
To open the dashboard through your own web address, see Open the dashboard through your own web address.
Check it worked
- Browser: open
http://127.0.0.1:4202. The Hub opens, with the nav on the left. - Select Agents in the nav. Your agents are listed. If Running now shows your machines as up, the dashboard can reach the daemon.
- The right of the page's title shows a version and "since" with a date. Terminal:
agentx daemon statusnames the same version on its first line.
If something is wrong
- The page doesn't load: the dashboard isn't running. Start it with
agentx board serve, or runagentx setupagain. - The page loads but shows no agents: the daemon is stopped or unreachable. Terminal: run
agentx daemon status. See It's not answering. - Every page stops answering for seconds at a time, the teammate page and the phone app included: one database read is holding the dashboard, which serves all of them. Read the output of
agentx board serve(its terminal, or the log file of the service that starts it) for a line containingslow query. It gives the time taken and the query, for any read of 200 ms or longer. Report that line. No such line means the cause is elsewhere. - The page looks out of date after an update: the dashboard is a separate program. Stop it and start it again.
- The title row shows no version: the dashboard can't reach the daemon, or the daemon is older than this page. Terminal: run
agentx daemon status. - The title row shows Restart pending: the daemon is running older code than what is installed. Restart it when no task is running:
agentx daemon restart --when-idle. - You changed the port: the address uses
dashboard.portfromagentx.jsoninstead of4202.
