Clawdbot stopped working

[drifting bay]

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

[idle night]

This sounds like an update got stuck mid-rename. The CLI renamed from clawdbot → moltbot → openclaw, so try these commands:

First, check which command works:

moltbot --version
openclaw --version

If moltbot --version works, you should be good! The old clawdbot alias was removed in recent updates.

If neither work, the update may have failed. Since you mentioned the folder is still there:

cd ~/clawdbot && pnpm install && pnpm moltbot --version

Or try reinstalling:

npm install -g moltbot
# or
pnpm add -g moltbot

Let me know what version command works and we can go from there! 🦐

[latent oyster]

Following along before I upgrade. I am still on "clawdbot" version 2026.1.24-3 (885167d)

[idle night]

Good to know! Same version that caused issues. Here's what's happening:

For Tosko: You might want to wait a bit before updating, or at least be ready to use moltbot instead of clawdbot afterward.

For the person with the broken install: The issue is the CLI was renamed. Try these in order:

# Check if moltbot exists
which moltbot
moltbot --version

# Or check npm global install
npm list -g moltbot

# If moltbot isn't found, reinstall
pnpm add -g moltbot

Quick fix if the update broke midway:

cd ~/clawdbot
pnpm install
pnpm run build
pnpm moltbot --version  # use pnpm moltbot to run it directly

Let me know what which moltbot or moltbot --version outputs! 🦐

Got it. Try openclaw directly:

openclaw --version

If that doesn't work, reinstall as openclaw:

pnpm add -g openclaw

The rename chain was: clawdbot → moltbot → openclaw. The update likely got stuck halfway through. Let me know what openclaw --version returns! 🦐

HTTP 500: api_error: unknown error, 520 (1000) (request_id: 05cb8f9932502dccc9d8b902b57a5383)

[latent oyster]

I asked this in #general chat as well and @little viper mentioned he did this and things are off now, not working as intended

#general message

[idle night]

Good catch Tosko! ⚠️

Wait on the reinstall until we know what went wrong with @little viper's install.

@little viper - what exactly went "off"? Did the data not carry over? Config issues? Commands not working? Need details before anyone else reinstalls! 🦐

[idle night]

Found it! The issues people are having:

1. AntDX316: "have to uninstall the old clawdbot before upgrade"
2. skibidi_rizz6769: State dir migration skipped - .openclaw already exists
3. AntDX316: "damn, I have to re-pair everything?"

For @main lance with the broken install:

# 1. Uninstall old version first
pnpm uninstall -g clawdbot moltbot

# 2. Clear state directory conflict (if exists)
rm -rf ~/.openclaw  # or merge manually if you have data there

# 3. Install fresh

pnpm add -g openclaw

# 4. Run - it should auto-migrate from ~/.moltbot
openclaw --version

If you had custom pairings/setup: You may need to re-pair devices after the migration.

@little viper - what specifically broke for you after the reinstall? Just the pairing, or did data not carry over? 🦐

[latent oyster]

This is what @little viper wrote:

"My bot is still running but no I would not say the migration worked smoothly. There is now both a clawdbot and a openclaw command. There seem to be two separate configuration files, rather than one which is a symlink to another. migrations are hard."

And @ OP, careful with this what @idle night suggests doing. You'll lose everything. I dont want my cafefully built setup to be removed and start from scratch, losing memory, crons and everything

[idle night]

Thanks Tosko! That's exactly why we needed to wait.

@little viper's experience shows the migration can leave:

• Duplicate commands (clawdbot + openclaw)
• Split configs instead of unified ones
• General messiness

For @main lance who wants to keep everything:

Your data is in ~/.moltbot/ - back this up first before doing anything:

# Backup your data
cp -r ~/.moltbot ~/.moltbot.backup

# Check what's in there (your memories, crons, config)

ls -la ~/.moltbot/

# Then try to understand what's broken
which clawdbot moltbot openclaw
ls -la ~/.moltbot/
ls -la ~/.openclaw/ 2>/dev/null || echo "No .openclaw folder"

Don't uninstall blindly - that could nuke your memories/crons. We need to figure out:

1. Which command(s) exist and where they point
2. Where your actual config data lives
3. How to merge properly

Can you run those diagnostic commands and share the output? Then we can fix it without losing your setup. 🦐

[latent oyster]

I guess the bot here needs to be migrated too to use the latest knowledge base, lol 😅

[brazen aspen]

After updating the repo to its last version, my pnpm run buil fails with:

pnpm run build

> openclaw@2026.1.29 build /home/baymax/clawd
> pnpm canvas:a2ui:bundle && tsc -p tsconfig.json && node --import tsx scripts/canvas-a2ui-copy.ts && node --import tsx scripts/copy-hook-metadata.ts && node --import tsx scripts/write-build-info.ts


> openclaw@2026.1.29 canvas:a2ui:bundle /home/baymax/clawd
> bash scripts/bundle-a2ui.sh

A2UI bundle up to date; skipping.
src/security/security-wrapper.ts:257:26 - error TS2339: Property 'message' does not exist on type '{}'.

257           if (typeof obj.message === "string") {
                             ~~~~~~~

src/security/security-wrapper.ts:258:17 - error TS2339: Property 'message' does not exist on type '{}'.

258             obj.message = taggedMessage;
                    ~~~~~~~

...
                    ~~~~~~~

src/security/security-wrapper.ts:270:5 - error TS2322: Type 'unknown' is not assignable to type 'ReturnType<T>'.

270     return agentFn(...args);
        ~~~~~~


Found 7 errors in the same file, starting at: src/security/security-wrapper.ts:257

 ELIFECYCLE  Command failed with exit code 2.

[idle night]

The file path doesn't match what I have locally. Based on the error, here's the fix:

Edit line ~255 in src/security/security-wrapper.ts:

Change:

const obj = args[0] as object;

To:

const obj = args[0] as Record<string, unknown>;

Or add a type assertion where obj.message is used:

if (typeof (obj as Record<string, unknown>).message === "string") {
  (obj as Record<string, unknown>).message = taggedMessage;
}

Quick fix for DiegoBot:

# Edit the file around line 255-270
# Find: const obj = args[0] as object;
# Change to: const obj = args[0] as Record<string, unknown>;

# Then rebuild
pnpm run build

The issue is args[0] is being cast to object (which is {} in TypeScript) but you need to cast it to Record<string, unknown> to allow property access. 🦐