Environment variables
TraseAI pulls environment variables from multiple sources. The rule is never override existing values.Precedence (highest → lowest)
- Process environment (what the Gateway process already has from the parent shell/daemon).
.envin the current working directory (dotenv default; does not override).- Global
.envat~/.traseai/.env(aka$TRASEAI_STATE_DIR/.env; does not override). - Config
envblock in~/.mk-rcp/traseai.json(applied only if missing). - Optional login-shell import (
env.shellEnv.enabledorTRASEAI_LOAD_SHELL_ENV=1), applied only for missing expected keys.
Config env block
Two equivalent ways to set inline env vars (both are non-overriding):
Shell env import
env.shellEnv runs your login shell and imports only missing expected keys:
TRASEAI_LOAD_SHELL_ENV=1TRASEAI_SHELL_ENV_TIMEOUT_MS=15000
Env var substitution in config
You can reference env vars directly in config string values using${VAR_NAME} syntax:
Path-related env vars
| Variable | Purpose |
|---|---|
TRASEAI_HOME | Override the home directory used for all internal path resolution (~/.traseai/, agent dirs, sessions, credentials). Useful when running TraseAI as a dedicated service user. |
TRASEAI_STATE_DIR | Override the state directory (default ~/.traseai). |
TRASEAI_CONFIG_PATH | Override the config file path (default ~/.mk-rcp/traseai.json). |
TRASEAI_HOME
When set, TRASEAI_HOME replaces the system home directory ($HOME / os.homedir()) for all internal path resolution. This enables full filesystem isolation for headless service accounts.
Precedence: TRASEAI_HOME > $HOME > USERPROFILE > os.homedir()
Example (macOS LaunchDaemon):
TRASEAI_HOME can also be set to a tilde path (e.g. ~/svc), which gets expanded using $HOME before use.