Summary

In a current WebChat/OpenAI Codex session, a connected and approved Windows node is visible to the Gateway and responds to node API capability checks, but no usable remote-node exec surface (node_exec, node_process, or equivalent) is exposed to Codex/WebChat.

This appears related to, but not fully covered by, the closed issue #92141. That issue originally tracked the missing host=node / remote-node exec surface. Later follow-up there reported a different intermediate state where node_exec became visible but failed with SYSTEM_RUN_DENIED: approval required. The issue is now closed, and the current smoke test again shows no remote-node exec tool visible in WebChat/Codex despite a healthy node.

Environment

• Gateway / CLI: OpenClaw 2026.6.11 (e085fa1)
• npm openclaw: 2026.6.11
• npm @openclaw/codex: 2026.6.11
• Surface: WebChat / Dashboard direct Codex session
• Gateway host: macOS iMac
• Remote node: JP-PC-Node
• Remote node platform: Windows
• Remote node version: 2026.6.8
• Remote node state: paired: true, connected: true, approvalState: approved
• Remote node capabilities: browser, file, system
• Remote node commands advertised: browser.proxy, system.run, system.run.prepare, system.which

Fresh smoke test, 2026-07-13

Version checks:

$ openclaw --version
OpenClaw 2026.6.11 (e085fa1)

$ npm view openclaw version
2026.6.11

$ npm view @openclaw/codex version
2026.6.11

Node status:

{
  "displayName": "JP-PC-Node",
  "platform": "windows",
  "version": "2026.6.8",
  "clientMode": "node",
  "deviceFamily": "Windows",
  "remoteIp": "100.123.153.83",
  "caps": ["browser", "file", "system"],
  "commands": ["browser.proxy", "system.run", "system.run.prepare", "system.which"],
  "approvalState": "approved",
  "paired": true,
  "connected": true
}

Node API capability check succeeds:

$ openclaw nodes invoke --node JP-PC-Node --command system.which --params '{"bins":["hostname","cmd","powershell","node"]}' --json

Result:

{
  "ok": true,
  "command": "system.which",
  "payload": {
    "bins": {
      "hostname": "C:\\Windows\\system32\\hostname.exe",
      "cmd": "C:\\Windows\\system32\\cmd.exe",
      "powershell": "C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe",
      "node": "C:\\Program Files\\nodejs\\node.exe"
    }
  }
}

Codex/WebChat tool catalog check:

tool_search query:
OpenClaw node_exec node_process remote node run command JP-PC-Node system.run host=node Codex WebChat

Result:
Found 0 tools.

Because no proper remote-node exec dynamic tool is exposed, I did not attempt a hostname remote exec command from Codex/WebChat. Direct system.run invocation via openclaw nodes invoke was intentionally not used, because system.run is documented/treated as reserved for the Exec path rather than direct node invocation.

Expected behavior

When a node is paired, approved, connected, advertises system.run / system.run.prepare, and the node API can resolve Windows commands via system.which, WebChat/OpenAI Codex should expose a supported remote-node exec surface such as node_exec / node_process, or provide a clear diagnostic explaining why the remote exec surface is intentionally withheld.

Actual behavior

The node is healthy and responds to node API checks, but the Codex/WebChat tool catalog exposes no usable remote-node exec surface. From the WebChat/Codex session there is currently no supported way to run even a minimal remote smoke command such as hostname on the connected Windows node.

Why this is distinct from #92141

#92141 is closed and its final state is ambiguous:

• Original problem: WebChat/OpenAI Codex did not expose a remote-node exec surface despite a connected Windows node.
• Later follow-up: the tool surface appeared in one test, but execution failed with SYSTEM_RUN_DENIED: approval required.
• Current 2026-07-13 smoke test: node is still connected and approved, node API checks work, but WebChat/Codex again exposes no node_exec / node_process tool.

So this issue is intended as a clean current-state repro rather than another late comment on the closed thread.

Requested diagnostic / guidance

Please clarify the expected supported path for mixed local+remote Codex sessions:

• Native Codex local shell/files for Gateway/local repo work.
• Explicit OpenClaw-owned remote node exec for selected node work, preserving node approval/audit policy.

If node_exec / node_process should be visible in this setup, what additional session/config flag or diagnostic should be checked to determine why WebChat/Codex receives no such tool?