11 replies

During onboarding no LLM info asked.

✅Solved

I have just installed a fresh Debian Linux on my VM, went to https://docs.openclaw.ai/start/getting-started and did these steps:
* Installed Node v24
* Ran

curl -fsSL https://openclaw.ai/install.sh | bash

curl -fsSL https://openclaw.ai/install.sh | bash

* I was automatically transferd to onboarding, went through Quickstart.

Issue

During the onboarding I wasn't asked about setting up LLM Api. After onboarding I was defaulted to claude-opus-4-6. I tried

openclaw onboard --reset

openclaw onboard --reset

but went through the same steps which skipped LLM Api configuration.

openclaw.json

openclaw.json

doesn't contain any info on which LLM api to use.

"agents": {
    "defaults": {
      "workspace": "/home/parallels/.openclaw/workspace",
      "compaction": {
        "mode": "safeguard"
      },
      "maxConcurrent": 4,
      "subagents": {
        "maxConcurrent": 8
      }
    }
  },

"agents": {
    "defaults": {
      "workspace": "/home/parallels/.openclaw/workspace",
      "compaction": {
        "mode": "safeguard"
      },
      "maxConcurrent": 4,
      "subagents": {
        "maxConcurrent": 8
      }
    }
  },

How should I setup LLM Api now?

Solution

openclaw configure --section models

openclaw configure --section models

Or the more direct auth command:

openclaw models auth add

openclaw models auth add

Docs:
- https://docs.openclaw.ai/cli/configure
- https://docs.openclaw.ai/cli/models

3) If you’re running the Gateway as a service: prefer

~/.openclaw/.env

~/.openclaw/.env

A common gotcha is: you export an API key in your shell, but systemd doesn’t inherit it.

Jump to solution

FotC�

Friends of the Crustacean 🦞🤝•4w ago•

11 replies

MrLms

During onboarding no LLM info asked.

✅Solved

I have just installed a fresh Debian Linux on my VM, went to https://docs.openclaw.ai/start/getting-started and did these steps:
* Installed Node v24
* Ran

curl -fsSL https://openclaw.ai/install.sh | bash

curl -fsSL https://openclaw.ai/install.sh | bash

* I was automatically transferd to onboarding, went through Quickstart.

Issue

During the onboarding I wasn't asked about setting up LLM Api. After onboarding I was defaulted to claude-opus-4-6. I tried

openclaw onboard --reset

openclaw onboard --reset

but went through the same steps which skipped LLM Api configuration.

openclaw.json

openclaw.json

doesn't contain any info on which LLM api to use.

"agents": {
    "defaults": {
      "workspace": "/home/parallels/.openclaw/workspace",
      "compaction": {
        "mode": "safeguard"
      },
      "maxConcurrent": 4,
      "subagents": {
        "maxConcurrent": 8
      }
    }
  },

"agents": {
    "defaults": {
      "workspace": "/home/parallels/.openclaw/workspace",
      "compaction": {
        "mode": "safeguard"
      },
      "maxConcurrent": 4,
      "subagents": {
        "maxConcurrent": 8
      }
    }
  },

How should I setup LLM Api now?

Solution

openclaw configure --section models

openclaw configure --section models

Or the more direct auth command:

openclaw models auth add

openclaw models auth add

Docs:
- https://docs.openclaw.ai/cli/configure
- https://docs.openclaw.ai/cli/models

3) If you’re running the Gateway as a service: prefer

~/.openclaw/.env

~/.openclaw/.env

A common gotcha is: you export an API key in your shell, but systemd doesn’t inherit it.

Jump to solution

During onboarding no LLM info asked.

Issue

3) If you’re running the Gateway as a service: prefer
`~/.openclaw/.env`
`~/.openclaw/.env`

Similar Threads

During onboarding no LLM info asked.

Issue

3) If you’re running the Gateway as a service: prefer
`~/.openclaw/.env`
`~/.openclaw/.env`

Similar Threads

Similar Threads

Similar Threads

During onboarding no LLM info asked.

Issue

3) If you’re running the Gateway as a service: prefer ~/.openclaw/.env~/.openclaw/.env

Similar Threads

During onboarding no LLM info asked.

Issue

3) If you’re running the Gateway as a service: prefer ~/.openclaw/.env~/.openclaw/.env

Similar Threads

Similar Threads

Similar Threads

3) If you’re running the Gateway as a service: prefer
`~/.openclaw/.env`
`~/.openclaw/.env`

3) If you’re running the Gateway as a service: prefer
`~/.openclaw/.env`
`~/.openclaw/.env`