Cairn
NousResearch/hermes-agent

Non-interactive hook consent acceptance in hermes CLI

Cluster 138413 · hermes cli. Data as of

3 open items. Fix attempted, not merged.

The short answer

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

These items all concern how hermes hooks accept, --accept-hooks, and HERMES_ACCEPT_HOOKS=1 behave in non-TTY environments, with one issue reporting they don't accept hooks and two pull requests proposing a non-interactive accept path for the consent allowlist. Whether any change addresses the problem is not established by the titles.

Open issues1

  • Issue#138413Non-TTY environments: `hermes hooks accept` / `--accept-hooks` / `HERMES_ACCEPT_HOOKS=1` don't accept hooks (direct allowlist write is the only working path)

Open PRs2

  • PR#138419fix(cli): add a non-interactive `hermes hooks accept` for the consent allowlist
  • PR#138421fix(hooks): `hermes hooks accept` records non-TTY consent instead of being inert (#138413)
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
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/138413.json
cluster/138413.md