Local execution tool routing failure in the current Codex session

Open
#37,547 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
macos, shell
Domain
cli, devtools

Research direction

No files or tests are named; first reproduce the unsupported custom tool call: execexec in the current Codex session and inspect local executor routing around session resume or context transitions. Done means shell and browser executors are reattached, a simple pwd or date command succeeds, and the local preview server can be started and validated again.

Written by the indexing model from the issue text.

Description

app bug session tool-calls
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

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.