Dashboard Overview
Dashboard is Anyy's visual control surface. It combines chat, runtime status, models, Channels, Roles, memory, Tools, Skills, MCP, Cron, and Profiles in one local web interface.
Start Dashboard
Run:
anyy dashboard
Dashboard needs the resident Gateway. If no Gateway is reachable in an interactive terminal, Anyy shows Gateway required and asks whether to start it. Accepting installs and starts the background service when necessary, waits for readiness, and continues.
By default, Anyy prints:
- a This machine URL; and
- Local network URLs for usable network interfaces.
An interactive run opens the This machine URL in your browser. To print the URLs without opening a browser:
anyy dashboard --no-open
To bind exactly one address instead of the automatic listeners:
anyy dashboard --listen 127.0.0.1:8767
Each startup URL contains a temporary access token. Do not share it, place it in logs, or include it in screenshots. Open the URL only in a browser you control.
Dashboard and Gateway Lifetimes
Dashboard is an on-demand sidecar; Gateway is the resident assistant runtime.
| Action | Dashboard | Gateway service |
|---|---|---|
Press Ctrl+C in the Dashboard terminal | Stops the web listener | Keeps running |
| Close the browser tab | Keeps running until its terminal stops | Keeps running |
anyy dashboard --stop | Stops running Dashboard processes | Keeps running |
anyy gateway stop | Dashboard loses its runtime connection | Stops |
Check or stop Dashboard from another terminal:
anyy dashboard --status
anyy dashboard --stop
Navigation
The Dashboard sidebar is organized around everyday work:
| Area | What it controls |
|---|---|
| Chat | Conversations, background sessions, attachments, model/reasoning selection and clarifications |
| Overview | Setup summary, runtime state, schedules, token usage, recent sessions, MCP, and Skills |
| Roles | Assistant identities and their Soul instructions |
| Memory | Durable personal context managed by Anyy |
| Models | Main model, ordered fallbacks, and image/video/voice routes |
| Channel | Messaging accounts, connection setup, policies, and health |
| MCP | External MCP servers and exposed tools |
| Skills | Installed Skills and their enabled state |
| Tools | Built-in tools and web, image, video, and voice backends |
| Cron | Scheduled assistant jobs |
| Profile | Separate Anyy homes and the active Profile |
| About | Runtime and product information |
The language selector in the sidebar changes Dashboard's own interface language. It does not translate conversation content or change the documentation language.
The Overview Page
Open Overview for a quick health and activity check. It shows:
- selected Profile, default Role, configured Channels, and main model;
- next scheduled Cron job;
- active sessions, scheduled task count, state database size, and heartbeat freshness;
- 7-day or 30-day input/output token totals and turn counts;
- recent conversations; and
- configured MCP servers and Skills.
After changing a Profile, model, Channel, Skill, MCP server, or Cron job, return to Overview and confirm that the active runtime reflects the expected setup.
Local-Network Access
The default Dashboard command advertises addresses reachable on the machine and local network. Availability depends on host networking and firewall rules.
For a personal single-machine setup, prefer an explicit loopback listener:
anyy dashboard --listen 127.0.0.1:8767
Use a LAN address only when you need another trusted device to connect. Dashboard does not turn the temporary token URL into a public, internet-hardened deployment.
Profiles and Homes
Dashboard is bound to the Profile/Home selected when it starts. Start another Profile explicitly:
anyy --profile work dashboard
or:
anyy dashboard --home /path/to/anyy-home
If sessions or settings appear missing, compare Dashboard's Profile with:
anyy config
anyy profile list
Troubleshooting
| Problem | Fix |
|---|---|
| Gateway required | Accept the prompt, or run anyy gateway start and retry |
Port 8767 is in use | Run anyy dashboard --status, stop an old process, or select another --listen port |
| Browser did not open | Copy the printed This machine URL, or rerun without --no-open in an interactive terminal |
| Token is invalid or already used | Run anyy dashboard again and use the newly printed URL |
| Dashboard loads but data is unavailable | Run anyy status and anyy doctor; the Gateway or selected Profile may be unhealthy |
| Another device cannot connect | Check the printed LAN URL, the listener address, and the host firewall; do not expose Dashboard directly to the public internet |
Continue with Dashboard Chat or Dashboard Models.