You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 224f23d
Browse filesBrowse the repository at this point in the historyBrowse files
fix: normalize legacy exec_command/shell_command tool calls to declared exec (#2493)
Codex 0.149 declares its code-mode shell tool as `exec` (a freeform custom
tool whose description mentions the nested `await tools.exec_command(...)`
helper). Routed models — DeepSeek in particular — sometimes echo that helper
name as the tool-call name, emitting `exec_command` instead of the declared
`exec`. The undeclared-tool guard then fails the whole turn with a 502.
Normalize the legacy shell bridge names to `exec` at the three guard sites
(streaming bridge x2, terminal snapshot guard) only when the request catalog
declares `exec` and declares no legacy shell bridge name itself, so an MCP
server advertising its own `exec_command` keeps working. Namespaced calls
are always matched by their full wire name and never legacy-normalized.
Co-authored-by: liyongjie.103 <[email protected]>
0 commit comments