Local execution tool routing failure in the current Codex session

Open 💬 1 comment Opened Aug 8, 2026 by u5de6
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

26.803.41515

What subscription do you have?

1

What platform is your computer?

macOS Intel

What issue are you seeing?

Symptoms:
The current session cannot execute even basic local shell commands.
Execution calls fail with: unsupported custom tool call: execexec
The same session previously executed local commands, started a localhost static server, and performed browser validation successfully.
The failure occurs at the tool-routing layer, before command execution.
There is no evidence that authorization, repository files, the prototype, or the local server caused the failure.
Impact:
Cannot start or verify the local preview server.
Cannot continue test_cash_processing, transaction-guard, safe-size, or focus validation.
Only conversation and existing-result review remain possible; new local verification cannot be performed.
Expected resolution:
Reattach the local shell and browser executors to the current session.
Check whether tool bindings are lost after session resume or context transition.
Check why the tool call is being wrapped or routed as execexec.
After recovery, validate with a simple pwd or date command.

What steps can reproduce the bug?

Execution calls fail with: unsupported custom tool call: execexec

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

1 Comment

github-actions[bot] contributor · 20 days ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #36215

Powered by Codex Action