Codex tool-dispatch failure — shell_command advertised but rejected

What version of Codex CLI is running?

codex-cli 0.143.0

What subscription do you have?

plus

Which model were you using?

gpt 5.5 medium

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What terminal emulator and version are you using (if applicable)?

VS code

Codex doctor report

Session ID: [019f4467-1a1f-77f0-a8bb-00af718e3ae4]
  OS: Windows
  Shell: PowerShell
  Workspace: E:\cl_code\qml_validations

  Codex advertises the `shell_command` tool, but every invocation fails before PowerShell executes.

  Exact error:
  unsupported call: shell_commandshell_command

  Minimal command attempted:
  Get-Content -Raw -LiteralPath 'DOA\CLAUDE.md'

  Expected:
  File contents are returned.

  unsupported call: shell_commandshell_command

  - Started multiple new sessions
  - Confirmed Claude can access the same workspace
  - Failure occurs before filesystem permissions or PowerShell are reached

  This appears to be a tool registration/routing mismatch between the tool manifest exposed to the model and the CLI/extension backend dispatcher.

  Please inspect the tool manifest and dispatch logs for this session.

What issue are you seeing?

I’m blocked by an environment/tooling failure: every filesystem command is currently rejected as an “unsupported call,” so I cannot truthfully inspect the requested files,
data, plots, or narratives. No files were changed.

Please retry this request in a session with workspace shell access enabled.
This looks specific to the Codex tool bridge, not your repository or permissions. I’ll make one minimal read attempt now; its raw failure mode will distinguish a broken shell
registration from filesystem sandboxing.

• The failure is confirmed before PowerShell or filesystem permissions are reached:

unsupported call: shell_commandshell_command

That indicates a Codex runtime/tool-dispatch mismatch: the session advertises shell_command, but the backend rejects its registered name. Reinstalling the client will not
necessarily affect that backend configuration. Claude working is consistent with it using a different tool bridge.

Please report this exact error to Codex support, including the session link/ID and:

• Workspace: E:\cl_code\qml_validations
• Shell: PowerShell
• Tool advertised: shell_command
• Every invocation returns: unsupported call: shell_commandshell_command
• The command never executes, so this is not a repository ACL issue

What steps can reproduce the bug?

read command

What is the expected behavior?

it would read and come back

Additional information

_No response_