Dashboard
Dashboard is Anyy's visual interface. Use it to chat, check runtime health, and operate the capabilities configured in the current Profile.
This page explains how to open and navigate Dashboard. Each capability has one canonical page under Features or Messaging Platforms.
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.
Access Token and Browser Session Lifetime
The token printed in a Dashboard URL is a one-time claim token. It expires after 10 minutes and is consumed by the first successful browser claim. The browser then receives an HttpOnly Dashboard session cookie valid for 24 hours or until the Dashboard process stops.
Opening an already claimed or expired URL cannot create another browser session. Run anyy dashboard again to issue a fresh URL. A valid browser cookie is scoped to /dashboard/; it does not authenticate arbitrary Gateway RPC or another Dashboard process.
Dashboard and Gateway Lifetimes
Dashboard is an on-demand web 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 | Loses its runtime connection | Stops |
Check or stop Dashboard from another terminal:
anyy dashboard --status
anyy dashboard --stop
Navigate Dashboard
The sidebar provides these work areas:
| Area | Use it for | Learn the capability |
|---|---|---|
| Chat | Start, resume, steer, and monitor conversations | Conversations & Sessions |
| Overview | Check setup, runtime health, recent activity, and usage | This page |
| Roles | Create and select assistant identities | Roles & Personality |
| Memory | Review and maintain durable personal context | Persistent Memory |
| Models | Configure providers and model routes | Models & Providers |
| Channel | Connect and diagnose messaging accounts | Messaging Platforms |
| MCP | Connect external MCP servers and choose exposed tools | MCP Integration |
| Skills | Inspect and manage reusable instruction packages | Skills System |
| Tools | Inspect tool governance and capability backends | Tools & Toolsets |
| Cron | Create and inspect scheduled work | Scheduled Automations |
| Profile | Create or switch isolated Anyy homes | Profiles |
| Approvals | Review pending authorization and decision history | Approvals & ChangePlans |
| About | Confirm the build, active Profile, Home, and default Role | Confirm the active runtime |
The language selector changes Dashboard's interface language. It does not translate conversation content or change the documentation language.
Read 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.
Confirm the Active Runtime
Open About when you need to answer “Which Anyy build is running?” or “Which Profile is this Dashboard using?”
The page shows:
| Field | Why it matters |
|---|---|
| Product name | Confirms that the running product is Anyy |
| Version | Compare with release notes or anyy --version |
| Commit | Identifies the exact build when commit metadata is available |
| Profile ID and Home | Confirms the data and configuration boundary |
| Default Role | Confirms the identity used for new sessions |
About also summarizes Anyy's user surfaces: Dashboard, terminal interface, CLI, and messaging Channels. They share the selected Profile's runtime and data; the Profile is the boundary, not the surface.
Use these values when Dashboard and CLI appear to show different sessions or settings. Compare them with:
anyy --version
anyy config
anyy status
Include version and commit in a reproducible bug report. Redact access tokens, credentials, and private Home paths.
Profile and Home Scope
Dashboard is bound to the Profile/Home selected when it starts. Start another Profile explicitly:
anyy --profile work dashboard
Or select a Home directly:
anyy dashboard --home /path/to/anyy-home
If sessions or settings appear missing, confirm About → Profile and compare it with:
anyy config
anyy profile list
Local-Network Access
The default 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 another trusted device needs access. Dashboard does not turn the temporary token URL into a public, internet-hardened deployment.
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 choose 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, over 10 minutes old, 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 |
| CLI and Dashboard show different data | Compare the Profile ID and Home on About with anyy config |
Version differs from anyy --version | Dashboard or Gateway may still be running an older binary; inspect status and follow the update workflow's restart guidance |
| Commit is blank | The build did not include commit metadata; use its version and installation source |
| Another device cannot connect | Check the printed LAN URL, listener address, and host firewall; do not expose Dashboard directly to the public internet |
Continue with Conversations & Sessions or Models & Providers.