NousResearch/hermes-agent
Gateway blocks invalid workspace paths in systemd units
Cluster 131164 · gateway. Data as of
2 open items. Fix attempted, not merged.
The short answer
1open issue
1open PR
4items grouped
- Known?
- Yes. 4 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 2 PRs 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.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese items address a scenario where a dependency-generation or PM-generation workspace context incorrectly influences gateway configuration, causing bad systemd unit writes. The fixes add refusals in the gateway to reject such paths or service-definition writes originating from those workspace types.
Open issues1
- Issue#131164`hermes gateway restart` run from a dependency-generation venv script rewrites the systemd unit to a workspace launcher → crash loop "no dependency environment is committed"
Open PRs1
- PR#133030fix(gateway): bind persisted supervisor commands to the install root
2 PRs closed without merging
From the close comments: closed without comment 1 · superseded by another PR 1
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.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- gateway
- Closed issues
- 0
- Attempts
- 2 PRs closed without merging