Regression: Codex 0.147.0 fails against Azure AI Foundry while 0.146.0 succeeds

Resolved 💬 1 comment Opened Aug 7, 2026 by rnduldulaojr Closed Aug 7, 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?

0.147.0

What subscription do you have?

Custom: Azure Foundry

Which model were you using?

gpt-5.6-terra

What platform is your computer?

Darwin 24.6.0 arm64 arm

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

Ghostty

Codex doctor report

What issue are you seeing?

Upgraded from 0.146.0 to 0.147.0. Requests are now coming back with:

■ {"error":{"message":"litellm.BadRequestError: AzureException BadRequestError - {\n \"error\": {\n \"message\": \"Invalid
'input[0].tools[0].description': empty string. Expected a string with minimum length 1, but got an empty string instead.\",\n
\"type\": \"invalid_request_error\",\n \"param\": \"input[0].tools[0].description\",\n \"code\": \"empty_string\"\n }\n}.
Received Model Group=gpt-5.6-terra\nAvailable Model Group Fallbacks=None","type":null,"param":null,"code":"400"}}

What steps can reproduce the bug?

  • Requires Azure Foundry integration.
  • just doing ordinary codex exec "test" against Azure Foundry hosted models (gpt-5.6-sol, gpt-5.6-terra) with v0.147.0

What is the expected behavior?

Integration with Azure Foundry should be ok like in version 0.146.0

Additional information

_No response_

View original on GitHub ↗

1 Comment

github-actions[bot] contributor · 21 days ago

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

  • #37422
  • #37380

Powered by Codex Action