Skip to main content
ZeroCode uses config.toml for durable settings. Use environment variables for shell-scoped overrides, automation secrets, installer behavior, or diagnostics. This page lists stable public environment variables that ZeroCode reads directly. It does not list internal development variables, test variables, or provider-specific secret names you choose yourself with env_key.

​
Core locations

For more about the files stored under ZEROTWO_HOME, see Config and state locations.

​
Installer variables

These variables apply to the standalone install scripts served from https://zerotwo.ai/zerocode/install.sh and https://zerotwo.ai/zerocode/install.ps1. For unattended installs, set CODEX_NON_INTERACTIVE=1 on the shell that runs the downloaded installer:

​
Authentication and network

For provider API keys, set env_key in the model provider configuration. ZeroCode reads the variable named by that config, so the variable name itself is not a fixed ZeroCode environment variable. For automation secret handling, see Use API key auth. For access token setup, see Access tokens.

​
Diagnostics

RUST_LOG accepts values such as error, warn, info, debug, and trace. It also accepts more targeted Rust logging filters, such as zerocode_core=debug,zerocode_tui=debug. The interactive CLI records diagnostics in bounded local stores by default, but the plaintext zerocode-tui.log file is opt-in. Set log_dir explicitly when you need a plaintext log for troubleshooting:
In non-interactive mode, ZeroTwo desktop runs prints messages inline instead of writing to a separate TUI log file.