TypeError: Cannot read properties of undefined (reading 'trim') | Friends of the Crustacean 🦞🤝 | Page 1

somber palm Apr 15, 2026, 1:47 AM

#

had this messege after i hit enter at discord channels allowlist
i only pasted one channel's ID

frank shardBOT Apr 15, 2026, 1:57 AM

#

One channel ID should be valid, yes.

I checked the Discord allowlist resolver, and a bare channel ID is supposed to work, so this looks like a bug in the setup flow, not bad input.

Can you paste:

openclaw --version

Workarounds for now:

Use guild:<SERVER_ID>/<CHANNEL_ID> instead of only the channel ID
Or allowlist the whole server first with guild:<SERVER_ID>
Or set it directly in config:

#

  channels: {
    discord: {
      groupPolicy: "allowlist",
      guilds: {
        "SERVER_ID": {
          channels: {
            "CHANNEL_ID": { enabled: true },
          },
        },
      },
    },
  },
}

Docs:

#

If you’re already on the latest version and it still blows up, that’s issue-worthy: https://github.com/openclaw/openclaw/issues

sweet prawn Apr 15, 2026, 2:14 AM

#

oh my I have the same problem but haven't found the ansswer

frank shardBOT Apr 15, 2026, 2:14 AM

#

Yep, this looks real, not just you.

A single Discord channel ID should be accepted. Right now it looks like the setup wizard is choking on that input path.

Current workaround:

use guild:<SERVER_ID>/<CHANNEL_ID> instead of only the channel ID, or
edit config directly:

{
  channels: {
    discord: {
      groupPolicy: "allowlist",
      guilds: {
        "SERVER_ID": {
          channels: {

#

            "CHANNEL_ID": { enabled: true },
          },
        },
      },
    },
  },
}

Can you both paste:

openclaw --version

Docs:

https://docs.openclaw.ai/channels/discord

#

https://docs.openclaw.ai/cli/configure

If this is still happening on the latest version, it should be filed here: https://github.com/openclaw/openclaw/issues

sweet prawn Apr 15, 2026, 2:15 AM

#

has anyone issued this on github from yesterday ?

frank shardBOT Apr 15, 2026, 2:16 AM

#

Yep, looks like there is already one from yesterday:

issue: https://github.com/openclaw/openclaw/issues/66848
fix PR opened today: https://github.com/openclaw/openclaw/pull/66882

The issue title is generic, not Discord-specific, but it looks like the same TypeError: Cannot read properties of undefined (reading 'trim') wizard/setup crash family.

If you want, paste your:

openclaw --version

and I can tell you whether you’re likely hitting that exact regression.

somber palm Apr 15, 2026, 2:43 AM

#

frank shard Yep, looks like there is already one from yesterday: - issue: <https://github.c...

OpenClaw 2026.4.14 (323493f)
i tried type server ID and channel ID together too still not working

frank shardBOT Apr 15, 2026, 2:44 AM

#

Yep, that version lines up with the regression.

If 2026.4.14 still crashes with serverId/channelId, then the wizard is probably the broken part, not your input format.

Best workaround right now is to bypass the wizard and edit the config directly:

{
  channels: {
    discord: {
      groupPolicy: "allowlist",
      guilds: {
        "YOUR_SERVER_ID": {
          channels: {
            "YOUR_CHANNEL_ID": { enabled: true },
          },

#

        },
      },
    },
  },
}

Then restart the gateway.

Docs:

If you want, paste your channels.discord block here with the token removed/redacted, and I’ll sanity-check it.

sweet prawn Apr 15, 2026, 3:30 AM

#

can I use a previous version of openclaw though

frank shardBOT Apr 15, 2026, 3:30 AM

#

Yes, you can, but I wouldn’t make rollback the first move unless you know a specific good version.

My recommendation:

Best short-term: stay on 2026.4.14 and bypass the broken wizard by editing the Discord config manually
If you really want to roll back: pin an older version, then run Doctor and restart the gateway

For a global install, that’s:

pnpm add -g openclaw@<version>
openclaw doctor
openclaw gateway restart

Docs:

https://docs.openclaw.ai/install/updating

#

One warning: downgrades can sometimes get weird with config/state migrations, so manual config is the safer workaround unless we know the exact last-good version for this bug.

If you want, I can help you pick the least risky option:

manual config now
rollback
wait for the fix PR to land

sweet prawn Apr 15, 2026, 3:32 AM

#

I'm gonna just use the previous one, right before this version

frank shardBOT Apr 15, 2026, 3:33 AM

#

That’s reasonable.

After the downgrade, I’d do:

openclaw doctor
openclaw gateway restart

That makes sure the service and current install are aligned.

If the previous version fixes it, please post which version worked, that’ll help a lot for everyone hitting this same bug.

sweet prawn Apr 15, 2026, 3:33 AM

#

so, what's the previous version ?

frank shardBOT Apr 15, 2026, 3:33 AM

#

Looks like the previous published stable is 2026.4.12.

There doesn’t seem to be a 2026.4.13 release in between.

If you want to pin that version:

pnpm add -g openclaw@2026.4.12
openclaw doctor
openclaw gateway restart

If that fixes it, please report back, that’ll help confirm the regression window.

sweet prawn Apr 15, 2026, 3:42 AM

#

I wanna install from the start version 4.12 though

frank shardBOT Apr 15, 2026, 3:43 AM

#

Yep, you can start directly on 2026.4.12.

If you’re doing a fresh global install with pnpm:

pnpm add -g openclaw@2026.4.12
pnpm approve-builds -g
openclaw onboard --install-daemon
openclaw --version

A small gotcha: changing the installed version does not wipe your existing ~/.openclaw state/config. So it’s a fresh code install, not automatically a fresh state install.

If you want, I can also tell you the safest way to make it truly clean without nuking anything by accident.

sweet prawn Apr 15, 2026, 3:43 AM

#

well I reinstall Ubuntu. So joke's on you

frank shardBOT Apr 15, 2026, 3:44 AM

#

Okay, fair, you win 😅

Yep, that definitely counts as a clean start.

In that case, just install 2026.4.12 directly:

pnpm add -g openclaw@2026.4.12
pnpm approve-builds -g
openclaw onboard --install-daemon
openclaw --version

If you hit anything weird during onboard, paste it here and I’ll help untangle it.

sweet prawn Apr 15, 2026, 3:49 AM

#

I wanna install, pnpm not recognized

frank shardBOT Apr 15, 2026, 3:50 AM

#

If pnpm isn’t recognized, try this first:

corepack enable
pnpm --version

If that works, then install 2026.4.12:

pnpm add -g openclaw@2026.4.12
pnpm approve-builds -g
openclaw onboard --install-daemon

If corepack is also missing, then Node isn’t set up yet. In that case you need Node first, docs here:
https://docs.openclaw.ai/install

#

If you want, paste the output of:

node --version
corepack --version

and I’ll tell you the next exact step.

sweet prawn Apr 15, 2026, 3:54 AM

#

npm install -g openclaw@2026.4.12
openclaw onboard --install-daemon, is this okay ?

frank shardBOT Apr 15, 2026, 3:54 AM

#

Yep, that should be fine.

I’d just add a quick version check in between:

npm install -g openclaw@2026.4.12
openclaw --version
openclaw onboard --install-daemon

If openclaw --version prints 2026.4.12, you’re good to continue.

If npm trips over a sharp build error, use:

SHARP_IGNORE_GLOBAL_LIBVIPS=1 npm install -g openclaw@2026.4.12

sweet prawn Apr 15, 2026, 4:12 AM

#

curl -fsSL https://openclaw.ai/install.sh | bash . Can I change the version after this though ?

#TypeError: Cannot read properties of undefined (reading 'trim')