Cairn
NousResearch/hermes-agent

Oneshot YOLO env var timing and ordering fixes

Cluster 86526 · hermes cli. 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.

These items address a race condition where HERMES_YOLO_MODE (and related env vars) were set too late, after plugin/hook discovery had already started. Fixes enforce correct ordering so the env is established before startup routines read it.

Open issues1

  • Issue#86526oneshot (-z): HERMES_YOLO_MODE set after plugin discovery starts — yolo freeze can latch False before the env is set

Open PRs1

  • PR#115654fix(oneshot): set HERMES_YOLO_MODE and HERMES_ACCEPT_HOOKS before startup discovery

1 PR closed without merging

From the close comments: closed without comment 1

  • #87640 fix(cli): batch resume dedup, oneshot yolo ordering, atomic update locks · closed without comment
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
hermes cli
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/86526.json
cluster/86526.md