Repository navigation
research: W7 verify actual Codex interoperability on Windows #152
Description
Purpose
Follow-up W7 from #122 and merged PR #144. The initial Rust feasibility evaluation is complete; this issue tracks one remaining evidence gate. Windows remains unsupported by the production CLI.
- Scope: the pinned upstream release (section 2) runs in a disposable
CODEX_HOME. A read-only observer checks the coordination and thread lock
ranges and share modes against the fixture model: Rust stdLockFileEx(0, u32::MAX, u32::MAX)versus the fs-ext0..0xffff0000emulation. - Evidence: a hypothesis-compared JSONL record with binary version/SHA,
token integrity and host policy recorded, plus checks on a host where
Defender is already enabled and third-party openers can be observed.
Changing protection or execution policy requires separate authorization. - Acceptance: every hypothesis
match. No real user Codex home is read. - Existing coverage: fixture range conflicts (Win32 33) only.
Delivery boundary
Use an isolated, unpublished research change with synthetic fixtures first. Record source/binary revisions, environment, hypotheses, actual outcomes and unverified conditions. Keep safeToUnlock=false; completing this gate alone does not authorize recovery or release. No production lock files, real user sessions, host policies or privileges are changed as part of this issue definition.
The proposed architecture keeps the TypeScript CLI. A Rust helper can be reconsidered after W1–W3 establish a concrete need; a full rewrite is deferred. W7 observations are prerequisites for the native classification portion of W3 and for W5; W6 must cover each integrity level claimed. W4 and W5 remain required for any automatic recovery design.
Priority: P3 research.
Milestone v0.4.7 is a planning target, not a Windows support or publication promise.
Source contract: Windows/Rust evaluation.
Activity
[-]research: W7 Windows real codex interoperability on windows (prerequisite for w3 and w5)[/-][+]research: W7 verify actual Codex interoperability on Windows[/+]abruption commentedon Oct 21, 2026
Windows work is now prioritized in Windows support (Rust), milestone #13, separately from deferred v0.4.8 work. Prototype PR #164 merged as
22857b3eb14b89976673830c601e54f52a42c217; its final head passed 41/41 checks and the main CI completed successfully. No release or package publication was performed.New designated-host evidence is in #168 (
5bec98c):held.unknown/open_existing_failed(Win32 2), not a measured free lock.This establishes native guarded contention under the measured Medium/NTFS configuration. It does not prove the native lock's entire range, holder attribution or safe third-party release. Defender remained disabled; other environments/modes and the High-token owner/DACL policy remain open. W6/W7 are not marked complete and automatic recovery remains no-go (
safeToUnlock=false).