Windows Codex local tool host exits during handshake after update
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
Powered by Codex & OWL 版本 26.820.80927
What subscription do you have?
plus
What platform is your computer?
Microsoft Windows NT 10.0.19045.0 x64
What issue are you seeing?
I am using the Microsoft Store version of the ChatGPT/Codex Windows app.
App package:
OpenAI.Codex 26.820.9563.0 x64
SignatureKind: Store
Workspace dependencies:
26.826.11250
Every local tool command fails before execution with:
code-mode host exited during handshake
Minimal reproduction:
- Open a Codex task.
- Ask Codex to run PowerShell command: Get-Location
- The command never starts and the handshake error is returned.
The issue started after a recent Codex update.
Troubleshooting already completed:
- Fully exited all ChatGPT/Codex processes
- Rebooted Windows multiple times
- Repaired the Windows app
- Diagnosed the workspace dependencies; diagnostics reported no problem
- Reinstalled the workspace dependencies
- Uninstalled and reinstalled the Microsoft Store ChatGPT app
- Renamed the existing C:\Users\Lenovo.codex directory and tested with a newly created clean profile
- Checked Windows Security protection history; no Codex/OpenAI process was blocked
The problem still occurs with a clean profile and clean reinstall.
Expected result:
Get-Location should return the current PowerShell working directory.
Actual result:
code-mode host exited during handshake
What steps can reproduce the bug?
Feedback ID: no-active-thread-01a045fd-1e2e-7673-be59-cc9d6fff1b92
What is the expected behavior?
Please fix it
Additional information
my ID : no-active-thread-01a045fd-1e2e-7673-be59-cc9d6fff1b92
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure on Microsoft Windows using the Microsoft Store app and the PowerShell command Get-Location, starting with the local tool host handshake path and the reported error. Done means the command completes and returns the current working directory on a clean profile after the update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100