Dashboard
This page covers using the dashboard. To extend or build dashboard pages, see the developer guide.
The dashboard is an on-demand browser sidecar for the resident Anyy gateway. It is not a separate cloud service. It connects to the selected profile's gateway over the Unix RPC socket and uses a temporary claim token for browser access.
Start Dashboard
Start the resident gateway first:
anyy gateway start
Then start the dashboard:
anyy dashboard
Default listen address:
127.0.0.1:8767
Interactive terminal runs open the URL in the default browser unless --no-open
is set.
Useful flags:
| Flag | Meaning |
|---|---|
--home PATH | Select an Anyy home. |
--socket PATH | Connect to a non-default gateway socket. |
--listen ADDR | Bind a custom HTTP listen address. |
--no-open | Print the URL without opening a browser. |
The dashboard refuses to start if the selected gateway reports a different home or profile than the CLI selected.
LAN Mode
LAN mode exposes the dashboard to trusted devices on the same private network:
anyy dashboard lan
anyy dashboard --lan
LAN mode discovers private IPv4 addresses on active LAN interfaces, skips common
VPN/container/bridge interfaces, binds port 8767, and prints one tokenized URL
per address.
Do not share LAN dashboard URLs. They include temporary access tokens.
Pages
Overview
Runtime summary for the selected profile and gateway.
Chat
Create sessions, open threads, send messages, stop a running turn, and stream chat updates through dashboard SSE.
Models
View and edit the main model, fallback entries, provider connection details, and media model slots such as image generation, TTS, and speech-to-text. Model tests run through gateway RPC.
Channels
View channel status and configure supported messaging channels. Some channels have specialized flows such as Weixin login.
Skills
Inspect skills, toggle visibility, install uploaded skills, and remove managed skills.
Tools
Inspect runtime toolsets and tool descriptors. The dashboard can edit resource limits such as timeout and output budgets, but it does not directly edit core security policy fields.
MCP
List MCP servers, inspect discovered tools, add or edit server config, toggle servers, probe config, and inspect individual MCP tool details.
Cron
List scheduled jobs, create jobs, inspect run history, edit schedule/prompt, pause/resume, and delete jobs.
Memory
View profile USER.md and MEMORY.md, plus memory suggestion state when the
runtime exposes it.
Roles
List roles, select the default role, create named roles, edit SOUL.md, rename
roles, and delete roles that are not actively referenced.
Approvals
Review open and decided approvals. Open prompts can be approved or denied from the browser session.
Claim Token
Dashboard URLs include a fragment token:
http://127.0.0.1:8767/dashboard/#t=<token>
The browser claims a dashboard session using that token. After claim, pages require the browser session. If no valid session exists, the server redirects to the claim shell.
Dashboard responses use no-store headers. POST actions check same-origin before changing state.
Lifecycle Commands
anyy dashboard --status
anyy dashboard --stop
--status lists running dashboard processes. --stop stops them.
If port 8767 is already in use, use lifecycle commands to inspect the existing
dashboard or choose another listen address:
anyy dashboard --listen 127.0.0.1:8777
Troubleshooting
| Symptom | Check |
|---|---|
| Gateway is not running | Start the resident gateway, then run anyy dashboard again. |
| Profile mismatch | Confirm --home, --profile, and the running gateway point to the same profile. |
| Port in use | Run anyy dashboard --status, anyy dashboard --stop, or choose another --listen. |
| Browser did not open | Use the printed URL manually or pass --no-open. |
| LAN URL does not work | Try the URL matching the client device's network; firewalls can still block port 8767. |