Cairn
NousResearch/hermes-agent

session_search profile parameter not honored across profiles

Cluster 60789 · agent. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 2 issues already closed.
Fix event
No fix has been merged to main. 4 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

Members describe session_search with a profile= argument searching the current profile's database instead of the named one, and several pull requests propose forwarding the profile parameter in handler or dispatch calls. One title also mentions enabling FTS in read-only mode, which appears to be an additional change beyond the shared theme.

Open issues0

No open issues.

Open PRs0

No open pull requests.

4 PRs closed without merging

From the close comments: superseded by another PR 3 · duplicate 1

  • #60792 fix(agent,state): pass profile in session_search handlers + enable FTS in read-only mode · superseded by another PR → a9838c2, 57197cd, #60789
  • #60819 fix(agent): forward profile param in session_search handler calls · superseded by another PR → a9838c2, 57197cd, #60789
  • #60838 fix: forward profile param in session_search handler calls · superseded by another PR → a9838c2, 57197cd, #60789
  • #94347 fix(agent): preserve profile in session_search dispatch · duplicate → #82938
Closed issues · 2
  • Closed#60789session_search(profile=...) silently searches current profile DB instead of named profile
  • Closed#65133session_search with profile= parameter returns sessions from wrong profile (cross-contamination)
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.29: 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
agent
Closed issues
2
Attempts
4 PRs closed without merging

For your agent

The same facts, typed.

cluster/60789.json
cluster/60789.md