# NousResearch/hermes-agent · Memory setup fallback when uv unavailable

## Open now

- Nothing open on GitHub.

These issues and PRs concern failures when memory or dependency setup relies on uv but uv is not present (e.g., in Docker), and proposed fixes to fall back to pip or ensurepip. No resolution status is assumed.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #38668. Verify it addresses your case.
- **Recommended:** read PR #38668 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## 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.

## Closed / duplicate issues

- #5950: \[Bug\]: memory setup uses uv and fails in docker

## Prior & competing PRs

- **#38668: fix(memory): fall back to pip when uv is unavailable (salvage #5954)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_cli/memory_setup.py`, `tests/hermes_cli/test_memory_setup_provider_arg.py`
- **#5954: fix(memory):  #5950 fallback to pip when uv is not available during p…**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `30c7b787d`, `#38668`

## Fix status

- Merged to main in PR #38668 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-06-04`.
- Subsystem: `environments`