diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index 07f1c62ef..4863c0855 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "51ed22e6081d71e25be2efe283f2dda28fd93822",
-  "syncedAt": "2026-04-23T02:06:41.243Z"
+  "sha": "bae057fd771dcb2c137e3e71b37a5b69617a7561",
+  "syncedAt": "2026-04-23T02:12:17.532Z"
 }
diff --git a/docs/plugins/codex-harness.md b/docs/plugins/codex-harness.md
index 3ce12bff8..4300a9239 100644
--- a/docs/plugins/codex-harness.md
+++ b/docs/plugins/codex-harness.md
@@ -509,6 +509,11 @@ OpenClaw still builds the tool list and receives dynamic tool results from the
 harness. Text, images, video, music, TTS, approvals, and messaging-tool output
 continue through the normal OpenClaw delivery path.
 
+Codex MCP tool approval elicitations are routed through OpenClaw's plugin
+approval flow when Codex marks `_meta.codex_approval_kind` as
+`"mcp_tool_call"`; other elicitation and free-form input requests still fail
+closed.
+
 When the selected model uses the Codex harness, native thread compaction is
 delegated to Codex app-server. OpenClaw keeps a transcript mirror for channel
 history, search, `/new`, `/reset`, and future model or harness switching. The