# NousResearch/hermes-agent · Preserve dependency path across managed venv relaunch

## Open now

- 1 issue, 2 PRs open on GitHub.
- #123667: Managed relaunch (-I) drops the caller's dependency path, so front-ends cannot probe the agent
- PR #123672: fix(cli): carry the committed generation's dependency path across the -I relaunch
- PR #123679: fix(cli): keep the managed dependency path across the venv_sync relaunch

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.

## TL;DR

- 3 member(s): 1 open issue(s), 0 closed issue(s), 2 open PR(s), 0 merged PR(s), 0 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Open related issues

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

## Prior & competing PRs

- **#123672: fix(cli): carry the committed generation's dependency path across the -I relaunch**. open
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `ef50926c50`, `acef88c402`
  - files: `hermes_cli/venv_sync.py`, `tests/hermes_cli/test_update_launch_completion.py`
- **#123679: fix(cli): keep the managed dependency path across the venv_sync relaunch**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`
  - files: `hermes_cli/venv_sync.py`, `tests/hermes_cli/test_update_launch_completion.py`

## Fix status

- No merged fix on record.
- Subsystem: `hermes_cli`