Cairn

Fix relative path cwd handling during dashboard respawn

NousResearch/hermes-agent · cluster 109287 · hermes cli

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 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 2 PRs.

These issues and PRs address a bug where respawning or restarting a dashboard after an update fails with ENOENT when the original launch used a relative path argument without preserving the working directory. The fixes anchor respawn behavior to the recorded launch working directory.

Open issues1

  • Issue#109287[Bug]: update respawn replays a relative dashboard argv with no cwd — ENOENT, dashboard stays down

Open PRs2

  • PR#109302fix(dashboard): restart relative launches after updates
  • PR#109305fix(cli): anchor dashboard respawn argv to the recorded launch cwd

1 PR closed without merging

From the close comments: done elsewhere 1

  • #109296 fix(cli): preserve cwd when respawning relative dashboards · done elsewhere → 3569e84, #109305, #109287, #109296, #109302
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.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/109287.json
cluster/109287.md