Data & Multi-User
Where Data Lives
All user data is stored in the local user data directory:
| Path | Content |
|---|---|
users/<user id>/sessions/ |
Session records (.jsonl files; multi-user profiles are isolated per user) |
auth.json |
Model provider credentials |
models.json |
Provider and model list |
settings.json |
App settings |
skills/ |
Skills you installed |
| Feature extensions | Plugins you installed |
taskboard/ |
Taskboard data |
cron-jobs.json |
Scheduled task configuration |
scheduler-history.json |
Scheduled task run history (keeps 200 entries) |
desktop/projects.json |
Project list |
| Python runtime | The built-in offline Python |
Multi-User Isolation
When several people share one machine, each user’s data stays fully isolated:
- Switch, create, or delete users from the user area at the bottom of the sidebar
- Switching clears the current state and reloads all data
- Credentials are never shared across users
- The default user (default) cannot be deleted
Archive
Deleting a session archives it by default and keeps its session records on disk; “Permanently delete” on the archive page and project cleanup really remove data and cannot be undone.
Settings → Archived tasks:
- View archived sessions grouped by project
- Restore (move back to the active list) or permanently delete (confirm, then the session records are removed, irreversible)
Data Export
Session messages can be exported as Markdown files (keeping code blocks, tables, and tool-call summaries).
Cleanup
- Taskboard metadata is cleaned up when its project is deleted