app-server tool router rejects exec_command as unsupported call: exec_commandexec_command

Open 💬 7 comments Opened Jul 9, 2026 by TaoYySC
💡 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

What subscription do you have?

Plus

What platform is your computer?

Local Codex App platform:Windows 11 x64 Remote server platfom: Linux 5.15.0-139-generic x86_64 x86_64

What issue are you seeing?

Summary

codex app-server starts successfully and creates a thread with the correct remote workspace, but command execution fails because the tool router rejects an unsupported tool call named exec_commandexec_command.

This prevents Codex App Remote SSH sessions from using the read-only terminal/file tools. The terminal-based Codex CLI works, but the App/app-server path cannot run even simple commands such as pwd or ls -la.

Environment

  • Codex CLI version: 0.143.0
  • Node version: 22.23.1
  • npm version: 10.9.8
  • OS: Ubuntu 20.04 x86_64
  • Remote mode: Codex App Remote SSH / codex app-server
  • Shell: bash
  • Project cwd: /mnt/Storage2/home/yangtao/FuncPhos-STR

Reproduction

From the remote server:

cd /mnt/Storage2/home/yangtao/FuncPhos-STR
codex debug app-server send-message-v2 "Run pwd and ls -la. Do not modify files."

### What steps can reproduce the bug?

[codex_app_server_exec_command_bug.txt](https://github.com/user-attachments/files/29830972/codex_app_server_exec_command_bug.txt)

### What is the expected behavior?

pwd
ls -la

### Additional information

codex --version works.
codex app-server --help works.
The remote workspace path exists and is readable.
The terminal-based Codex CLI can be started from the project directory.
The issue appears specific to the app-server/tool-routing path.

View original on GitHub ↗

7 Comments

github-actions[bot] contributor · 12 days ago

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

  • #31656
  • #31697
  • #31665
  • #31609
  • #31691

Powered by Codex Action

SAIKA40170 · 12 days ago

I also got this issues

PlumYu-Labs · 12 days ago

+1

hmy-2002 · 12 days ago

The same, back to version142 can solve the problem

TaoYySC · 11 days ago
The same, back to version142 can solve the problem

yes, i change the model to 5.4 also can solve this problem, maybe it just a version problem.

roruizf · 11 days ago

Same issue here on WSL with Codex 0.143.0. Rollback to 0.142.5 resolved it immediately — no more exec_commandexec_command errors.

taduo · 7 days ago

I’m also seeing this issue on WSL with Codex CLI 0.143.0 installed via the standalone installer under ~/.local/bin/codex. Tool execution fails with the malformed exec_commandexec_command call. Rolling back to 0.142.5 resolved it.