Codex Desktop 26.810.41047 returns 400: input[0].tools[0].description is empty with Azure Responses API
What version of the Codex App are you using (From “About Codex” dialog)?
Desktop version: 26.810.41047 Runtime/client version: 0.148.0
What subscription do you have?
Provider: Azure OpenAI / Foundry
What platform is your computer?
Windows
What issue are you seeing?
Invalid 'input[0].tools[0].description': empty string. Expected a string with minimum length 1, but got an empty string instead.
What steps can reproduce the bug?
After updating to Codex Desktop 26.810.41047, requests sent through a custom Azure OpenAI / Microsoft Foundry provider fail with HTTP 400.
The API rejects a dynamically generated tool because its description field is an empty string
What is the expected behavior?
_No response_
Additional information
Desktop version: 26.810.41047
Runtime/client version: 0.148.0
Provider: Azure OpenAI / Foundry
Endpoint: /openai/v1/responses
Error: input[0].tools[0].description empty_string
First occurrence: 2026-08-14 04:58:32
Last observed: 2026-08-14 07:57:46
The issue is reproducible and has occurred 18 times in the local logs.
Observed failures by model:
gpt-5.6-sol: 10
gpt-5.6-luna: 7
gpt-5.6-terra: 1
8 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
As compared to the same reported issue for the Codex CLI (the guys suggested a workaround of downgrading to 0.146.1), for the Windows Store app there seems to be no workarounds (at least I cannot find where I could download the earlier version of the app, and apparently it ships its own Codex CLI).
The app became completely unusable.
Can there be any workaround?
I don't think there is an easy way to rollback versions on the Codex desktop app (on Windows anyway). What I ended up doing was point the desktop app to use a different codex.exe from the bundled version.
What I did to fix this issue was:
pnpm install -g @openai/codex@0.146.1)CODEX_CLI_PATHto the global Codex CLI installation (C:\Users\username\AppData\Local\pnpm\store\v11\links\@openai\codex\0.146.1-win32-x64\**big-hash-here**\node_modules\@openai\codex\vendor\x86_64-pc-windows-msvc\bin\codex.exe')This fixed the issue for me and I can now use the Codex Desktop app normally.
(One extra step I did was also edit the
CODEX_CLI_PATHentry under the[mcp_servers.node_repl.env]section of theconfig.tomlthough I don't expect that to have been the fix to the problem.)For me the path was
C:\Users\{YOUR-USERNAME}\AppData\Roaming\npm\node_modules\@openai\codex\node_modules\@openai\codex-win32-x64\vendor\x86_64-pc-windows-msvc\bin\codex.exei have installed the CLI at 0.146.1 successfully, but my codex/chatgpt app didnt pick up the env variable i created properly, any clue? is there anything to add to the .toml file to make it visible? other than the [mcp_servers.node_repl.env] section cause it would then show
"Error creating chat
invalid configuration: invalid transport
in
mcp_servers.node_repl"@Nxorz you may want to restart the codex app. Remember, it continues to run in tray, even when you close the window
Yeah that picked it up, thanks, can it also be done via npm?
Cause the npm module of openai shows a very old version lol (at least for me)
@Nxorz assuming you mean https://www.npmjs.com/package/@openai/codex then
npm,pnpm,bun,yarnwhatever shouldn't make a difference when installing it, just need to point theCODEX_CLI_PATHto wherever it installs.