Configuration & Storage
Data directory
Section titled “Data directory”Lattis keeps its state under the platform data directory:
| Platform | Path |
|---|---|
| macOS | ~/Library/Application Support/lattis |
| Linux | ~/.local/share/lattis |
| Windows | %APPDATA%\lattis |
Contents
Section titled “Contents”| Entry | What it is |
|---|---|
config.json | Theme, host/port, default agent, MCP servers, agent/code-exec settings, GUI panel sizes. |
pane_layouts.json | Per-branch tiled workspace layouts — panes, tabs, and focus. |
review_sessions.json | Per-branch code review state — viewed marks and draft comment threads. |
accounts.json | Named cloud and local accounts per provider. |
remote_auth.json | Cloud credentials (mode 0600 on Unix). |
chats/ | Saved conversations and their artifacts. |
skills/ | Your global Skills. |
telemetry.db | SQLite usage store; usage survives daemon restarts. |
daemon.log | Daemon output when launched on login. |
Network
Section titled “Network”- The API listens on
127.0.0.1:5288by default. The host and port are configurable. - On a loopback bind the API is unauthenticated, on the assumption that only local processes can reach it.
- On a non-loopback bind the daemon refuses to start without an auth token.
Set
LATTIS_AUTH_TOKEN(orauth_tokenin config) and sendAuthorization: Bearer <token>. See Headless & Remote Hosts for the trade-offs — including why an SSH tunnel is usually the better choice.
Environment variables
Section titled “Environment variables”| Variable | Effect |
|---|---|
LATTIS_DATA_DIR | Relocate the whole data dir (config, telemetry, logs, state). |
LATTIS_PORT | Override the API port. |
LATTIS_AUTH_TOKEN | Bearer token required for a non-loopback bind. Persisted once set. |
LATTIS_API_KEY | Lattis API key, so a headless daemon can report usage without a browser sign-in. |
LATTIS_ORG_ID | Pin the organization a headless daemon attributes usage to. Optional — the daemon discovers your organizations from the key. |
LATTIS_TELEMETRY_API_BASE | Point the daemon at a different Lattis backend. |
Running multiple instances
Section titled “Running multiple instances”Setting LATTIS_DATA_DIR and LATTIS_PORT per checkout lets several instances
run side by side with separate state and ports — useful when working across
multiple worktrees. Run lattisd doctor to print which directories, ports, and
binaries the daemon resolves from the current environment.
Themes
Section titled “Themes”Two hand-tuned Lattis themes plus a range of built-in themes (Dracula, Nord, Tokyo Night, Catppuccin, Gruvbox, Kanagawa, and more), switchable live from Settings.
If something isn’t behaving, see Troubleshooting.