reef fable
Currently having this issue after update :
Agent failed before reply: Requested agent harness "codex" is not registered.
Logs: openclaw logs —follow gateway connected | idle
agent main | session terminal (openclaw-tui) | openai-codex/gpt-5.5 | tokens 48k/100k (48%)
bitter relicBOT
silent tinselBOT
Currently having this issue after update :
Agent failed before reply: Requeste...
That error usually means the session/config is explicitly asking for the codex agent harness, but the bundled Codex plugin did not register. I checked the current docs: the Codex harness is plugin-owned, so if plugins.allow is restrictive and omits codex, or the plugin entry is disabled, you can get exactly this kind of failure.
First, please confirm the actual binary version:
openclaw --version
Then try this order:
openclaw doctor
openclaw config get plugins.allow --json
openclaw config get plugins.entries.codex --json
If doctor reports Codex route/session repair, run:
silent tinselBOT
Currently having this issue after update :
Agent failed before reply: Requeste...
openclaw doctor --fix
openclaw gateway restart
If plugins.entries.codex is missing/disabled, enable it:
openclaw config set plugins.entries.codex.enabled true --strict-json
openclaw gateway restart
If plugins.allow is set, make sure codex is included in that existing list. Don’t replace the whole list unless you mean to; a restrictive allowlist blocks bundled plugins too.
After the restart, start a fresh chat/session with /new or /reset, because stale session runtime pins can survive config changes.
Docs I checked:
silent tinselBOT
Currently having this issue after update :
Agent failed before reply: Requeste...
reef fable
No matter what I type it keep giving that error
silent tinselBOT
No matter what I type it keep giving that error
If it happens for everything, the broken state is probably being hit before your message content matters. Run these from your terminal, not in the chat/TUI:
openclaw --version
openclaw plugins doctor
openclaw plugins list | grep -i codex
openclaw doctor --fix
openclaw gateway restart
Then start a fresh session:
/new
If plugins list | grep -i codex shows nothing, or plugins doctor says Codex is blocked, that’s the smoking gun. In that case enable it and restart:
silent tinselBOT
No matter what I type it keep giving that error
openclaw plugins enable codex
openclaw gateway restart
If it still fails after that, paste the output of these three:
openclaw --version
openclaw plugins doctor
openclaw config get plugins.allow --json
The key thing: keep this fix loop in the shell until the harness registers. Typing different prompts won’t help while the session is pinned to an unavailable codex harness.
reef fable
No telegram seems to not be working properly responses take forever and never come thru
silent tinselBOT
No telegram seems to not be working properly responses take forever and never co...
Got it. If Telegram responses take forever and never arrive, split it into two checks: “is Telegram receiving/sending?” vs “is the agent run stuck before delivery?”
Run this from the Gateway machine while sending one Telegram test message:
openclaw --version
openclaw status --all
openclaw channels status --probe
openclaw channels logs --channel telegram
openclaw logs --follow
What to look for:
channels status --probe shows Telegram disconnected/auth errors, it’s channel transport/token/network.Requested agent harness "codex" is not registered, Telegram is probably fine; the agent runtime is still broken from the Codex harness issue.
silent tinselBOT
No telegram seems to not be working properly responses take forever and never co...
openclaw models status
openclaw doctor
Given the earlier Codex error, I’d still do this once from shell:
openclaw plugins doctor
openclaw doctor --fix
openclaw gateway restart
Then send /new in Telegram and try one short test message. If it still hangs, paste the output of openclaw channels status --probe plus the few log lines around the Telegram test message. Don’t paste tokens.