Cairn

Preserve dependency path across managed venv relaunch

NousResearch/hermes-agent · cluster 123667 · 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 issues and fixes address a bug where the managed relaunch (-I) drops the caller's dependency path, preventing front-ends from probing the agent. The fixes ensure the committed generation's dependency path is carried through the venv_sync relaunch.

Open issues1

  • Issue#123667Managed relaunch (-I) drops the caller's dependency path, so front-ends cannot probe the agent

Open PRs2

  • PR#123672fix(cli): carry the committed generation's dependency path across the -I relaunch
  • PR#123679fix(cli): keep the managed dependency path across the venv_sync relaunch
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/123667.json
cluster/123667.md