#OpenClaw config web dashboard is too heavy for my PC.

1 messages · Page 1 of 1 (latest)

radiant knoll
#

Although I'm running on a i5 10400 and have plenty of available RAM, it lags so much. How to reduce this lag or configure Discord accounts through CLI?

gentle orioleBOT
alpine cradleBOT
#

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

fleet cragBOT
#

First, paste:

openclaw --version

If it’s mainly the web dashboard / Control UI that feels heavy, I’d just skip it for setup and use the CLI. Discord can be configured fully from there.

If by “Discord accounts” you mean Discord bot accounts, yes.

Default Discord bot

export DISCORD_BOT_TOKEN="..."
openclaw config set channels.discord.token --ref-provider default --ref-source env --ref-id DISCORD_BOT_TOKEN
openclaw config set channels.discord.enabled true --strict-json
openclaw gateway restart
#

Or shorter:

openclaw channels add --channel discord --token "$DISCORD_BOT_TOKEN"

Add another Discord bot account

openclaw channels add --channel discord --account work --name "Work Bot" --token "$DISCORD_WORK_BOT_TOKEN"
openclaw config set channels.discord.defaultAccount default

Check status

openclaw channels list
openclaw channels status --probe
#

Approve DM pairing

openclaw pairing list discord
openclaw pairing approve discord <CODE>
# or for a named account:
openclaw pairing approve discord <CODE> --account work

If you use multiple agents, bind the account too

openclaw agents bind --agent main --bind discord:default
openclaw agents bind --agent work --bind discord:work

Docs:

radiant knoll
#

How to get schema working in VSCode so I can edit openclaw.json directly?

fleet cragBOT
#

Yep, easiest way is to use the live schema from your installed OpenClaw.

openclaw --version
openclaw config file
openclaw config schema > ~/.openclaw/openclaw.schema.json

Then in VSCode add this to .vscode/settings.json:

{
  "files.associations": {
    "**/openclaw.json": "jsonc"
  },
  "json.schemas": [
# 
    {
      "fileMatch": ["**/openclaw.json"],
      "url": "file:///home/YOUR_USER/.openclaw/openclaw.schema.json"
    }
  ]
}

Then validate after edits:

openclaw config validate

Two gotchas:

#
  • openclaw.json is JSON5, so VSCode schema support is usually happiest if you keep it close to JSONC style, especially quoted keys.
  • If you regenerate/update OpenClaw, rerun openclaw config schema > ~/.openclaw/openclaw.schema.json so VSCode gets the current schema.

Docs:

If you want, paste your OS + openclaw --version and I can give you the exact VSCode path snippet for your machine.

radiant knoll
# 
$ref '/$defs/route' in 'file:///home/wh1te/.openclaw/openclaw.schema.json' can not be resolved.
fleet cragBOT
#

Yeah, that looks like a schema bug, not you messing up VSCode.

I checked the generated schema, and the current one has broken plugin refs under webhooks / qqbot, so VSCode chokes on them.

Workaround: generate a VSCode-only schema with those broken plugin entries removed.

openclaw --version
openclaw config schema > ~/.openclaw/openclaw.vscode.schema.json

node - <<'NODE'
const fs = require('fs');
const p = process.env.HOME + '/.openclaw/openclaw.vscode.schema.json';
const s = JSON.parse(fs.readFileSync(p, 'utf8'));

const entries = s?.properties?.plugins?.properties?.entries?.properties;
# 
if (entries) {
  delete entries.webhooks;
  delete entries.qqbot;
}

fs.writeFileSync(p, JSON.stringify(s, null, 2));
console.log('Wrote', p);
NODE

Then point VSCode at:

{
  "files.associations": {
# 
    "**/openclaw.json": "jsonc"
  },
  "json.schemas": [
    {
      "fileMatch": ["**/openclaw.json"],
      "url": "file:///home/wh1te/.openclaw/openclaw.vscode.schema.json"
    }
  ]
}

That keeps schema help working for the rest of openclaw.json, you just lose autocomplete/validation for those 2 plugin blocks.

Also still run: