Embedded agent failed before reply: (0 , _sandbox.resolveSandboxRuntimeStatus) is not a function

[tacit rune]

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

[exotic dagger]

That stack points at a version/code mismatch in the agent runtime: something is importing resolveSandboxRuntimeStatus, but the loaded module does not export it in that running install. Most often that’s a partial/stale update or gateway still running old files.

First thing: please run and share:

openclaw --version
openclaw gateway status
openclaw status --all

Then I’d try the clean updater path:

openclaw update
openclaw gateway restart
openclaw doctor

If you’re running from a source checkout instead of the packaged install:

git pull
pnpm install
pnpm build
pnpm ui:build
openclaw gateway restart

Relevant docs: https://docs.openclaw.ai/help/faq and https://docs.openclaw.ai/install/updating

If it still happens after updating/rebuilding, this is worth filing with those logs plus the version: https://github.com/openclaw/openclaw/issues

This one is clearer: your Codex plugin is newer than the OpenClaw core it is loading from.

The plugin is trying to import:

openclaw/plugin-sdk/agent-harness-task-runtime

but your installed core under /home/toolupload02/.npm-global/lib/node_modules/openclaw does not have that built SDK subpath. That usually means a partial update, or plugins updated without the core update landing/restarting.

Please run:

openclaw --version
openclaw plugins list --json
openclaw update
openclaw gateway restart
openclaw doctor

If openclaw update does not repair the plugin/core skew, try repairing the Codex plugin explicitly after the core update:

openclaw plugins update codex
openclaw gateway restart

Docs: https://docs.openclaw.ai/install/updating and https://docs.openclaw.ai/plugins/manage-plugins

If it still fails, paste the openclaw --version plus the relevant openclaw logs --follow lines after restart.

[feral creek]

codex is up to date (2026.5.22).

[exotic dagger]

That means the plugin side is current, but the core side still looks wrong.

agent-harness-task-runtime exists in OpenClaw core starting at/around 2026.5.22. Your error says the running core path is missing it:

/home/toolupload02/.npm-global/lib/node_modules/openclaw/dist/plugin-sdk/...

Can you run:

openclaw --version
node -e "console.log(require.resolve('openclaw/plugin-sdk/agent-harness-task-runtime'))"
ls /home/toolupload02/.npm-global/lib/node_modules/openclaw/dist/plugin-sdk | grep agent-harness

If openclaw --version is older than 2026.5.22, update core too:

[exotic dagger]

openclaw update
openclaw gateway restart

If it says 2026.5.22 but that require.resolve fails, the global core install is incomplete/stale. I’d reinstall the core package, then restart:

openclaw gateway stop
npm i -g openclaw@latest
openclaw gateway install --force
openclaw gateway restart
openclaw doctor

Docs for that recovery path: https://docs.openclaw.ai/install/updating

[feral creek]

i want to use OpenClaw 2026.5.20 (e510042

[exotic dagger]

Got it. Then don’t keep @openclaw/codex@2026.5.22 installed against OpenClaw 2026.5.20 - that’s the mismatch causing this. The agent-harness-task-runtime SDK export is present in 2026.5.22, not 2026.5.20.

Pin the Codex plugin back to the same line as core:

openclaw plugins update npm:@openclaw/codex@2026.5.20
openclaw gateway restart

Then verify:

openclaw --version
openclaw plugins list --json
openclaw doctor