~/.relai/config.toml. These
settings apply across repositories for your user account. The file uses TOML;
create it if it does not exist, and keep it private because it can contain an
API key.
Use relai setup --theme light or relai setup --theme dark to change the
terminal theme. Use relai setup and the relai auth commands to manage your
connection and sign-in. Edit the file directly for permission rules and
telemetry preferences.
Terminal theme
Chooselight or dark under [ui]. If no theme is set, RELAI uses light.
Permissions
[permissions] profile sets the default permission profile for agentic CLI
workflows. The default is auto. You can choose auto, accept_edits, or
ask. On commands that expose it, --permissions overrides this setting for that run.
Simulation and optimization do not expose this flag. Resume resolves the profile
again, so repeat a permission override when you need the same boundary.
allow lists restrict access to matching paths. If omitted,
they allow the full workspace; allow = [] allows no paths. deny lists block
matching paths. Patterns use Gitignore-style syntax and are relative to the
repository root. Global allowlists combine with any repository allowlists by
intersection. Global and repository deny rules combine, and deny rules and
built-in protected paths always take precedence.
The repository’s .relai/config.toml can add path rules but cannot set the
profile or loosen global rules. See Permissions for
profile behavior and examples.
Settings managed by RELAI
RELAI also stores connection and sign-in metadata under[api], plus update
check state under [updates]. Manage the connection with relai setup,
relai auth login, and relai auth logout instead of editing those fields.
OAuth tokens are kept as plaintext in the user-only
~/.relai/credentials.json, not in this file. If API-key authentication is
configured, the key is sensitive; do not share or commit either file.