# NousResearch/hermes-agent · Windows ARM64 agent-browser spawn EFTYPE fix

## Open now

- Nothing open on GitHub.

These items address a spawn failure with EFTYPE error when running the agent-browser on Windows ARM64. The focus is on preferring a native Windows ARM64 binary to avoid the issue.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #77051: agent-browser spawn fails with EFTYPE on Windows arm64

## Prior & competing PRs

- **#77093: fix(browser): avoid EFTYPE spawn on Windows ARM64 agent-browser**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `3d12e86ef13`
- **#121470: fix(browser): prefer a native Windows ARM64 agent-browser binary**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `3d12e86ef1`, `27df3b8847`

## Fix status

- No merged fix on record.
- Subsystem: `agent`