01a0ab02-ac9a-7f53-9e25-bad45f540c44
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)?
App: 26.908.4834.0
What subscription do you have?
Pro
What platform is your computer?
Windows
What issue are you seeing?
App restart did not resolve it. Codex dependency diagnostics report healthy. The available sandbox.log is stale, dated May 13, and contains no current failure. Computer control also fails with trusted Node process exited unexpectedly; kernel reset.
Please advise how to rerun or repair sandbox setup in this app version while retaining sandbox restrictions.
What steps can reproduce the bug?
Feedback ID: 01a0ab02-ac9a-7f53-9e25-bad45f540c44
What is the expected behavior?
No response
Additional information
No response
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
Start with the Windows sandbox setup and trusted Node process failure described in the report; the available sandbox.log is stale and does not contain a current failure. Done means identifying a reproducible way to rerun or repair sandbox setup in this app version while preserving sandbox restrictions and addressing the kernel reset.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- desktop, operating-systems, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100