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

vernal juniper Apr 15, 2026, 1:33 AM

#

On the setup after clicking skip for channel I got TypeError: Cannot read properties of undefined (reading 'trim')

white tinselBOT Apr 15, 2026, 1:37 AM

#

I’m checking the onboarding path that handles “skip channel” so I can give you something more useful than a guess.

#

Skipping channels should be valid, so that looks like a bug, not you.

Can you paste these?

openclaw --version
openclaw status --all

And if you have it, the full stack trace after the reading 'trim' error.

I’ve seen similar trim crashes come from stale session/bootstrap state, especially on older builds, but I want to confirm your version first before suggesting a cleanup/reset.

Docs:
https://docs.openclaw.ai/help/faq
https://docs.openclaw.ai/gateway/troubleshooting

vernal juniper Apr 15, 2026, 1:39 AM

#

x@x-Mini ~ % openclaw --version
OpenClaw 2026.4.14 (323493f)
x@x-Mini ~ % openclaw status --all

🦞 OpenClaw 2026.4.14 (323493f) — I'm like tmux: confusing at first, then suddenly you can't live without me.

│
OpenClaw status --all

Overview
┌─────────────────┬────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Item │ Value │
├─────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Version │ 2026.4.14 │
│ OS │ macos 26.4 (arm64) │
│ Node │ 22.22.2 │
│ Config │ ~/.openclaw/openclaw.json │
│ Dashboard │ http://127.0.0.1:18789/ │
│ Tailscale │ off │
│ Channel │ stable (default) │
│ Update │ pkg │
│ Gateway │ local · ws://127.0.0.1:18789 (local loopback) · unreachable │
│ Security │ Run: openclaw security audit --deep │
│ Gateway self │ unknown │
│ Gateway service │ LaunchAgent not installed │
│ Node service │ LaunchAgent not installed │
│ Agents │ 0 total · 0 bootstrapping · 0 active · 0 sessions │
│ Secrets │ none │
└─────────────────┴────────────────────────────────────────────────────────────────────────────────────────────────────┘

Channels
┌──────────┬─────────┬────────┬────────────────────────────────────────────────────────────────────────────────────────┐
│ Channel │ Enabled │ State │ Detail │
├──────────┼─────────┼────────┼────────────────────────────────────────────────────────────────────────────────────────┤
└──────────┴─────────┴────────┴────────────────────────────────────────────────────────────────────────────────────────┘

Agents
┌────────────┬────────────────┬──────────┬──────────┬──────────────────────────────────────────────────────────────────┐
│ Agent │ Bootstrap file │ Sessions │ Active │ Store │
├────────────┼────────────────┼──────────┼──────────┼──────────────────────────────────────────────────────────────────┤
└────────────┴────────────────┴──────────┴──────────┴──────────────────────────────────────────────────────────────────┘

Diagnosis (read-only)

Gateway connection details:
Gateway target: ws://127.0.0.1:18789
Source: local loopback
Config: /Users/x/.openclaw/openclaw.json
Bind: loopback

✗ Config: /Users/x/.openclaw/openclaw.json
✓ Secret diagnostics (0)
✓ Restart sentinel: none
✓ Port 18789
! Tailscale: off · unknown
✓ Plugin compatibility (none)
! Channel issues skipped (gateway unreachable)

Gateway health:
gateway unreachable

white tinselBOT Apr 15, 2026, 1:40 AM

#

That helps, thanks. I’m checking the gateway troubleshooting path, because your status output points more to “gateway never came up” than to channel setup itself.

#

Thanks, this helps a lot.

Your version looks current enough. The bigger problem in that output is this part:

Gateway: unreachable
LaunchAgent not installed
0 agents / 0 sessions

So I don’t think “skip channel” is the real blocker. It looks more like setup exited before the gateway actually came up.

Try this first:

openclaw gateway run

If you want the background service path instead, rerun onboarding with:

#

openclaw onboard --install-daemon

If openclaw gateway run throws the same trim error, please paste:

openclaw gateway status
openclaw logs --follow

The first 20 to 30 log lines after the failure should be enough.

Docs:
https://docs.openclaw.ai/help/faq
https://docs.openclaw.ai/gateway/troubleshooting
https://docs.openclaw.ai/start/onboarding

vernal juniper Apr 15, 2026, 1:48 AM

#

xx@xx-Mini ~ % openclaw gateway status
openclaw logs --follow

🦞 OpenClaw 2026.4.14 (323493f)
If it's repetitive, I'll automate it; if it's hard, I'll bring jokes and a rollback plan.

│
◇
Service: LaunchAgent (not loaded)
File logs: /tmp/openclaw/openclaw-2026-04-15.log

Config (cli): ~/.openclaw/openclaw.json (missing)
Config (service): ~/.openclaw/openclaw.json (missing)

Gateway: bind=loopback (127.0.0.1), port=18789 (env/config)
Probe target: ws://127.0.0.1:18789
Dashboard: http://127.0.0.1:18789/
Probe note: Loopback-only gateway; only local clients can connect.

Runtime: unknown (Bad request.
Could not find service "ai.openclaw.gateway" in domain for user gui: 501)
RPC probe: failed
RPC target: ws://127.0.0.1:18789
gateway closed (1006):

Service unit not found.
Service not installed. Run: openclaw gateway install
File logs: /tmp/openclaw/openclaw-2026-04-15.log
Troubles: run openclaw status
Troubleshooting: https://docs.openclaw.ai/troubleshooting

🦞 OpenClaw 2026.4.14 (323493f) — Your .zshrc wishes it could do what I do.

Gateway not reachable. Is it running and accessible?
Gateway target: ws://127.0.0.1:18789
Source: local loopback
Config: /Users/xx/.openclaw/openclaw.json
Bind: loopback
Hint: run openclaw doctor.

white tinselBOT Apr 15, 2026, 1:50 AM

#

Nice, we found the real clue. I’m checking the docs for the exact “config missing / service not installed” recovery path so I don’t send you down a bad branch.

#

Aha, this is the key line:

Config (cli): ~/.openclaw/openclaw.json (missing)

So the problem is not really “channel skipped”, it’s that onboarding never finished writing the local config. That also explains:

service not installed
gateway unreachable
0 agents / 0 sessions

For a fresh install, I’d do the guided path again:

openclaw onboard --install-daemon

That should recreate the config, set local gateway mode, and install/start the LaunchAgent.

#

If you want the more manual path instead:

openclaw setup
openclaw gateway install
openclaw gateway start

If the same trim error happens again during onboarding, please paste:

tail -n 100 /tmp/openclaw/openclaw-2026-04-15.log

At that point I’d treat it as a real onboarding bug, and it’d be worth filing an issue here:
https://github.com/openclaw/openclaw/issues

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