Profiles

Dashboard → Profile manages Anyy's data and runtime boundaries. Each Profile has an independent Home, Workspace, sessions, memory, credentials, models, Roles, Channels, Skills, MCP configuration, schedules.

Understand the Profile list

The page shows every Profile known under the selected Profile root. Each card includes its display name, ID, Home path, update time, and runtime state:

State	Meaning
Current runtime	This Dashboard is connected to that Profile
Running	Another resident runtime currently owns the Profile
Stopped	No live runtime was detected
Default	The base Profile; it cannot be deleted

Open a card to view its full Home path and the actions currently allowed.

Create a Profile

1. Select New Profile.
2. Enter an ID such as work.
3. Optionally add a display name such as Work.
4. Select Create.

IDs contain lowercase letters, digits, dashes, or underscores, start with a letter or digit, and are at most 64 characters. Reserved command names are rejected.

A fresh Profile receives its own directory layout, Workspace, empty user and memory files, default Role selection, and configuration. Durable runtime state is created when that Profile is first used by the runtime.

Switch Dashboard to another Profile

Open a non-current Profile and select Start and switch or Switch to. Dashboard shows the handoff stages while it:

1. selects the target Profile;
2. starts or finds its Gateway runtime; and
3. binds Dashboard to the target Profile's data.

After the handoff, the browser redirects to the target Dashboard. The visible sessions, models, memory, Channels, Skills, MCP servers, Cron jobs all change with the Profile.

Switching is not migration

Dashboard does not copy any data between Profiles. Return to the previous Profile to see its sessions and settings again.

Stop another Profile

A running, non-current Profile can be stopped from its detail page. Stopping ends that resident runtime but leaves all Profile data on disk.

Stop a Profile before deletion or when it should no longer consume resident resources. The current Dashboard runtime cannot stop itself from this page. To stop the target from a terminal, use anyy --profile NAME gateway stop; there is no profile stop subcommand.

Delete a Profile

Deletion is available only when the target is not:

• the current Dashboard Profile;
• the default Profile;
• the active sticky selection; or
• running.

Dashboard submits a forced deletion that also purges Profile Secrets, then removes the entire Profile Home. This includes sessions, Workspace files, memory, configuration, Skills, Channels, schedules, credentials, and runtime state.

Back up before removal

Profile deletion is permanent. Create and verify a backup before deleting any Profile whose data may be needed again.

When to use a Role instead

Create another Role when you want a different assistant identity but intentionally share sessions, memory, credentials, and tools. Create another Profile when those resources must remain separate.

Troubleshooting

Problem	Check
New Profile ID is rejected	Use a non-reserved lowercase ID with only digits, -, or _
Switch stops at a handoff stage	Check the target Home and Gateway health with anyy --profile NAME status
Delete action is missing	Switch away, change the active Profile if needed, and stop the target runtime
Data appears to have disappeared after switching	Confirm the Profile shown on Dashboard → About

Restore a Profile archive with the backup CLI; this page does not import or merge Profile directories.

See Profiles for the matching CLI workflow and resolution rules.