#env-variable
Sorted by views, then solution_desc, solution, and root_cause length (desc).
3886 issues
When running `openclaw update`, the **Completion cache update** step produces the following error: ``` Completion cache update failed ([openclaw] Failed to start CLI: Error: qa scenario pack not found: qa/scenarios/index.md at readQaScenarioPack (file:///usr/local/lib/node_modules/openclaw/dist/suite-BW4kSK9C.js:754:27) at readQaScenarioById (file:///usr/local/lib/node_modules/openclaw/dist/suite-BW4kSK9C.js:790:19) at readQaScenarioExecutionConfig (file:///usr/local/lib/node_modules/openclaw/dist/suite-BW4kSK9C.js:795:9) at readRequiredDiscoveryRefs (file:///usr/local/lib/node_modules/openclaw/dist/suite-BW4kSK9C.js:2834:9) at file:///usr/local/lib/node_modules/openclaw/dist/suite-BW4kSK9C.js:2840:39 ```
OpenClaw's OpenRouter provider is not sending the Authorization: Bearer <token> header, causing all requests to fail with 401 authentication errors. Environment • OpenClaw version: 2026.3.13 (61d171a) • OS: Linux (Debian-based) • Node version: v22.22.1 Configuration // ~/.openclaw/openclaw.json "models": { "providers": { "openrouter": { "baseUrl": "https://openrouter.ai/api/v1", "api": "openai-completions", "models": [...] } } }, "auth": { "profiles": { "openrouter:default": { "provider": "openrouter", "mode": "api_key" } } }
The OpenClaw Gateway service fails to install with a systemd error indicating the service unit file does not exist. This affects users attempting to run the gateway as a systemd user service.
The `memory-lancedb-pro` and `memory-openviking` plugins' `config` fields are rejected by OpenClaw's gateway-level config validator with "must NOT have additional properties" error, preventing the gateway from starting when these configs are present in `openclaw.json`.
After upgrading to OpenClaw v2026.3.31 and installing qmd CLI as a backup memory backend, the Gateway continuously reports false positive warnings about qmd collections, even though no qmd collections actually exist in the system.
`openclaw plugins install` still blocks installation on dangerous-code findings even when `--dangerously-force-unsafe-install` is provided. Plugin Github: https://github.com/albertbuchard/forge
After upgrading from 2026.4.2 to 2026.4.5, the bundled `nextcloud-talk` plugin fails to load with: ``` [plugins] nextcloud-talk missing register/activate export [openclaw] Failed to start CLI: PluginLoadFailureError: plugin load failed: nextcloud-talk: plugin export missing register/activate ``` This blocks all CLI commands (`openclaw agent`, `openclaw doctor --fix`, `openclaw plugins disable`, etc.). The gateway daemon itself starts but NC Talk is non-functional.
The `AGENTS.md` template bundled with CrewAI's project scaffolding (`crewai create`) includes a Calculator tool example that uses `eval()` on LLM-provided input, creating a remote code execution vulnerability in every new CrewAI project that follows the template. **Severity**: MEDIUM **Rule**: AGENT-053 — Unsafe Code Execution Pattern in Template **OWASP Agentic Security Index**: ASI-09 — Improper Output Handling **Affected files**: - `lib/crewai/src/crewai/cli/templates/AGENTS.md` (line 773)
When spawning a subagent with `sessions_spawn` using an NVIDIA provider configured as `"api": "openai-completions"`, OpenClaw sends Anthropic-style message content (arrays with `type` objects) instead of OpenAI-style simple strings. This causes the NVIDIA API to reject requests with HTTP 400 errors. bug was created using openclaw *