Reference
Commands, config files, environment variables and exit codes, generated from the code.
This section is the exact reference: every page in it is generated from turno's code by a script, and CI fails when one is out of date, so it cannot drift from what the CLI does.
The CLI carries the same reference: turno --help groups the commands, turno <command> --help explains each, and turno help environment, turno help exit-codes and turno help json print the topics.
turno mcp sync --helpUsage:
turno mcp sync [profile...] [--dry-run] [--force]
write gateway entries into every profile config
Examples:
$ turno mcp syncFiles
| Path | What |
|---|---|
~/.config/turno/config.toml | profiles and folder rules |
~/.config/turno/mcp.toml | MCP servers behind the gateway |
~/.config/turno/accounts.toml | service accounts for the accounts bridge |
~/.local/state/turno/ | usage, run records, logs (with the tool call log logs/calls.jsonl), backups, the gateway tokens |
~/.local/share/turno/ | installed servers, tool cache, browser identities |
All three honor XDG_CONFIG_HOME, XDG_STATE_HOME and XDG_DATA_HOME. turno config path prints where each file lives on your machine.
How these pages are made
apps/docs/scripts/generate.mjs in the turno repository writes them: it runs the built CLI in a throwaway HOME for the help text, reads the command registry, the known config keys, the exit code table and the checks of turno doctor from the source, and compares the mcp.toml keys the parser reads with the documented ones. Troubleshooting is generated the same way, one page per finding of turno doctor.