Configuration Overview
Xenocept stores all of its state — sessions, screenshots, settings, destinations — inside a single AeorDB-backed file (xenocept.aeordb). The paths described below are paths inside that file, not paths on your real filesystem.
Edit through the Settings UI in the desktop app, or via the HTTP endpoints listed below.
Where the Database Lives
| Platform | Path |
|---|---|
| Linux | (depends on Tauri’s resolved app-data dir, typically under ~/.local/share/xenocept/) |
| macOS | ~/Library/Application Support/<Xenocept-app-id>/ |
| Windows | %APPDATA%\<Xenocept-app-id>\ |
The exact directory is resolved by Tauri’s app_data_dir at startup ( around the state_store initialization). The Settings UI in the running app is the authoritative source of the actual path on your system.
The Three Config Documents
Inside the AeorDB store:
| Path | Concern |
|---|---|
/config/settings.json | User-facing settings (hotkey, autostart, screenshot export path/template). See Settings. |
/config/destinations.json | Configured destinations (recipients of submitted sessions). See Destinations. |
/config/auto-send-destinations.json | Which destinations auto-send on Submit, plus a master enable flag. |
HTTP Endpoints For Config
| Endpoint | Method | Purpose |
|---|---|---|
/api/v1/settings | GET / POST | Read or overwrite settings.json |
/api/v1/destinations | GET / POST | List or create destinations |
/api/v1/destinations/{id} | PUT / DELETE | Update or delete a destination |
/api/v1/auto-send | GET / PUT | Read or update the auto-send config |
The HTTP Server Itself
When Xenocept starts, it spawns its HTTP server on:
http://127.0.0.1:9500
Both the host and the port are hardcoded. There is no server configuration block in settings.json. The MCP channel-mode CLI accepts a --port flag, but that flag tells the channel server which port the running Xenocept GUI listens on (defaulting to 9500) — it does not change the listening port.