ZeroTrace Companion
Settings Overview
Every Companion setting, organised by category.
Open settings with Ctrl+, (or via the menu). Settings are organised into five categories.
Categories
| Category | What it covers |
|---|---|
| Appearance | Window behaviour, theme, content protection |
| Connection | Default port, baud rate, auto-reconnect, custom device profiles |
| Terminal | Font size, line wrap, history limit |
| AI | Model server, model selection, system prompt |
| Privacy | Telemetry confirmation, data-storage paths, local-data management |
All settings persist across launches in a local file under your application data directory.
Where settings are stored
| Platform | Location |
|---|---|
| Windows | %APPDATA%\ZeroTrace Companion\zerotrace-settings.json |
| macOS | ~/Library/Application Support/ZeroTrace Companion/zerotrace-settings.json |
| Linux | ~/.config/zerotrace-companion/zerotrace-settings.json |
The file is plain JSON. You can back it up, copy it to another machine, or version-control it if you want to.
For team setups where everyone uses the same custom-firmware profile or the same model selection, copying zerotrace-settings.json to each team member's machine is the fastest way to share configuration.
Resetting settings
Two ways:
- Reset to defaults in the settings UI — preserves the file but restores defaults.
- Delete the settings file — Companion creates a fresh default file on next launch.
Use the second option if Companion seems stuck or misconfigured in ways the in-app reset does not fix.
What is not in settings
A few things deliberately not exposed in settings:
- AI model contents — managed by Ollama / your runner, not by Companion.
- Per-device firmware settings — those are on the device itself; manage via the dashboard or the Web UI.
- Operating-system permissions — Companion can't grant itself OS-level access; you handle those externally.