CLI 0.143.0 duplicates shell_command namespace and returns unsupported call

Resolved 💬 2 comments Opened Jul 9, 2026 by zhang352477834 Closed Aug 6, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex CLI is running?

codex-cli 0.143.0

What subscription do you have?

ChatGPT Plus

Which model were you using?

gpt 5.5

What platform is your computer?

Windows x64

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

Windows PowerShell

Codex doctor report

What issue are you seeing?

After upgrading from Codex CLI 0.142.0 to 0.143.0, every built-in shell tool call fails before the command is executed.

The rollout records the following function call:

```json
{
"type": "function_call",
"name": "shell_command",
"namespace": "shell_command",
"arguments": "{\"command\":\"Get-Location\",\"workdir\":\"C:\\\\Users\\\\35247\"}"
}

Codex then returns:

unsupported call: shell_commandshell_command

It appears that the namespace and function name are incorrectly concatenated:

shell_command + shell_command = shell_commandshell_command

The issue reproduces consistently in a new session with a clean CODEX_HOME. Codex CLI 0.142.0 works correctly on the same machine.

The failure occurs during tool routing, before PowerShell or the Windows sandbox executes the command.

What steps can reproduce the bug?

• 1. Install Codex CLI 0.143.0:

```powershell
npx -y @openai/codex@0.143.0

  1. Use a new, empty CODEX_HOME:

New-Item -ItemType Directory -Force "$HOME\.codex-143"
$env:CODEX_HOME = "$HOME\.codex-143"
npx -y @openai/codex@0.143.0

  1. Sign in and start a new session.
  2. Ask Codex:

Please use the terminal to execute Get-Location.

  1. Observe that Codex retries but the terminal command is never executed.
  2. Inspect the generated rollout JSONL. The function call contains:

"name": "shell_command",
"namespace": "shell_command"

  1. The corresponding function output is:

unsupported call: shell_commandshell_command

The issue reproduces consistently with Codex CLI 0.143.0. Version 0.142.0 works correctly on the same machine.

What is the expected behavior?

• Codex should route the built-in tool as shell_command without duplicating its namespace, execute Get-Location in PowerShell, and return the actual working directory.

The function call should not be converted to shell_commandshell_command.

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 1 month ago

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

  • #31744
  • #31748
  • #31746
  • #31739
  • #31740

Powered by Codex Action

ppk42 · 1 month ago

tails:
Expected: exec_command.exec_command
Registered function: exec_command._
Runtime error: unsupported call: exec_commandexec_command

Environment:
Codex CLI version: codex-cli 0.143.0 > bash > kitty
OS/Arch: Linux 7.0.14-arch1-1 #1 SMP PREEMPT_DYNAMIC GNU/Linux
Model: GPT-5.5
Subscription: Plus

Reproduction:

  1. Start Codex CLI
  2. Select GPT-5.5
  3. Ask it to run a simple command, e.g. pwd
  4. Command execution fails with unsupported call: exec_commandexec_command

Workaround:
Using GPT-5.4 appears to work