| title | description |
|---|---|
Web Dashboard |
Monitor and manage your agent network through the browser-based dashboard |
The web dashboard provides a real-time interface for monitoring your agent network. View agent presence, message history, spawn agents, and coordinate your team from a central interface.
Start the daemon with the --dashboard flag:
agent-relay up --dashboardThis starts both the relay daemon and the dashboard. By default, the dashboard runs on port 3888:
Dashboard: http://localhost:3888
Specify a different port:
agent-relay up --dashboard --port 3889Or set the environment variable:
export AGENT_RELAY_DASHBOARD_PORT=3889
agent-relay up --dashboardThe main dashboard shows all connected agents in real-time:
- Agent Name - Identifier for each agent
- Status - Online/Offline indicator
- CLI - The AI provider (claude, codex, gemini)
- Last Seen - Timestamp of last activity
- Team - Team assignment (if configured)
The dashboard uses WebSocket connections to provide instant updates:
- New agents appear immediately when they connect
- Status changes reflect within seconds
- Message activity updates live
View the conversation log between agents:
- Filter by agent name or channel
- Search message content
- View full message details
- Track message delivery status
Monitor individual agent output in real-time:
- Click on an agent in the presence view
- Select "View Logs" to open the log panel
- Logs stream live as the agent works
Use the CLI to view logs without the dashboard:
agent-relay agents:logs <agent-name>The coordinator panel provides orchestration controls:
Spawn new worker agents directly from the dashboard:
- Click "Spawn Agent" in the coordinator panel
- Enter agent name and CLI tool
- Provide the initial task description
- Click "Spawn"
Stop agents that have completed their work:
- Select the agent in the presence view
- Click "Release" to gracefully stop the agent
- Confirm the release action
If you have a teams.json configuration, the dashboard shows:
- Team hierarchy view
- Role assignments
- Auto-spawn status
The dashboard exposes a REST API for programmatic access:
curl http://localhost:3888/api/healthResponse:
{
"status": "healthy"
}curl http://localhost:3888/api/agentsResponse:
{
"agents": [
{
"name": "Lead",
"cli": "claude",
"status": "ONLINE",
"lastSeen": "2024-01-15T10:30:00Z"
}
]
}curl -X POST http://localhost:3888/api/send \
-H "Content-Type: application/json" \
-d '{
"to": "Worker1",
"message": "Please review the PR",
"from": "Lead"
}'curl -X POST http://localhost:3888/api/spawn \
-H "Content-Type: application/json" \
-d '{
"name": "Reviewer",
"cli": "claude",
"task": "Review all pending pull requests"
}'curl -X POST http://localhost:3888/api/release \
-H "Content-Type: application/json" \
-d '{
"name": "Reviewer"
}'When running in bridge mode, the dashboard shows cross-project status:
agent-relay bridge ~/project-a ~/project-bThe bridge dashboard displays:
- Connected projects and their status
- Lead agents in each project
- Cross-project message flow
- Reconnection status
See Multi-Project Bridging for details.
| Variable | Description | Default |
|---|---|---|
AGENT_RELAY_DASHBOARD_PORT |
Dashboard port | 3888 |
AGENT_RELAY_DATA_DIR |
Data directory | ~/.local/share/agent-relay |
Dashboard data is stored in the project data directory:
.relay/
agents.json # Agent registry
connected-agents.json # Live connections
messages.db # SQLite message store
worker-logs/ # Agent log files
Run the daemon with automatic restart on crash:
agent-relay up --watchOptions:
--max-restarts <n>- Maximum restarts in 60 seconds (default: 5)
The supervisor will restart the daemon automatically if it crashes, up to the maximum restart limit within the time window.
1. Check if the daemon is running: `agent-relay status` 2. Verify the port is not in use: `lsof -i :3888` 3. Try a different port: `relay-dashboard --port 3890` 4. Ensure relay-dashboard is installed: `npm list -g relay-dashboard` 1. Agents must send a HELLO message to register 2. Check agent logs for connection errors 3. Verify the socket path matches between daemon and agents 1. Check for network issues or firewalls 2. The dashboard auto-reconnects on disconnection 3. Refresh the page if state becomes stale