Codex desktop for Win thread loses workspace tools mid-conversation when using Azure AI Foundry OpenAI model
What version of the Codex App are you using (From “About Codex” dialog)?
26.527.60818
What subscription do you have?
Azure AI Foundry (Open AI)
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
In Codex desktop for Windows (version 26.527.60818), a coding thread started with normal workspace tools available, but later lost access to all workspace/Codex tools mid-conversation. After that point, the assistant could only see web/search tools and could no longer use terminal, file read/write, apply_patch, tests/build, Codex thread tools, or app tools.
This blocked an active implementation that was already in progress.
Environment
- App: Codex desktop
- OS: Windows
- Provider: Azure AI Foundry OpenAI
- Model/deployment: GPT-5.5, reasoning
xhigh - Not using an OpenAI subscription/API key directly
What Happened
The thread initially had full workspace tool access. The assistant was able to:
- read files
- edit files with
apply_patch - run terminal commands
- run tests
- run
npm run typecheck - run
npm run build - inspect prior Codex threads
Later in the same task, while continuing implementation, the assistant suddenly reported that no workspace tools were available. It could only see web/search. A delegation message was then sent asking the assistant to continue implementation, but the assistant still had no workspace tools available.
This happened after a long-running coding workflow involving Copy Video / AI Browser changes. It may be related to thread continuation, context compaction, delegation, or tool rehydration.
Expected Behavior
At minimum, if tools cannot be restored, Codex should show a clear error explaining why workspace tools were removed or blocked.
What steps can reproduce the bug?
Approximate flow:
- Open Codex desktop with workspace
- Start a coding task that uses filesystem and terminal tools.
- Let the assistant inspect prior thread context and implement changes.
- Continue the conversation after several messages / possible context compaction.
- Ask the assistant to continue implementation.
- Observe that workspace tools are no longer visible to the assistant.
- Send a Codex delegation message to continue the same implementation.
- Assistant still reports only web/search tools available.
What is the expected behavior?
If a Codex desktop thread starts with workspace tools, those tools should remain available across the conversation, including after:
- long context
- compaction/resume
- user follow-up messages
- delegation messages
- continued implementation requests
Additional information
Actual Behavior
The assistant lost access to all workspace tools and could not continue implementation. It could only respond with text and web/search access.
The missing tools included:
- terminal/shell
- file read/write
apply_patch- test/build execution
- Codex app tools
- thread inspection/delegation tools
Impact
This breaks coding workflows because the assistant can get halfway through a repo change, then become unable to edit or verify anything. In this case, implementation was interrupted while fixing active bugs in an Electron app.
Additional Context
This was not using an OpenAI subscription directly. The configured provider was Azure AI Foundry OpenAI with GPT-5.5 / xhigh.