Cairn
NousResearch/hermes-agent

Gateway slot registration after profile import

Cluster 69163 · 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 bug where the gateway service or slot is not properly registered following a profile import, causing 'no such gateway' errors. The fixes involve ensuring gateway registration occurs after the import process completes.

Open issues1

  • Issue#69163[Bug]: no such gateway 'coder': register it with `hermes profile create coder` first, or pass an existing profile name via `-p <name>`

Open PRs1

  • PR#69165fix(profiles): register s6 gateway slot after profile import

1 PR closed without merging

From the close comments: duplicate 1

  • #69361 fix(profiles): register gateway service after profile import (#69163) · duplicate → #69165, #69163
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/69163.json
cluster/69163.md