Cairn
NousResearch/hermes-agent

Windows codex CLI .CMD lookup errors in subprocess calls

Cluster 48510 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

The members share one theme: on Windows, launching the codex CLI via subprocess apparently does not find a .CMD wrapper because PATHEXT is not applied. One is a bug report and two are pull requests proposing to look up the binary path (e.g., via shutil.which); their outcomes are not established here.

Open issues1

  • Issue#48510[Bug]: Windows — 3 locations fail to find codex.CMD via subprocess.run/Popen (CreateProcess doesn't resolve PATHEXT)

Open PRs1

  • PR#48522fix(codex): resolve codex binary via shutil.which so Windows .CMD is found (fixes #48510)

1 PR closed without merging

From the close comments: other 1

  • #71696 fix(codex): resolve codex CLI to a launchable path on Windows (#48510) · other → #48522, #52083
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
agent
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/48510.json
cluster/48510.md