Storage & privacy
Everything Briglia knows lives in three folders in your home directory. Nothing is sent anywhere except to the providers you configured, and one command removes it all.
Where things live
| Path | Contents |
|---|---|
~/.config/briglia/ | user-editable configuration: secrets.json (mode 0600, multi-process safe), mcp.json, mcp-routing.json, agents/ (your subagent definitions), skills/<name>/SKILL.md (hot-reloaded skills) |
~/.local/share/briglia/ | state: conversation, long-term archive, logs, images and documents received, projects, reminders and watcher scripts, trigger events, subagent sessions, the release trust floor, the app-chat socket, the userdata toolchain |
~/Documents/Briglia/ | landing zone: files Briglia receives, downloads or generates for you |
Paths follow the XDG convention (honouring XDG_CONFIG_HOME / XDG_DATA_HOME) and are distinct from the macOS Ada.app's, so both can coexist on one Mac.
What leaves your machine
- Your messages, attachments and the results of Briglia's tool calls go to the model provider you chose (OpenCode, OpenRouter, your endpoint, or nowhere if it is a local server), plus OpenAI for voice/OCR/images if configured, Serper and Jina for web research, and your email provider if enabled.
- Briglia has no telemetry, no analytics, no accounts. Updates are fetched from GitHub Releases.
- Secrets are injected into commands only when a tool needs them, and command output is redacted of known secret values before the model sees it.
Skills, agents and MCP
Extend Briglia without touching code: drop a SKILL.md package in ~/.config/briglia/skills/<name>/ (agentskills.io format; user skills override bundled ones of the same name), define subagents as Markdown in ~/.config/briglia/agents/, and register MCP servers in mcp.json (/restart reloads it).
Delete everything
/deleteuserdataAsks for confirmation, then: stops all running work (Bash jobs, subagents, watchers), revokes and removes connected email credentials (AgentMail key, gws OAuth tokens) and cached email/calendar data, deletes memory, documents, reminders and the rest of the state, sweeps stragglers and reports honestly if anything could not be removed. LLM, web and image keys stay so Briglia can still start; server-side mailboxes are never touched.
/setname changes what Briglia calls you (two-step, with confirmation). Briglia also builds a small learned persona over time; it is part of what /deleteuserdata removes and what a Mind export carries.