Config
Environment Variables
Know which Wenlan environment variables are normal configuration, which are development-only, and which belong to eval or Windows repair paths.
At a glance
01
Look up process-scoped overrides for Space selection, networking, data isolation, and runtime repair.
02
Set a variable in the affected process environment before starting it.
01
Use commands first
Variables apply to the process receiving them. Set daemon variables before starting the daemon and client variables before launching the client; restarting the affected process applies changes.
02
Normal runtime overrides
Set these in the environment of the affected process before launching it. Restart that process after changes.
- WENLAN_SPACE: unset by default; pins a Space for the client process.
- WENLAN_HOST: CLI daemon URL; default http://127.0.0.1:7878.
- WENLAN_BIND_ADDR: daemon listen address; default 127.0.0.1 with the configured port. A non-loopback address exposes the API beyond the machine.
- ANTHROPIC_API_KEY: optional Anthropic provider key; no default. Set it for the process using the provider.
03
Development isolation
Set both overrides before starting a source checkout. A separate port alone does not isolate data; restart the daemon for changes to take effect.
- WENLAN_PORT: daemon port; default 7878.
- WENLAN_DATA_DIR: daemon data root; unset by default, using the platform data location.
WENLAN_PORT=7879 WENLAN_DATA_DIR=/tmp/wenlan-test cargo run -p wenlan-server04
Windows runtime repair
ORT_DYLIB_PATH selects the ONNX Runtime library. When unset, the normal runtime loader is used. If Windows reports a library loading error, set it to the bundled onnxruntime.dll before starting the daemon.
05
Eval variables
Evaluation runs have separate cache, fixture, and judge settings. Consult the evaluation guide and record the settings used in a comparison.
06
Experimental flags
Experimental switches and their release status are documented separately.
07
Security boundary
Environment variables can change where Wenlan listens, where it stores data, and which provider keys it can use. Treat those values like operational configuration, not copy-paste snippets.
Never publish a shell transcript that includes API keys, private data paths, or a non-loopback daemon address you did not mean to expose.
Next
Connect MCP Clients
Connect Claude Code, Codex, Cursor, Claude Desktop, Gemini CLI, Muse Code, ChatGPT, Claude.ai, Muse, and other MCP clients to Wenlan.
Read next