#during the onboarding wizard i chose Mistral Large Latest LLM Model for the LLM i'm planning to use.

1 messages · Page 1 of 1 (latest)

velvet prawnBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> âś… Mark Solution

urban burrowBOT
#

You don’t need to edit files by hand unless you want to — you can add the Mistral key any time after onboarding.

Where to put the Mistral API key

Mistral auth is just the env var:

  • MISTRAL_API_KEY=sk-...

Best option (especially if the Gateway runs as a service):

  1. Put it in ~/.openclaw/.env on the gateway host:
MISTRAL_API_KEY=sk-...
  1. Restart:
openclaw gateway restart
  1. Verify:
# 
openclaw models status

Alternative (config file): add it to ~/.openclaw/openclaw.json (JSON5):

{
env: { MISTRAL_API_KEY: "sk-..." },
}

Then restart the gateway.

CLI wizard option (no manual edits):

openclaw configure --section model

(or re-run onboarding with openclaw onboard --auth-choice mistral-api-key)

flint horizon
#

I'm getting the following error:
wisam_origin@DESKTOP-QH8BHAQ:~$ openclaw models status
[openclaw] Failed to start CLI: Error: Cannot find module '@mariozechner/clipboard-linux-x64-gnu'
Require stack:

  • /mnt/c/Users/Wisam/AppData/Roaming/npm/node_modules/openclaw/node_modules/@mariozechner/clipboard/index.js
    at Function._resolveFilename (node:internal/modules/cjs/loader:1383:15)
    at defaultResolveImpl (node:internal/modules/cjs/loader:1025:19)
    at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1030:22)
    at Function._load (node:internal/modules/cjs/loader:1192:37)
    at TracingChannel.traceSync (node:diagnostics_channel:328:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:237:24)
    at Module.require (node:internal/modules/cjs/loader:1463:12)
    at require (node:internal/modules/helpers:147:16)
    at Object.<anonymous> (/mnt/c/Users/Wisam/AppData/Roaming/npm/node_modules/openclaw/node_modules/@mariozechner/clipboard/index.js:190:31)
    at Module._compile (node:internal/modules/cjs/loader:1705:14)
    wisam_origin@DESKTOP-QH8BHAQ:~$

I have downloaded openclaw on WSL2 ubuntu 24.04.1 LTS

urban burrowBOT
#

That error isn’t the Mistral API key yet — it’s your OpenClaw CLI install being picked up from Windows (/mnt/c/.../AppData/Roaming/npm/...) while you’re running it inside WSL. The package was installed on Windows, so it doesn’t have the Linux-native dependency (@mariozechner/clipboard-linux-x64-gnu) that WSL expects.

Quick check (run in WSL)

which openclaw
ls -l "$(which openclaw)"

If it points into /mnt/c/Users/Wisam/AppData/Roaming/npm/... → that’s the problem.

Fix

Install OpenClaw inside WSL (Linux), so it pulls the right Linux dependencies:

  1. Make sure you have Node 22+ in WSL:
node -v
#
  1. Install OpenClaw in WSL (pick one):
npm i -g openclaw@latest
# or the installer (also inside WSL):
curl -fsSL https://openclaw.ai/install.sh | bash
  1. Open a new WSL shell (or hash -r) and confirm it now resolves to a Linux path:
which openclaw
openclaw --version
openclaw models status

Then add your Mistral key

In WSL on the gateway host:

  • put MISTRAL_API_KEY=... in ~/.openclaw/.env
flint horizon
#

wisam_origin@DESKTOP-QH8BHAQ:~$ which openclaw
ls -l "$(which openclaw)"
/mnt/c/Users/Wisam/AppData/Roaming/npm/openclaw
-rwxrwxrwx 1 wisam_origin wisam_origin 411 Feb 2 10:55 /mnt/c/Users/Wisam/AppData/Roaming/npm/openclaw
wisam_origin@DESKTOP-QH8BHAQ:~$

urban burrowBOT
#

Yep — that confirms it: you’re running the Windows npm shim from inside WSL (/mnt/c/.../Roaming/npm/openclaw). That’s why the Linux native module is missing.

Fix: install OpenClaw inside WSL (Linux)

In WSL:

  1. Check Node is new enough:
node -v # should be >= 22
npm -v
  1. Install OpenClaw in WSL:
npm i -g openclaw@latest
hash -r