Configuration
Anyy configuration belongs to a Profile. Each Profile has its own model routes, channels, tools, schedules, credentials, workspace, and state.
Recommended Ways to Change Settings
| Change | Recommended surface |
|---|---|
| Initial setup | anyy setup |
| Models and credentials | Dashboard → Models or anyy setup model |
| Channels | Dashboard → Channels or anyy setup channel |
| Web, browser, image, and voice capabilities | Dashboard → Tools |
| Roles, skills, MCP, and cron | Their Dashboard section |
| Inspect the resolved configuration | anyy config |
anyy config is read-only. It reports the resolved Profile, paths, provider/model selection, and credential-reference health without printing secret values.
Dashboard and setup commands validate changes, protect credentials, and reload the live runtime where supported. Direct YAML editing is useful for advanced recovery, but it skips those guided checks.
Profile Layout
The active Profile home contains the canonical user data for that Profile. Important paths include:
| Path | Purpose |
|---|---|
config.yaml | Non-secret settings and credential references |
secrets/ | Anyy-managed secret material |
state.db | Sessions, messages, jobs, audit, and other durable state |
memory/USER.md | Durable user facts and preferences |
memory/MEMORY.md | Durable assistant memory |
objects/ | Content-addressed durable payloads referenced by canonical state |
workspace/ | Context files and user-produced working files |
skills/ | Installed Profile-local skills |
roles/ | Profile-local Role definitions |
Do not treat workspace/ as a security boundary. A tool still follows its own policy, approvals, and execution limits.
Which Profile Is Active?
anyy status
anyy config
To inspect another named Profile:
anyy --profile work config
Commands that accept --home PATH can target an explicit Profile directory. Avoid mixing --profile, --profile-root, and ad-hoc --home values unless you are deliberately diagnosing path resolution.
Credentials
Configuration stores references to credentials rather than the secret value. Dashboard and setup commands write supported keys under the Profile's secrets/ directory with restricted permissions.
Replace, clear, connect, or disconnect credentials through the same feature surface that created them. Never paste secrets into chat prompts, screenshots, shell history, or support bundles.
Applying Changes
Many Dashboard and setup operations reload the affected runtime after a successful write. Channel changes can also be applied explicitly:
anyy channel reload
If a change is saved but behavior has not changed, check:
anyy status
anyy doctor
anyy gateway status
Restart the Gateway only when the feature's remediation asks for it or a live reload cannot complete.
Back Up Before Manual Editing
anyy backup create
By default, secrets are excluded. Add --include-secrets only when the archive will be protected like a credential store. See Backup & Restore.
Troubleshooting
| Symptom | Check |
|---|---|
| A setting appears unchanged | Confirm the active Profile and inspect anyy config |
| Gateway still uses old values | Run the relevant reload action, then inspect anyy status |
| Configuration validation fails | Use the Dashboard form or setup wizard to identify the invalid field |
| Credential is configured but unresolved | Replace it from the owning Models, Tools, or Channels page |
| Hand-edited YAML prevents startup | Restore the last valid file or restore a backup into a new Profile |