Skip to main content
Every environment variable Clawboo reads is listed here with its purpose, default, and an example value. Variables not listed here are not consulted by Clawboo. You can set any of these inline before the command or in a .env file in your project root (or wherever your process manager loads it).
This page covers only Clawboo’s own configuration variables. Variables that appear inside marketplace agent templates (FEISHU_*, SUPABASE_*, DATABASE_URL, BETTER_AUTH_SECRET, and similar) are third-party agent content — Clawboo never reads them and they are not documented here.

​
Quick reference

VariableAreaDefaultRead by
CLAWBOO_HOMEState & paths~/.clawbooresolveClawbooDir()
OPENCLAW_STATE_DIRState & paths~/.openclawresolveStateDir()
MOLTBOT_STATE_DIRState & paths— (legacy)resolveStateDir()
CLAWDBOT_STATE_DIRState & paths— (legacy)resolveStateDir()
CLAWBOO_DB_PATHState & paths~/.openclaw/clawboo/clawboo.dbdefaultDbPath() (MCP stdio bins)
CLAWBOO_UI_DIRState & paths<server bundle>/uiserver boot
CLAWBOO_SERVER_PATHState & paths(auto-discovered)CLI dev-fallback
CLAWBOO_MCP_BIN_DIRState & paths(set by CLI)GET /api/mcp/config
CLAWBOO_API_PORTPorts & binding18790 (auto-scan)resolveApiPort()
CLAWBOO_API_PORT_STARTPorts & binding18790resolveApiPort()
PORTPorts & binding—resolveApiPort() (production only)
HOSTPorts & binding127.0.0.1resolveHost()
HOSTNAMEPorts & binding127.0.0.1resolveHost() fallback
STUDIO_ACCESS_TOKENSecrets & auth—access gate
CLAWBOO_SECRETS_MASTER_KEYSecrets & authauto-generated key filesecrets vault
ANTHROPIC_API_KEYRuntime keys—resolveRuntimeKey()
OPENAI_API_KEYRuntime keys—resolveRuntimeKey()
OPENROUTER_API_KEYRuntime keys—resolveRuntimeKey()
OLLAMA_BASE_URLRuntime keyshttp://localhost:11434/v1Native runtime
CLAWBOO_REVIEWER_MODELRuntime tuning(builder’s model)executor verification
LOG_LEVELLogginginfo@clawboo/logger
NODE_ENVLogging— (pretty transport)@clawboo/logger
CLAWBOO_BOARD_STALE_TTL_MSOperational tuning3600000 (60 min)board stale-task sweep
CLAWBOO_BOARD_STALE_SWEEP_MSOperational tuning300000 (5 min)board stale-task sweep
CLAWBOO_APPROVAL_TTL_MSOperational tuning86400000 (24 h)approval reaper
CLAWBOO_APPROVAL_REAPER_INTERVAL_MSOperational tuning3600000 (1 h)approval reaper
CLAWBOO_MCP_PROBE_MSOperational tuning60000 (60 s)MCP liveness supervisor
CLAWBOO_ROUTINE_OPENCLAW_TIMEOUT_MSOperational tuning600000 (10 min)scheduled dispatch watchdog
OTEL_EXPORTER_OTLP_ENDPOINTOpenTelemetry—OTel bridge gate
OTEL_EXPORTER_OTLP_TRACES_ENDPOINTOpenTelemetry—OTel bridge gate
OTEL_SERVICE_NAMEOpenTelemetryclawbooOTel tracer resource
There are no feature-flag environment variables. Every subsystem (board, executors, worktrees, MCP, verification, governance, observability) is always on. The only opt-in surface is the OpenTelemetry export bridge, gated by the presence of an OTLP endpoint variable.

​
How to set variables

Inline, before the command: 
CLAWBOO_API_PORT=19000 HOST=0.0.0.0 STUDIO_ACCESS_TOKEN=mysecret npx clawboo
Via a .env file (loaded by your process manager or a tool like dotenv): 
# .env
CLAWBOO_API_PORT=19000
HOST=0.0.0.0
STUDIO_ACCESS_TOKEN=mysecret
LOG_LEVEL=debug

​
State & paths

​
Ports & binding

Setting HOST to a non-loopback address (0.0.0.0, a LAN IP, or a hostname) without also setting STUDIO_ACCESS_TOKEN exposes the dashboard and every /api/* route to your network with no authentication. Clawboo logs a prominent SECURITY: warning at boot in this case but does not block it. See Security.

​
Secrets & auth

STUDIO_ACCESS_TOKEN is explicitly blocklisted from being passed to spawned runtime subprocess environments, alongside GATEWAY_AUTH_TOKEN, CLAWBOO_SECRETS_MASTER_KEY, and any BETTER_AUTH_* key. Untrusted agents never inherit these values.

​
Runtime provider keys

These variables are resolved through the credential chain resolveRuntimeKey(envVar): process.env → the encrypted vault → OpenClaw’s ~/.openclaw/.env. Setting a key in your process environment is the highest-priority way to satisfy a runtime’s credential check.
Codex authenticates via interactive ChatGPT OAuth (codex login), not a pasted API key, so there is no provider-key environment variable for it. See Codex runtime.

​
Runtime tuning

​
Logging

​
Operational tuning

These variables tune the always-on background services that start at server boot. Each is parsed as a positive number of milliseconds and falls back to its default when missing or invalid.

​
OpenTelemetry

The OpenTelemetry export bridge is the only opt-in subsystem in Clawboo. Without these variables, the always-on local event log is the trace store and the OpenTelemetry SDK is never imported. When an endpoint is configured, the SDK is lazily loaded and traces are exported via OTLP.

​
See also

  • Configuration reference — settings.json schema, state directory, and the OpenClaw token-resolution chain
  • CLI reference — npx clawboo and the MCP stdio binaries
  • Connecting runtimes — install, connect, and the encrypted credential vault
  • Security — access gate, loopback binding, vault, and redaction
  • Deployment — ports, fallback, state directory, and the bundled server
  • Observability — the event log and the OTel bridge