VS Code extension becomes unresponsive and renders blank content after resuming a paused Goal
What version of the Codex App are you using (From “About Codex” dialog)?
26.5810.41047
What subscription do you have?
ChatGPT Pro 20x
What platform is your computer?
Microsoft Windows NT 10.0.26100.0 x64
What issue are you seeing?
Description
The Codex extension became unresponsive after I attempted to ask a question while a Goal was paused and then resumed the Goal.
The failure occurred at approximately 8:12 PM Central Time on August 13, 2026. The Codex extension may have updated approximately three hours before the failure.
Steps leading to the failure
- Codex was working on an active Goal.
- I paused the Goal so I could review several documents.
- While the Goal was paused, I entered a question in the Codex composer.
- A red error-message box appeared at the top of the Codex UI. I did not capture the exact wording, but it indicated that the conversation was done, completed, or otherwise no longer active.
- I resumed the Goal.
- I entered the question again.
- Codex appeared to begin thinking.
- The conversation area began scrolling or expanding upward with what looked like blank response lines. It appeared possible that text was being rendered in a dark foreground color matching the dark-theme background.
- After several blank entries appeared, I asked Codex what was happening.
- No visible response was produced.
- The Codex panel eventually changed to a nearly solid gray screen and became completely unresponsive.
Actual behavior
The Codex conversation area appeared to render multiple blank entries and then became a solid gray, unresponsive panel. No conversation controls, messages, progress indicators, or error details remained visible.
The attached screenshot shows the final state. The rest of VS Code remained visible, but the Codex panel was unusable.
Expected behavior
One of the following should occur:
- If questions cannot be submitted while a Goal is paused, the composer should be disabled or a clear, recoverable message should be displayed.
- After the Goal is resumed, the submitted question should be accepted and the response should render normally.
- If the conversation or Goal can no longer accept messages, the extension should preserve the conversation display and provide a clear recovery action instead of entering an unresponsive gray-screen state.
Environment
- Component: Codex IDE extension for Visual Studio Code
- Codex extension version:
26.5810.41047 - Visual Studio Code:
1.133.0(User Setup) - Operating system: Windows 11 Enterprise, version 24H2
- OS build:
26100.8893 - Windows Feature Experience Pack:
1000.26100.334.0 - Processor: 12th Gen Intel Core i7-12800H, 2.40 GHz
- Installed RAM: 32 GB
- System type: 64-bit operating system, x64-based processor
- VRAM: 4 GB
- Available system storage capacity: 477 GB
- VS Code theme: Dark
Windows, Visual Studio Code, and the Codex extension were fully updated at the time of the failure.
Possible regression
The Codex extension appears to have updated approximately three hours before the incident. I cannot yet confirm that the update caused the failure, but the timing may be relevant.
Reproducibility
Not yet determined. The observed sequence involved submitting a question while a Goal was paused, receiving a red “conversation done” or similar error, resuming the Goal, and submitting the question again.
Additional information
I did not record the exact text of the initial red error message. The screenshot captures the final gray-screen state.
Session ID: Not available
What steps can reproduce the bug?
Unknows
What is the expected behavior?
Unknown
Additional information
codex-vscode-console-errors-2026-08-13
vscode-app-1786670741904.log:
log.ts:117 ERR [vscode.mermaid-markdown-features]: Extension 'vscode.mermaid-markdown-features' CANNOT use 'legacyToolReferenceFullNames' without the 'chatParticipantPrivate' API proposal enabled
logToConsole @ log.ts:117
marketplace.visualstudio.com/_apis/public/gallery/vscode/msoffice/microsoft-office-add-in-debugger/latest:1 Failed to load resource: the server responded with a status of 404 ()
log.ts:117 ERR [Extension Host] (node:35800) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `Code --trace-deprecation ...` to show where the warning was created)
logToConsole @ log.ts:117
console.ts:139 [Extension Host] (node:35800) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `Code --trace-deprecation ...` to show where the warning was created)
log @ console.ts:139
log.ts:117 ERR [Extension Host] (node:35800) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
logToConsole @ log.ts:117
console.ts:139 [Extension Host] (node:35800) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
log @ console.ts:139
log.ts:117 ERR [Extension Host] Failed to load message bundle for file c:\Users\{redacted}\.vscode\extensions\ms-edgedevtools.vscode-edge-devtools-2.1.10\out\extension
logToConsole @ log.ts:117
console.ts:139 [Extension Host] Failed to load message bundle for file c:\Users\{redacted}\.vscode\extensions\ms-edgedevtools.vscode-edge-devtools-2.1.10\out\extension
log @ console.ts:139
log.ts:117 ERR [Extension Host] Failed to load message bundle for file c:\Users\{redacted}\.vscode\extensions\ms-edgedevtools.vscode-edge-devtools-2.1.10\out\extension
logToConsole @ log.ts:117
console.ts:139 [Extension Host] Failed to load message bundle for file c:\Users\{redacted}\.vscode\extensions\ms-edgedevtools.vscode-edge-devtools-2.1.10\out\extension
log @ console.ts:139
log.ts:117 ERR [Extension Host] Failed to load message bundle for file c:\Users\{redacted}\.vscode\extensions\ms-edgedevtools.vscode-edge-devtools-2.1.10\out\extension
logToConsole @ log.ts:117
console.ts:139 [Extension Host] Failed to load message bundle for file c:\Users\{redacted}\.vscode\extensions\ms-edgedevtools.vscode-edge-devtools-2.1.10\out\extension
log @ console.ts:139
log.ts:117 ERR [Extension Host] Failed to load message bundle for file c:\Users\{redacted}\.vscode\extensions\ms-edgedevtools.vscode-edge-devtools-2.1.10\out\extension
logToConsole @ log.ts:117
console.ts:139 [Extension Host] Failed to load message bundle for file c:\Users\{redacted}\.vscode\extensions\ms-edgedevtools.vscode-edge-devtools-2.1.10\out\extension
log @ console.ts:139
log.ts:117 ERR [Extension Host] Failed to load message bundle for file c:\Users\{redacted}\.vscode\extensions\ms-edgedevtools.vscode-edge-devtools-2.1.10\out\extension
logToConsole @ log.ts:117
console.ts:139 [Extension Host] Failed to load message bundle for file c:\Users\{redacted}\.vscode\extensions\ms-edgedevtools.vscode-edge-devtools-2.1.10\out\extension
log @ console.ts:139
log.ts:117 ERR [Extension Host] Failed to load message bundle for file c:\Users\{redacted}\.vscode\extensions\ms-edgedevtools.vscode-edge-devtools-2.1.10\out\extension
logToConsole @ log.ts:117
console.ts:139 [Extension Host] Failed to load message bundle for file c:\Users\{redacted}\.vscode\extensions\ms-edgedevtools.vscode-edge-devtools-2.1.10\out\extension
log @ console.ts:139
log.ts:117 ERR [Extension Host] Failed to load message bundle for file c:\Users\{redacted}\.vscode\extensions\ms-edgedevtools.vscode-edge-devtools-2.1.10\out\extension
logToConsole @ log.ts:117
console.ts:139 [Extension Host] Failed to load message bundle for file c:\Users\{redacted}\.vscode\extensions\ms-edgedevtools.vscode-edge-devtools-2.1.10\out\extension
log @ console.ts:139
log.ts:117 ERR [Extension Host] Failed to load message bundle for file c:\Users\{redacted}\.vscode\extensions\ms-edgedevtools.vscode-edge-devtools-2.1.10\out\extension
logToConsole @ log.ts:117
console.ts:139 [Extension Host] Failed to load message bundle for file c:\Users\{redacted}\.vscode\extensions\ms-edgedevtools.vscode-edge-devtools-2.1.10\out\extension
log @ console.ts:139
api.github.com/copilot_internal/managed_settings:1 Failed to load resource: the server responded with a status of 404 ()
api.github.com/copilot_internal/managed_settings:1 Failed to load resource: the server responded with a status of 404 ()
api.github.com/copilot_internal/managed_settings:1 Failed to load resource: the server responded with a status of 404 ()
api.github.com/copilot/mcp_registry:1 Failed to load resource: the server responded with a status of 404 ()
api.github.com/copilot/mcp_registry:1 Failed to load resource: the server responded with a status of 404 ()
api.github.com/copilot/mcp_registry:1 Failed to load resource: the server responded with a status of 404 ()
api.github.com/copilot_internal/managed_settings:1 Failed to load resource: the server responded with a status of 404 ()
api.github.com/copilot_internal/managed_settings:1 Failed to load resource: the server responded with a status of 404 ()
api.github.com/copilot_internal/managed_settings:1 Failed to load resource: the server responded with a status of 404 ()
api.github.com/copilot/mcp_registry:1 Failed to load resource: the server responded with a status of 404 ()
api.github.com/copilot/mcp_registry:1 Failed to load resource: the server responded with a status of 404 ()
api.github.com/copilot/mcp_registry:1 Failed to load resource: the server responded with a status of 404 ()
log.ts:117 ERR Tool "renderMermaidDiagram" was not contributed.
logToConsole @ log.ts:117
mainThreadExtensionService.ts:79 [openai.chatgpt]Git snapshot became stale
$onExtensionRuntimeError @ mainThreadExtensionService.ts:79
mainThreadExtensionService.ts:80 GitReviewSnapshotStaleError: Git snapshot became stale
at $v.read (c:\Users\{redacted}\.vscode\extensions\openai.chatgpt-26.5810.41047-win32-x64\out\extension.js:252:6373)
$onExtensionRuntimeError @ mainThreadExtensionService.ts:80
log.ts:117 ERR An unknown error occurred. Please consult the log for more details.
logToConsole @ log.ts:117
api.github.com/copilot_internal/managed_settings:1 Failed to load resource: the server responded with a status of 404 ()
api.github.com/copilot_internal/managed_settings:1 Failed to load resource: the server responded with a status of 404 ()
api.github.com/copilot_internal/managed_settings:1 Failed to load resource: the server responded with a status of 404 ()
api.github.com/copilot/mcp_registry:1 Failed to load resource: the server responded with a status of 404 ()
api.github.com/copilot/mcp_registry:1 Failed to load resource: the server responded with a status of 404 ()
api.github.com/copilot/mcp_registry:1 Failed to load resource: the server responded with a status of 404 ()
7 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Screen shot, almost forgot...
<img width="1300" height="869" alt="Image" src="https://github.com/user-attachments/assets/3fc2b6c2-43eb-4b35-a974-37a662af57c6" />
Follow-up Observations
After submitting the bug report and closing the browser, I noticed that the Windows UI became slow and sluggish, as though a large number of background tasks were still running. I then started VS Code, and the system responsiveness became even worse. Windows Task Manager showed numerous Codex-related processes, consoles, and sessions still active.
I shared the bug report with the VS Code Codex extension. Then I asked Codex to read and follow my VS Code/Codex extension shutdown procedure documented in a Markdown file. After that, I rebooted my PC.
I have observed the same thing. Particularly, when running codex /goal for long , the entire PC starts to slow down. This includes slow minimizing/maximizing , lag etc. This is a general observation, but is relevant given i have experienced the same nature of lag on the entire PC on windows with vs code extension.
i have encountered the Same issue.
This may be a renderer/process-lifecycle problem rather than damaged session history, but that distinction is exactly what I’m trying to measure on real cases.
If one of the affected Goal threads still exists locally, could someone with the issue run a read-only Codex Rescue check after Codex is fully stopped/restarted?
A clean/healthy result is useful here too: it would argue that the durable rollout survived and the failure is above the transcript layer. If Rescue finds an interrupted/unfinished boundary, that gives us a different signal. I’m not claiming Rescue fixes the Goal controller, VS Code renderer, or the background-process buildup.
Please share only sanitized status/findings — no raw rollout, prompts, repository contents, databases, paths, IDs, credentials, or secrets.
https://github.com/shleder/codex-rescue
Something I found useful; I tell Codex to run the following processes at Windows
BelowNormalpriority: