Configure the CLI
Configuration file
Section titled “Configuration file”UseTrawsn stores configuration under ~/.usetrawsn/config.toml by default.
usetrawsn config showusetrawsn config get <key>usetrawsn config set <key> <value>usetrawsn config unset <key>Common settings:
| Key | Purpose | Default |
|---|---|---|
endpoint |
UseTrawsn server URL | UseTrawsn production API |
auto_update |
Check CLI updates on launch | true |
feedback |
Enable direct feedback commands | true |
Custom config directory
Section titled “Custom config directory”Use USETRAWSN_CONFIG_DIR when the home directory is read-only, ephemeral, or intentionally isolated:
export USETRAWSN_CONFIG_DIR=./.usetrawsnusetrawsn statusRelative paths are resolved to absolute paths. The directory contains CLI state, credentials or keyring fallback data, and update markers. Do not commit it.
Endpoint override
Section titled “Endpoint override”Set the endpoint for one command:
usetrawsn --endpoint https://example.internal statusOr persist it:
usetrawsn config set endpoint https://example.internalMachine-readable output
Section titled “Machine-readable output”Commands write one final JSON document to stdout. Use normal shell redirection or jq; do not wrap MCP stdio with scripts that print banners to stdout.