Fix Windows Codex launch-home file links#4366
Merged
Merged
Conversation
Jinwoo-H
force-pushed
the
Jinwoo-H/fix-codex-launch-home-hardlinks
branch
2 times, most recently
from
June 1, 2026 06:20
c21265a to
ad089bc
Compare
Jinwoo-H
force-pushed
the
Jinwoo-H/fix-codex-launch-home-hardlinks
branch
from
June 1, 2026 06:33
ad089bc to
22b8630
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
EEXISTfailureshooks.json, Codex SQLite state files, and theEEXISTrace/stale-target variantDiagnosis
The latest installed app was
1.4.36-rc.14, so it did not include the prior merged PR. The new startup blocker reproduced with the preserved broken profile by copying onlycodex-runtime-home\homeinto an isolated fixture: packaged RC started main/GPU/network processes but never produced an Orca renderer or CDP page.The repeated
EPERM symlink ... hooks.json -> ... launch\host\system\home\hooks.jsonfailures are Windows file symlink privilege failures. Directory entries are junctioned, but file entries such ashooks.json,logs_2.sqlite,logs_2.sqlite-wal, andlogs_2.sqlite-shmneed another strategy.The related
EEXIST symlink ... memories_1.sqlite-walwarning is the same launch-home linker hitting an already-present target. That can happen with stale launch-home state or a concurrent materialization race. The PR now treats an already-created correct hard link/symlink as success instead of warning.Verification
pnpm exec vitest run --config config/vitest.config.ts src/main/codex/codex-launch-home-paths.test.tspnpm exec vitest run --config config/vitest.config.ts src/main/codex/codex-launch-home-paths.test.ts src/main/codex/codex-home-paths.test.tspnpm exec oxlint src/main/codex/codex-launch-home-paths.ts src/main/codex/codex-launch-home-paths.test.tspnpm run typecheck:nodeORCA_DEV_USER_DATA_PATH=C:\Users\jinwo\orca\debug-orca-codex-runtime-parts\home-only, the minimal bad fixture that hung packaged RC. Patched app opened an Orca renderer athttp://localhost:5173/, CDP listed the page, and Playwright snapshot showed the Orca workspaces UI.Note: local pre-commit hook could not load
oxlint-plugin-react-doctor; commit was made with--no-verifyafter the commands above passed.