What version of the Codex App are you using (From “About Codex” dialog)?
26.707.72221
What subscription do you have?
Pro
What platform is your computer?
Codex desktop app on Windows
What issue are you seeing?
In-app bug feedback was submitted from my signed-in ChatGPT Pro account on 14 July 2026, with the affected session logs included. No reference ID was displayed.
Title: Critical reproducible Codex workspace failure — terminal commands hang indefinitely
In-app bug feedback submitted with current session logs on 14 July 2026. No feedback/session ID was displayed.
Date: 14 July 2026
Severity: Critical operational blocker
Platform: Codex desktop application on Windows
Workspace location:
D:\OneDrive[business project][application]\app_source
Issue summary
Codex is unable to execute even the simplest read-only terminal command in this workspace. Commands stall without producing any output and must be terminated manually.
This completely blocks source inspection, editing, building, testing and Git operations. Ordinary conversational responses and non-workspace tests remain responsive, indicating that the problem is specifically connected to workspace or terminal execution.
Reproduction steps
-
Open Codex.
-
Open the workspace shown above.
-
Start a new task.
-
Ask Codex to run only:
Get-Location
-
Do not request any file inspection, build or source changes.
Expected result
The current working directory should be returned almost instantly.
Actual result
The command remains unresponsive without producing output. In the post-reboot test, it was still running after 1 minute 31 seconds and had to be stopped.
Previous failures during the same incident
-
An implementation task ran for 16 minutes 18 seconds. The required patch mechanism repeatedly timed out before writing even a one-line change. No source changes were applied.
-
A fresh task attempted the read-only command:
Get-Location
The command stalled repeatedly, including during an elevated retry, and was terminated each time.
-
Another fresh task attempted:
Get-Location; Get-ChildItem -Force | Select-Object -ExpandProperty Name; Test-Path -LiteralPath package.json; git status --short --branch
This produced no output and was terminated after 40 seconds.
-
Codex was then completely closed, remaining processes were cleared, and the computer was rebooted.
-
Following the reboot, a new task was instructed to run only Get-Location. The command again failed to return and was stopped after more than 1 minute 31 seconds.
Troubleshooting already completed
- Tested through multiple fresh Codex tasks.
- Reduced the test to a single read-only Get-Location command.
- Tried an elevated retry.
- Fully closed Codex.
- Rebooted the computer.
- Reopened the workspace and reproduced the fault.
- Confirmed that no build or source modification was required to trigger the problem.
Data and repository impact
No source files were changed during these failed attempts. No successful patch was applied, no UAT log was updated and no post-failure build was run. There is currently no evidence that the repository or application data has been corrupted.
A baseline pnpm/Vite build completed successfully before the terminal failure became total, transforming 32 modules.
Operational impact
This is a complete development blocker for a business-critical application. Codex cannot inspect the workspace, edit source files, run builds or report Git status. Continued retries are not practical or safe.
Evidence available
- Screenshots of each stalled task and elapsed time.
- Codex’s own failure reports confirming that no files were changed.
- A saved Codex performance trace.
- A consolidated Word incident record.
- Exact workspace path and commands used.
Please investigate the Codex workspace/terminal execution service and advise whether this is related to:
- Windows PowerShell process initialisation;
- opening a workspace located within OneDrive;
- workspace permissions or repository ownership;
- local security-software interception; or
- a Codex desktop/backend regression.
Please also confirm whether the performance trace can be uploaded securely and whether any additional diagnostic information is required.
Severe performance degradation preceding the failure
This incident did not begin with the complete terminal failure on 14 July 2026.
Throughout 13 July 2026, Codex performance was severely degraded. Development tasks that would ordinarily complete within minutes took hours. One task ran for approximately 1 hour 52 minutes, despite being of a type and scope that had previously completed much more quickly.
The application frequently remained in a working or thinking state for prolonged periods, with very slow or absent terminal feedback. By 14 July, the degradation had progressed to the point where Codex could no longer execute even a single read-only Get-Location command.
The apparent progression was therefore:
- Normal performance previously.
- Severe slowdown on 13 July, with routine tasks taking hours.
- Repeated patch-tool timeouts on 14 July.
- Total workspace terminal failure, including Get-Location.
- The same total failure persisting after Codex was fully closed and the computer rebooted.
Conversational and non-workspace Codex responses remained fast during at least some of this period. The severe degradation was most apparent when Codex attempted to access or operate within the local SETL workspace.
What steps can reproduce the bug?
- Open the Codex desktop app on Windows.
- Open a local development workspace stored under D:\OneDrive[business project][application]\app_source.
- Start a new task.
- Ask Codex to run only the read-only PowerShell command:
Get-Location
- The shell does not return any output. The task remains working indefinitely and must be stopped manually.
The issue has been reproduced across multiple fresh tasks. It also persists after completely closing Codex, clearing remaining processes and rebooting the computer.
Other failed checks included:
Get-Location; Get-ChildItem -Force | Select-Object -ExpandProperty Name; Test-Path -LiteralPath package.json; git status --short --branch
That command produced no output and was terminated after 40 seconds.
A separate implementation task ran for 16 minutes 18 seconds because the patch mechanism repeatedly timed out before writing even a one-line change.
The simplest post-reboot reproduction, Get-Location alone, remained unresponsive for more than 1 minute 31 seconds.
No source files were changed during these tests.
Session ID: [INSERT IN-APP FEEDBACK SESSION ID HERE, OR WRITE “NOT YET AVAILABLE”]
What is the expected behavior?
Get-Location should return the current working directory almost instantly.
Codex should be able to inspect the workspace, execute read-only terminal commands, edit files, run builds and perform Git checks without indefinite terminal stalls.
Routine development tasks that ordinarily take minutes should not take hours.
Additional information
The complete terminal failure was preceded by severe performance degradation on 13 July 2026.
Routine development tasks that would ordinarily complete within minutes took hours. One task ran for approximately 1 hour 52 minutes. Codex frequently remained in a working or thinking state for prolonged periods, with very slow or absent terminal feedback.
By 14 July, the degradation had progressed through repeated patch-tool timeouts to total workspace terminal failure. Even Get-Location could no longer execute.
Conversational and non-workspace Codex responses remained fast during at least some of this period. The problem was most apparent when Codex attempted to access or operate within the local workspace.
A baseline pnpm/Vite build completed successfully before the terminal failure became total. There is currently no evidence of repository corruption.
Impact: complete development blocker for a business-critical application.
Screenshots, a performance trace and a consolidated evidence report are available privately on
What version of the Codex App are you using (From “About Codex” dialog)?
26.707.72221
What subscription do you have?
Pro
What platform is your computer?
Codex desktop app on Windows
What issue are you seeing?
In-app bug feedback was submitted from my signed-in ChatGPT Pro account on 14 July 2026, with the affected session logs included. No reference ID was displayed.
Title: Critical reproducible Codex workspace failure — terminal commands hang indefinitely
In-app bug feedback submitted with current session logs on 14 July 2026. No feedback/session ID was displayed.
Date: 14 July 2026
Severity: Critical operational blocker
Platform: Codex desktop application on Windows
Workspace location:
D:\OneDrive[business project][application]\app_source
Issue summary
Codex is unable to execute even the simplest read-only terminal command in this workspace. Commands stall without producing any output and must be terminated manually.
This completely blocks source inspection, editing, building, testing and Git operations. Ordinary conversational responses and non-workspace tests remain responsive, indicating that the problem is specifically connected to workspace or terminal execution.
Reproduction steps
Open Codex.
Open the workspace shown above.
Start a new task.
Ask Codex to run only:
Get-Location
Do not request any file inspection, build or source changes.
Expected result
The current working directory should be returned almost instantly.
Actual result
The command remains unresponsive without producing output. In the post-reboot test, it was still running after 1 minute 31 seconds and had to be stopped.
Previous failures during the same incident
An implementation task ran for 16 minutes 18 seconds. The required patch mechanism repeatedly timed out before writing even a one-line change. No source changes were applied.
A fresh task attempted the read-only command:
Get-Location
The command stalled repeatedly, including during an elevated retry, and was terminated each time.
Another fresh task attempted:
Get-Location; Get-ChildItem -Force | Select-Object -ExpandProperty Name; Test-Path -LiteralPath package.json; git status --short --branch
This produced no output and was terminated after 40 seconds.
Codex was then completely closed, remaining processes were cleared, and the computer was rebooted.
Following the reboot, a new task was instructed to run only Get-Location. The command again failed to return and was stopped after more than 1 minute 31 seconds.
Troubleshooting already completed
Data and repository impact
No source files were changed during these failed attempts. No successful patch was applied, no UAT log was updated and no post-failure build was run. There is currently no evidence that the repository or application data has been corrupted.
A baseline pnpm/Vite build completed successfully before the terminal failure became total, transforming 32 modules.
Operational impact
This is a complete development blocker for a business-critical application. Codex cannot inspect the workspace, edit source files, run builds or report Git status. Continued retries are not practical or safe.
Evidence available
Please investigate the Codex workspace/terminal execution service and advise whether this is related to:
Please also confirm whether the performance trace can be uploaded securely and whether any additional diagnostic information is required.
Severe performance degradation preceding the failure
This incident did not begin with the complete terminal failure on 14 July 2026.
Throughout 13 July 2026, Codex performance was severely degraded. Development tasks that would ordinarily complete within minutes took hours. One task ran for approximately 1 hour 52 minutes, despite being of a type and scope that had previously completed much more quickly.
The application frequently remained in a working or thinking state for prolonged periods, with very slow or absent terminal feedback. By 14 July, the degradation had progressed to the point where Codex could no longer execute even a single read-only Get-Location command.
The apparent progression was therefore:
Conversational and non-workspace Codex responses remained fast during at least some of this period. The severe degradation was most apparent when Codex attempted to access or operate within the local SETL workspace.
What steps can reproduce the bug?
Get-Location
The issue has been reproduced across multiple fresh tasks. It also persists after completely closing Codex, clearing remaining processes and rebooting the computer.
Other failed checks included:
Get-Location; Get-ChildItem -Force | Select-Object -ExpandProperty Name; Test-Path -LiteralPath package.json; git status --short --branch
That command produced no output and was terminated after 40 seconds.
A separate implementation task ran for 16 minutes 18 seconds because the patch mechanism repeatedly timed out before writing even a one-line change.
The simplest post-reboot reproduction, Get-Location alone, remained unresponsive for more than 1 minute 31 seconds.
No source files were changed during these tests.
Session ID: [INSERT IN-APP FEEDBACK SESSION ID HERE, OR WRITE “NOT YET AVAILABLE”]
What is the expected behavior?
Get-Location should return the current working directory almost instantly.
Codex should be able to inspect the workspace, execute read-only terminal commands, edit files, run builds and perform Git checks without indefinite terminal stalls.
Routine development tasks that ordinarily take minutes should not take hours.
Additional information
The complete terminal failure was preceded by severe performance degradation on 13 July 2026.
Routine development tasks that would ordinarily complete within minutes took hours. One task ran for approximately 1 hour 52 minutes. Codex frequently remained in a working or thinking state for prolonged periods, with very slow or absent terminal feedback.
By 14 July, the degradation had progressed through repeated patch-tool timeouts to total workspace terminal failure. Even Get-Location could no longer execute.
Conversational and non-workspace Codex responses remained fast during at least some of this period. The problem was most apparent when Codex attempted to access or operate within the local workspace.
A baseline pnpm/Vite build completed successfully before the terminal failure became total. There is currently no evidence of repository corruption.
Impact: complete development blocker for a business-critical application.
Screenshots, a performance trace and a consolidated evidence report are available privately on