Environment Variables

Wenlan's normal configuration path is command-driven. Use /init or npx setup for installation, wenlan mcp add for clients, wenlan space for spaces, and wenlan key or wenlan model for optional language features.

Reach for environment variables when you need a temporary override, a scripted run, or a development/eval setup that should not become the default for every session.

WENLAN_SPACE selects the active memory bucket for the current shell or process. WENLAN_HOST points the CLI at a daemon URL when you are not using the default local address.

WENLAN_BIND_ADDR changes where the daemon listens and should stay loopback unless you intentionally expose the daemon in Docker or a VM.

ANTHROPIC_API_KEY is only needed when you opt into daemon-side Anthropic work. The core local memory loop does not require it.

Developers sometimes need a separate port and data directory so a test daemon does not share the same database as the installed product runtime.

Use those overrides deliberately and together. A different port without a different data directory can still point development work at production-like local memory data.

If Windows cannot load the bundled ONNX Runtime library, point ORT_DYLIB_PATH at the onnxruntime.dll inside the Wenlan install directory before starting the daemon.

This is a repair path, not a normal setup step. Start with wenlan doctor when the daemon fails to start.

Eval variables belong to benchmark and maintainer workflows. They control cache location, fixture truncation, and API-backed judge access.

Do not use eval variables to make product claims casually. Public numbers should follow the eval methodology and state run count, fixture, model, and limits.

Main-branch experimental flags are separate from normal runtime configuration. They are for source checkouts, evaluation, and maintainer testing, not routine installed use.

If you set one, record the flag name, git commit, data directory, and whether the feature is released or still on main.

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.