OpenClaw 5.28: Codex Plugin Broken After Upgrade — Fix with Symlink Shim

Upgrading OpenClaw from 5.12 to 5.28 can silently break the Codex plugin. After the upgrade, all agent calls hang at Waiting for agent reply, cron jobs time out at exactly 121 seconds with model-call-started, and the fallback chain doesn't kick in fast enough. The gateway starts clean, OAuth is valid, and Codex shows as installed and enabled — but every binary spawn attempt fails with a silent ENOENT.
Root Cause: Path Mismatch
The 5.28 Codex plugin harness expects the binary at:
vendor/x86_64-unknown-linux-musl/codex/codexBut the package ships the binary at:
vendor/x86_64-unknown-linux-musl/bin/codexThe plugin never finds the binary, so every spawn attempt hangs.
Fix: Create a Symlink Shim
Set the Codex extension directory and symlink the binary:
CODEX_DIR="/home/clawbot/.openclaw/extensions/codex/node_modules/@openai/codex-linux-x64/vendor/x86_64-unknown-linux-musl"
sudo mkdir -p "$CODEX_DIR/codex"
sudo ln -sf "$CODEX_DIR/bin/codex" "$CODEX_DIR/codex/codex"
sudo chown -h clawbot:clawbot "$CODEX_DIR/codex/codex"
sudo systemctl restart openclawAfter restart, agent calls should resume normally.
Important Caveats
- Reinstall or force-update of the Codex plugin wipes the extensions directory, so you must recreate the symlink after each reinstall.
- If your systemd service uses an
ExecStartPostchmod on the Codex binary, update that path tobin/codexas well.
This was reproduced on Ubuntu 24.04, npm install, systemd service. Hopefully this saves you a few hours of debugging.
📖 Read the full source: r/openclaw
👀 See Also

Fix for 'VM Service Not Running' error in Cowork on Windows 11
A Reddit user shares a PowerShell command fix for the 'VM Service Not Running' error in Cowork when Hyper-V is installed but the hypervisor isn't launching at boot. The solution involves checking hypervisorlaunchtype and setting it to auto.

OpenClaw Cost Optimization: Five Settings for Continuous Agent Usage
A developer running OpenClaw continuously on a Raspberry Pi identified five configuration settings that significantly reduced agent costs by optimizing for cost rather than default capability.

OpenClaw Memory Management: Complete Guide

OpenClaw Memory Plugin Analysis: Lossless Claw + LanceDB Recommended
A developer tested OpenClaw memory plugins and found that the default setup causes token bloat, while Lossless Claw paired with LanceDB provides optimal performance for maintaining agent context without high costs.