Codex Harnes Failed | Friends of the Crustacean 🦞🤝 | Page 1

loud pebble May 10, 2026, 8:58 AM

#

hi after updating to v2026.5.9-beta.1
the chat dosent answer anymore it gives this error in console
10:54:57 [ws] ⇄ res ✓ commands.list 196ms conn=2c029d3c…d243 id=63a5e882…2c15
10:54:57 [ws] ⇄ res ✓ sessions.list 200ms conn=2c029d3c…d243 id=609ae0f4…33e8
10:54:57 [ws] ⇄ res ✓ chat.history 204ms conn=2c029d3c…d243 id=3dd14ac6…f9a4
10:55:06 [agent/embedded] workspace bootstrap file MEMORY.md is 37563 chars (limit 32000); truncating in injected context
10:55:06 [agents/harness] Codex agent harness failed; not falling back to embedded PI backend
10:55:06 [diagnostic] lane task error: lane=main durationMs=1268 error="Error: unsafe native hook relay bridge directory permissions"
10:55:06 [diagnostic] lane task error: lane=session:agent:main:main durationMs=1271 error="Error: unsafe native hook relay bridge directory permissions"
Embedded agent failed before reply: unsafe native hook relay bridge directory permissions

honest kelpBOT May 10, 2026, 8:58 AM

#

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

tepid raptorBOT May 10, 2026, 8:59 AM

#

That error is from the new Codex native hook relay safety check, not from MEMORY.md — the memory line is just a warning/truncation.

OpenClaw expects this temp relay directory to be owned by the gateway user and private (0700):

ls -ld /tmp/openclaw-native-hook-relays-$(id -u)
chmod 700 /tmp/openclaw-native-hook-relays-$(id -u)
openclaw gateway restart

If ls -ld shows it’s owned by a different user/root, either change ownership or remove that temp dir and restart so OpenClaw recreates it:

sudo chown -R "$USER":"$(id -gn)" /tmp/openclaw-native-hook-relays-$(id -u)
chmod 700 /tmp/openclaw-native-hook-relays-$(id -u)
openclaw gateway restart

#

If the directory doesn’t exist, that’s okay — paste the output of:

openclaw --version
openclaw status --all
ls -ld /tmp /tmp/openclaw-native-hook-relays-* 2>/dev/null

Docs for the general debugging flow: https://docs.openclaw.ai/help/faq and https://docs.openclaw.ai/gateway/troubleshooting 🦞

loud pebble May 10, 2026, 8:59 AM

#

im hosting it locally on windows

tepid raptorBOT May 10, 2026, 9:00 AM

#

Ah — if it’s truly running as native Windows, that exact directory permissions check shouldn’t normally fire. So either OpenClaw is actually running under WSL/Docker/Git-Bash-ish Linux, or this beta has a Windows-specific regression around the relay temp dir.

Can you run these from the same terminal/user that starts OpenClaw?

openclaw --version
openclaw status --all
node -p "process.platform + ' ' + require('os').tmpdir()"

Quick safe thing to try on native Windows:

openclaw gateway stop
Remove-Item -Recurse -Force "$env:TEMP\openclaw-native-hook-relays-*" -ErrorAction SilentlyContinue
openclaw gateway start

#

If node -p prints linux, then it’s WSL/Linux and the fix is the /tmp/... chmod/chown one from above. If it prints win32 and still errors, I’d treat this as a beta bug and file it here with the status --all output: https://github.com/openclaw/openclaw/issues

loud pebble May 10, 2026, 9:01 AM

#

PS C:\Users\ibrah> openclaw --version
OpenClaw 2026.5.9-beta.1 (0d3141e)
PS C:\Users\ibrah> openclaw status --all

🦞 OpenClaw 2026.5.9-beta.1 (0d3141e)
I'm the assistant your terminal demanded, not the one your sleep schedule requested.

│
OpenClaw status --all

Overview
┌────────────────────┬─────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Item │ Value │
├────────────────────┼─────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Version │ 2026.5.9-beta.1 │
│ OS │ windows 10.0.26200 (x64) │
│ Node │ 22.19.0 │
│ Config │ ~.openclaw\openclaw.json │
│ Dashboard │ http://127.0.0.1:18789/ │
│ Tailscale exposure │ off │
│ Channel │ beta (config) │
│ Update │ pnpm · up to date · npm beta 2026.5.9-beta.1 │
│ Gateway │ local · ws://127.0.0.1:18789 (local loopback) · reachable 102ms · auth token · MagicBlack (26. │
│ │ 88.112.181) app 2026.5.9-beta.1 windows 10.0.26200 │
│ Security │ Run: openclaw security audit --deep │
│ Gateway self │ unknown │
│ Gateway service │ Scheduled Task installed · registered · running │
│ Node service │ Scheduled Task not installed │
│ Agents │ 1 total · 0 bootstrapping · 1 active · 2 sessions │
│ Secrets │ none │
└────────────────────┴─────────────────────────────────────────────────────────────────────────────────────────────────┘

Channels
┌──────────┬─────────┬────────┬────────────────────────────────────────────────────────────────────────────────────────┐
│ Channel │ Enabled │ State │ Detail │
├──────────┼─────────┼────────┼────────────────────────────────────────────────────────────────────────────────────────┤
│ WhatsApp │ ON │ OK │ configured · accounts 1/1 │
└──────────┴─────────┴────────┴────────────────────────────────────────────────────────────────────────────────────────┘

WhatsApp accounts
┌──────────┬──────────┬────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Account │ Status │ Notes │

#

├──────────┼──────────┼────────────────────────────────────────────────────────────────────────────────────────────────┤
│ default │ OK │ dm:allowlist · credential available in gateway runtime · allow:393281396413 │
└──────────┴──────────┴────────────────────────────────────────────────────────────────────────────────────────────────┘

Agents
┌────────────┬────────────────┬──────────┬──────────┬──────────────────────────────────────────────────────────────────┐
│ Agent │ Bootstrap file │ Sessions │ Active │ Store │
├────────────┼────────────────┼──────────┼──────────┼──────────────────────────────────────────────────────────────────┤
│ main │ ABSENT │ 2 │ 5m ago │ ~.openclaw\agents\main\sessions\sessions.json │
└────────────┴────────────────┴──────────┴──────────┴──────────────────────────────────────────────────────────────────┘

Diagnosis (read-only)

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

✓ Config: C:\Users\ibrah.openclaw\openclaw.json
✓ Secret diagnostics (0)
✓ Restart sentinel: none
! Port 18789
Port 18789 is already in use.

pid 101484: "C:\Program Files\nodejs\node.exe" C:\Users\ibrah\AppData\Roaming\npm\node_modules\openclaw\dist\index.js gateway --port 18789 (127.0.0.1:18789)
Gateway already running locally. Stop it (openclaw gateway stop) or use a different port.
! Tailscale exposure: off · daemon unknown
✓ Skills: 29 eligible · 0 missing · C:\Users\ibrah\clawd
✓ Plugin compatibility (none)

Gateway restart attempts (tail): C:\Users\ibrah.openclaw\logs\gateway-restart.log
[2026-04-26T23:31:38.9867808+02:00] openclaw restart log initialized
[2026-04-26T23:31:38.9927882+02:00] openclaw restart attempt source=update target=OpenClaw Gateway
[2026-04-26T23:31:40.0438629+02:00] SUCCESS: The scheduled task "OpenClaw Gateway" has been terminated successfully.
[2026-04-26T23:31:41.6167561+02:00] SUCCESS: Attempted to run the scheduled task "OpenClaw Gateway".
[2026-04-26T23:31:41.6202677+02:00] openclaw restart done source=update
… 14 lines omitted …
[2026-04-27T21:53:31.7519781+02:00] openclaw restart done source=update
[30/04/2026 20:04:31.46] openclaw restart log initialized
[30/04/2026 20:04:31.47] openclaw restart attempt source=windows-task-handoff target="OpenClaw Gateway"
[30/04/2026 20:04:35.02] openclaw restart finished source=windows-task-handoff
[30/04/2026 20:38:37.70] openclaw restart log initialized
[30/04/2026 20:38:37.70] openclaw restart attempt source=windows-task-handoff target="OpenClaw Gateway"
[30/04/2026 20:38:39.23] openclaw restart finished source=windows-task-handoff
[10/05/2026 10:46:51.05] openclaw restart log initialized
[10/05/2026 10:46:51.06] openclaw restart attempt source=windows-task-handoff target="OpenClaw Gateway"
[10/05/2026 10:46:52.31] openclaw restart finished source=windows-task-handoff
✓ Channel issues (none)

Pasteable debug report. Auth tokens redacted.
Troubleshooting: https://docs.openclaw.ai/troubleshooting

◇
PS C:\Users\ibrah> node -p "process.platform + ' ' + require('os').tmpdir()"
win32 C:\Users\ibrah\AppData\Local\Temp
PS C:\Users\ibrah>

tepid raptorBOT May 10, 2026, 9:02 AM

#

Thanks — that confirms native Windows. I’m now pretty convinced this is a 2026.5.9-beta.1 Codex harness regression on Windows, because the permission check that throws that exact error is supposed to be Linux/macOS-style, not Windows.

Two useful next steps:

Try clearing the relay temp dir and restarting the scheduled task:

openclaw gateway stop
Remove-Item -Recurse -Force (Join-Path ([IO.Path]::GetTempPath()) "openclaw-native-hook-relays-*") -ErrorAction SilentlyContinue
openclaw gateway start

Then start a fresh chat/session (/new or /reset) and test again.

Please also run this and paste the output:

node -p "process.platform + ' tmp=' + require('os').tmpdir() + ' uid=' + (process.getuid?.() ?? 'none')"

#

If clearing temp doesn’t fix it, workaround is to avoid the Codex harness for now: route OpenAI through PI/direct API instead of Codex (agentRuntime.id: "pi"), or temporarily downgrade off this beta. Codex harness docs: https://docs.openclaw.ai/plugins/codex-harness

And yeah, this is worth a GitHub issue with the console error + openclaw status --all: https://github.com/openclaw/openclaw/issues

loud pebble May 10, 2026, 9:02 AM

#

PS C:\Users\ibrah> node -p "process.platform + ' tmp=' + require('os').tmpdir() + ' uid=' + (process.getuid?.() ?? 'none')"
win32 tmp=C:\Users\ibrah\AppData\Local\Temp uid=none

tepid raptorBOT May 10, 2026, 9:02 AM

#

Yep, this output is clean aside from the actual Codex harness crash. The Port 18789 is already in use warning is normal here — it’s just saying the gateway is already running on that port.

Since process.platform is win32, this looks like a beta regression in the native Codex hook relay on Windows.

Try the temp cleanup first:

openclaw gateway stop
Remove-Item -Recurse -Force (Join-Path ([IO.Path]::GetTempPath()) "openclaw-native-hook-relays-*") -ErrorAction SilentlyContinue
openclaw gateway start

Then in the chat, run /new or /reset and send a test message.

If it still fails, quickest workaround is to leave beta for now:

#

openclaw update --channel stable

Or, if you need to stay on beta, avoid the Codex harness temporarily and route OpenAI through direct/PI runtime instead. But honestly: please file this as a Windows beta bug with the exact error + your status --all: https://github.com/openclaw/openclaw/issues

Docs refs: https://docs.openclaw.ai/plugins/codex-harness and https://docs.openclaw.ai/cli/update

#

Perfect, that confirms it’s native Windows (win32, no uid), so the Linux-style permission failure is almost certainly a Windows bug in 2026.5.9-beta.1’s Codex harness path.

Do this next:

openclaw gateway stop
Remove-Item -Recurse -Force (Join-Path ([IO.Path]::GetTempPath()) "openclaw-native-hook-relays-*") -ErrorAction SilentlyContinue
openclaw gateway start

Then /new or /reset in the chat and test again.

If it still fails, I’d downgrade to stable for now:

openclaw update --channel stable

#Codex Harnes Failed