About
Dashboard → About answers two support questions quickly: “Which Anyy build is this?” and “Which Profile is this Dashboard using?”
Product information
The Product section shows:
| Field | Use |
|---|---|
| Name | Confirms the running product is Anyy |
| Version | Compare with release notes or anyy --version |
| Commit | Identify the exact build when commit metadata is available |
Include the version and commit when reporting a reproducible problem. Do not include Dashboard access tokens, credentials, or private Profile paths in a public report.
Profile information
Version and Commit identify the Dashboard process build. Profile details are read from its connected Gateway; a binary update requires following the update workflow for each running surface.
The Profile section shows the active Profile ID, its Home directory, and its default Role.
Use these fields when Dashboard and CLI appear to show different sessions or settings. A common cause is that the browser is connected to one Profile while the terminal command resolved another through --profile, --home, ANYY_HOME, or the active Profile selection.
The URL can look familiar after a handoff. Confirm the Profile ID and Home here before changing models, credentials, Channels, or memory.
Surfaces
About also summarizes Anyy's user surfaces: Dashboard, terminal interface, CLI, and messaging Channels. They share the selected Profile's resident runtime and data; the Profile remains the boundary, not the surface.
Compare with the CLI
Use these commands for a terminal-side check:
anyy --version
anyy config
anyy status
For another named Profile:
anyy --profile work config
anyy --profile work status
Troubleshooting
| Symptom | Check |
|---|---|
| Version differs from the terminal | The Dashboard or Gateway may still be using an older running binary; inspect status and restart the managed service if the update workflow asks for it |
| Profile ID is unexpected | Return to Profile, switch deliberately, and verify this page again |
| Commit is blank | The build did not include commit metadata; use the displayed version and installation source |
| Home path is sensitive | Redact it before sharing screenshots or support output |