# NousResearch/hermes-agent · Windows stress test Hermes subprocess harness and CI

## Open now

- Nothing open on GitHub.

These items address running standalone kernel stress scripts in CI and fixing the Windows stress test harness to correctly invoke the installed Hermes binary via a native shim. The work centers on improving stress test infrastructure for Windows environments.

## 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

- #93136: Windows stress subprocess harness can silently run the installed Hermes binary

## Prior & competing PRs

- **#93173: fix(test): native hermes shim for Windows stress e2e (#93136)**. closed without merge
  - maintainer direction: category `stale_abandoned`; implication `active`
- **#93210: ci(stress): run standalone kernel stress scripts**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#93135`, `#93136`, `#93137`

## Fix status

- No merged fix on record.