OpenAI released Codex CLI rust-v0.162.0 on October 8, 2026, with a fix for Linux sandbox startup when multiple files are denied at once, a fix for ordinary drive-letter file access on Windows 10, managed Git worktree tools when enabled, and a transcript copy command.
The release sits inside a pattern common to command-line agent tools: most of the visible feature set is incremental, while the fixes address failures that block usage entirely rather than degrade it. A sandbox that fails to start under multiple denied files is not a slow or degraded session, it is a session that cannot run. Drive-letter path handling on Windows 10 is the kind of platform detail that does not show up in testing on a single operating system, which is likely why it persisted into a 0.162.0 release rather than being caught earlier.
OpenAI's release notes confirm the two fixes and the two additions but do not disclose how long the Linux sandbox bug existed in prior versions, how many denied-file configurations triggered it, or what share of Windows 10 users were affected by the path issue before the patch. That absence matters for anyone trying to estimate how much prior automation on these platforms may have silently failed or fallen back to degraded behavior.
For operators running Codex CLI in continuous integration or multi-platform fleets, the practical step is straightforward: pin to 0.162.0 or later on any Linux host that enforces sandboxing with more than one denied file, and verify Windows 10 agents can read and write across drive letters rather than assuming the prior version worked. Teams using the managed Git worktree feature should confirm it is explicitly enabled, since the release notes specify the tools apply only when that flag is set, not by default.
What is not established is whether the Linux sandbox and Windows path bugs were independent defects or shared a common cause in how Codex CLI resolves file permissions across platforms. If they are related, future releases may surface similar path or permission failures on macOS or in less common sandbox configurations. Checking release notes for fixes framed around file access, rather than new commands, is the more reliable signal for operators deciding when to upgrade a CLI tool embedded in automated pipelines.
The fixes themselves are narrow, but the dependency they expose is not: any agent tool that touches a filesystem inherits every quirk of every operating system it runs on, and 0.162.0 is a reminder that those quirks surface in production before they get documented.