›_ Codex Issues
Codex Issues / #31639

Codex CLI 0.143.0: shell_command fails with “unsupported call: shell_commandshell_command”

Resolved 💬 6 comments Opened Jul 8, 2026 by fhoalbino Closed Jul 13, 2026
💡 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)?

0.143.0

What subscription do you have?

Plus

What platform is your computer?

Windows 11 Professional 64-bit (10.0.26200)

What issue are you seeing?

Codex CLI 0.143.0 on Windows 11

Every shell call fails with:
unsupported call: shell_commandshell_command

Reproduces with danger-full-access.
Downgrading to 0.142.5 fixes it.

What steps can reproduce the bug?

  1. Install Codex CLI 0.143.0:

npm install -g @openai/codex@0.143.0

  1. Open PowerShell inside any repository.
  1. Start Codex:

codex

  1. Ask:

List the files in this repository.

  1. Codex attempts to call shell_command, but every call returns:

unsupported call: shell_commandshell_command

The same failure occurs with:
codex -s danger-full-access -a on-request

Downgrading fixes it:
npm install -g @openai/codex@0.142.5

Affected session ID:
019f437b-7e1b-7483-898e-297f30aa9bfd

What is the expected behavior?

Codex should execute the shell_command tool and return the repository file listing.

Additional information

The issue began immediately after upgrading from 0.142.5 to 0.143.0.

The session permissions were unrestricted, and the failure persisted with danger-full-access. The command never reached PowerShell; the CLI rejected the tool call itself.

Rolling back to 0.142.5 restored shell execution immediately.

View original on GitHub ↗

6 Comments

github-actions[bot] contributor · 12 days ago

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

  • #31617
  • #31609
  • #31611
  • #31635

Powered by Codex Action

loveu8 · 12 days ago

I faced the same issue. My env is Windows 10 Professional 64-bit 22H2 (19045.6466). For now, downgrade to 0.142.5 will fix this issue.

hsiong · 12 days ago

I got the same tool-routing failure after upgrading Codex CLI to 0.143.0.

Environment:

  • OS: macOS / Linux mint
  • Codex CLI version with issue: 0.143.0
  • Install method: npm global install / Homebrew / installer script
  • Model: GPT-5.5
  • Surface: local terminal / Codex CLI / TUI
  • Subscription: Plus

Observed behavior:

After upgrading to 0.143.0, local terminal tool calls consistently fail before the command is executed.

The error is:

unsupported call: exec_commandexec_command

This happens for basic commands such as listing files or checking the current directory. The command does not appear to reach the local shell; it looks like the CLI/tool router rejects the generated tool call name before execution.

Expected behavior:

Codex should route the built-in terminal execution tool correctly and execute the requested shell command.

Workaround:

Downgrading fixes the issue:

npm uninstall -g @openai/codex
# brew uninstall --cask codex # mac
npm install -g @openai/codex@0.142.5
codex --version

Notes:

This appears related to the same tool-name duplication / unsupported-call pattern reported here, where the model or router emits a duplicated/self-referential built-in tool name such as exec_commandexec_command instead of the supported terminal execution tool name.

ziyuanLi-alex · 12 days ago

Ubuntu wsl 0.143.0 is also experiencing this issue

hafeezhmhahk · 11 days ago

Man i thought codex was better written than claude code. So many bugs lately. I hope it doesnt get enshittified!
i was facing the same issue in my mac installation using brew after i upgraded to the latest version. Downgraded using npm.

TidyWeb · 11 days ago

For those still hitting tool-calling issues (namespace doubling, broken HTML rendering): before rolling back to 0.142.5, check whether your install is actually complete.

My symptoms matched what's being reported here, but the root cause turned out to be a missing platform binary — @openai/codex-linux-x64 — not a version regression. The global npm install -g had silently skipped the optional dependency, leaving an incomplete install regardless of version.

Fix (Linux x64):

npm install -g @openai/codex@0.143.0
cd ~/.nvm/versions/node/$(node -v)/lib/node_modules/@openai/codex
npm install --include=optional

That installs codex-linux-x64 into the correct nested location. Currently running 0.143.0 without issue — tool calls passing, HTML rendering correctly.