# NousResearch/hermes-agent · Mixed fixes and a feature request

## Open now

- 1 issue, 1 PR open on GitHub.
- #2736: \[Feature\]: Obsidian Vault as Persistent Shared Memory Layer
- PR #2853: fix(runtime_provider): use custom provider name instead of hardcoded string

Two bug fixes address Honcho URL handling and runtime provider naming. One feature request proposes using an Obsidian Vault as a persistent shared memory layer. These members do not share a single theme.

## TL;DR

- 3 member(s): 1 open issue(s), 0 closed issue(s), 1 open PR(s), 0 merged PR(s), 1 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

- #2736: \[Feature\]: Obsidian Vault as Persistent Shared Memory Layer

## Prior & competing PRs

- **#2757: fix(honcho): graceful degradation for bad URL and add disable command**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#2757`
- **#2853: fix(runtime_provider): use custom provider name instead of hardcoded string**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`
  - files: `hermes_cli/runtime_provider.py`, `tests/test_runtime_provider_resolution.py`

## Fix status

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