Skip to content

Fix npm-installed Codex detection for v1.0.1 - #6

Merged
causercode merged 1 commit into
mainfrom
fix/npm-codex-detection-v1.0.1
Sep 22, 2026
Merged

causercode merged 1 commit into
mainfrom
fix/npm-codex-detection-v1.0.1

Conversation

@causercode

Copy link
Copy Markdown
Owner

Summary

  • detect npm-installed Codex CLI on Windows by treating codex.cmd and codex.ps1 as discovery anchors
  • resolve only the expected native x64 or ARM64 executable from bounded nested and hoisted npm package paths
  • preserve configured, standalone, and direct PATH executable precedence
  • report npm-specific executable provenance in Settings
  • target this patch for v1.0.1

Fixes #5

Verification

  • Release build succeeds
  • Automated tests pass
  • Formatting check passes
  • Package vulnerability audit passes
  • Relevant manual UI and accessibility checks were completed (not applicable; no UI layout or interaction changes)

Security and privacy

Process launching is affected. npm shell shims are never executed or returned; they are used only as anchors for exact, architecture-specific native executable paths. Candidates still must be fully qualified existing .exe files. No credential, provider communication, logging, storage, or startup behavior changes.

@causercode
causercode merged commit b981e20 into main Sep 22, 2026
6 checks passed
@causercode
causercode deleted the fix/npm-codex-detection-v1.0.1 branch September 22, 2026 00:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Automatic Codex detection fails for npm-installed Codex on Windows

2 participants