> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wednesdayai.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Environment Variables

# Environment variables

WednesdayAI pulls environment variables from multiple sources. The rule is **never override existing values**.

## Precedence (highest → lowest)

1. **Process environment** (what the Gateway process already has from the parent shell/daemon).
2. **`.env` in the current working directory** (dotenv default; does not override).
3. **Global `.env`** at `~/.openclaw/.env` (aka `$OPENCLAW_STATE_DIR/.env`; does not override).
4. **Config `env` block** in `~/.openclaw/openclaw.json` (applied only if missing).
5. **Optional login-shell import** (`env.shellEnv.enabled` or `OPENCLAW_LOAD_SHELL_ENV=1`), applied only for missing expected keys.

If the config file is missing entirely, step 4 is skipped; shell import still runs if enabled.

## Config `env` block

Two equivalent ways to set inline env vars (both are non-overriding):

```json5 theme={"dark"}
{
  env: {
    OPENROUTER_API_KEY: "sk-or-...",
    vars: {
      GROQ_API_KEY: "gsk-...",
    },
  },
}
```

## Shell env import

`env.shellEnv` runs your login shell and imports only **missing** expected keys:

```json5 theme={"dark"}
{
  env: {
    shellEnv: {
      enabled: true,
      timeoutMs: 15000,
    },
  },
}
```

Env var equivalents:

* `OPENCLAW_LOAD_SHELL_ENV=1`
* `OPENCLAW_SHELL_ENV_TIMEOUT_MS=15000`

## Runtime-injected env vars

WednesdayAI also injects context markers into spawned child processes:

* `OPENCLAW_SHELL=exec`: set for commands run through the `exec` tool.
* `OPENCLAW_SHELL=acp`: set for ACP runtime backend process spawns (for example `acpx`).
* `OPENCLAW_SHELL=acp-client`: set for `wednesdayai acp client` when it spawns the ACP bridge process.
* `OPENCLAW_SHELL=tui-local`: set for local TUI `!` shell commands.

These are runtime markers (not required user config). They can be used in shell/profile logic
to apply context-specific rules.

## Env var substitution in config

You can reference env vars directly in config string values using `${VAR_NAME}` syntax:

```json5 theme={"dark"}
{
  models: {
    providers: {
      "vercel-gateway": {
        apiKey: "${VERCEL_GATEWAY_API_KEY}",
      },
    },
  },
}
```

See [Configuration: Env var substitution](https://docs.wednesdayai.dev/next/admin/gateway/configuration.md#env-var-substitution-in-config) for full details.

## Secret refs vs `${ENV}` strings

WednesdayAI supports two env-driven patterns:

* `${VAR}` string substitution in config values.
* SecretRef objects (`{ source: "env", provider: "default", id: "VAR" }`) for fields that support secrets references.

Both resolve from process env at activation time. SecretRef details are documented in [Secrets Management](https://docs.wednesdayai.dev/next/admin/gateway/secrets.md).

## Path-related env vars

| Variable | Purpose |
| - | - |
| `OPENCLAW_HOME` | Override the home directory used for all internal path resolution (`~/.openclaw/`, agent dirs, sessions, credentials). Useful when running WednesdayAI as a dedicated service user. |
| `OPENCLAW_STATE_DIR` | Override the state directory (default `~/.openclaw`). |
| `OPENCLAW_CONFIG_PATH` | Override the config file path (default `~/.openclaw/openclaw.json`). |
| `OPENCLAW_PROFILE` | Active profile, as set by `--profile <name>` (`--dev` sets `dev`). Scopes the state dir to `~/.openclaw-<name>` and the default workspace to `~/.openclaw/workspace-<name>`. |

## Logging

| Variable | Purpose |
| - | - |
| `OPENCLAW_LOG_LEVEL` | Override log level for both file and console. One of `silent`, `fatal`, `error`, `warn`, `info` (default), `debug`, `trace`, least to most verbose. Takes precedence over `logging.level` and `logging.consoleLevel` in config. Invalid values are ignored with a warning. |

## Media understanding provider keys

Audio transcription, image description and video understanding providers ship as extensions that
are **disabled by default**. Enabling one is not enough on its own; it also needs a credential.
Each provider reads its own variable:

| Variable | Provider |
| - | - |
| `OPENAI_API_KEY` | OpenAI |
| `ANTHROPIC_API_KEY` | Anthropic |
| `GEMINI_API_KEY` / `GOOGLE_API_KEY` | Google Gemini (either works) |
| `GROQ_API_KEY` | Groq |
| `DEEPGRAM_API_KEY` | Deepgram |
| `MISTRAL_API_KEY` | Mistral (Voxtral) |
| `ELEVENLABS_API_KEY` | ElevenLabs |
| `DEEPINFRA_API_KEY` | DeepInfra |
| `OPENROUTER_API_KEY` | OpenRouter |
| `MOONSHOT_API_KEY` | Moonshot |
| `MINIMAX_API_KEY` | MiniMax |
| `ZAI_API_KEY` | Z.ai |
| `BIFROST_API_KEY` | Bifrost (proxy) |

A provider whose key resolves nowhere is **skipped** during auto-detection rather than attempted,
so a missing key looks like the provider was never tried. Third-party provider extensions declare
their own variables the same way. Full resolution order and troubleshooting:
[Media understanding](https://docs.wednesdayai.dev/next/users/nodes/media-understanding.md).

## Plugin and skill catalogs

| Variable | Default | Purpose |
| - | - | - |
| `OPENCLAW_CATALOG_URL` | `https://raw.githubusercontent.com/ExpansionX/WednesdayAI-plugins/main/catalog.json` | Override the remote plugin catalog URL (operator mirror / airgap pinning) |
| `OPENCLAW_CATALOG_TTL_MS` | `3600000` (1 hour) | Remote catalog cache TTL in milliseconds (0 is rejected — falls back to default) |
| `OPENCLAW_CATALOG_REMOTE` | unset (enabled) | Set to `"0"` to disable all remote catalog fetching (airgap / mirror mode) |
| `OPENCLAW_SKILLS_CATALOG_URL` | `https://raw.githubusercontent.com/ExpansionX/WednesdayAI-skills/main/catalog.json` | Override the remote skills catalog URL used by `wednesdayai skills install <id>` |

`OPENCLAW_CATALOG_REMOTE=0` disables **all** remote catalog fetching, plugins and skills alike;
each feed then falls back to its bundled offline snapshot. Catalog feeds cache in memory for the
TTL and fail open on any fetch error.

### `OPENCLAW_HOME`

When set, `OPENCLAW_HOME` replaces the system home directory (`$HOME` / `os.homedir()`) for all internal path resolution. This enables full filesystem isolation for headless service accounts.

**Precedence:** `OPENCLAW_HOME` > `$HOME` > `USERPROFILE` > `os.homedir()`

**Example** (macOS LaunchDaemon):

```xml theme={"dark"}
<key>EnvironmentVariables</key>
<dict>
  <key>OPENCLAW_HOME</key>
  <string>/Users/kira</string>
</dict>
```

`OPENCLAW_HOME` can also be set to a tilde path (e.g. `~/svc`), which gets expanded using `$HOME` before use.

## Related

* [Gateway configuration](https://docs.wednesdayai.dev/next/admin/gateway/configuration.md)
* [FAQ: env vars and .env loading](https://docs.wednesdayai.dev/next/users/help/faq.md#env-vars-and-env-loading)
* [Models overview](https://docs.wednesdayai.dev/next/developers/concepts/models.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.