Cairn

Session RPC methods ignoring profile parameter

NousResearch/hermes-agent · cluster 62503 · dashboard

Data as of

Nothing open on GitHub. Fix merged in #70604. Check it covers your case.

The short answer

0open issues
0open PRs
7items grouped
Known?
Yes. 7 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #70604. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #70604. That is separate from the fix event.
Still open
Nothing open on GitHub.

A bug where session.* RPC methods and WebSocket dispatch ignore the params.profile field, plus related fixes to ensure sessions respect their owning profile through branching and compression.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #70604 fix(sessions): keep a conversation on its owning profile through branch and compression

    merged to main

    files: agent/conversation_compression.py, apps/desktop/src/app/session/hooks/use-session-actions.test.tsx, apps/desktop/src/app/session/hooks/use-session-actions/index.ts, hermes_state.py, tests/run_agent/test_compression_persistence.py, tests/test_hermes_state.py, tests/test_tui_gateway_server.py, tui_gateway/server.py

5 PRs closed without merging

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

  • #62509 fix(tui_gateway): honor params.profile for session.* state.db access · superseded by another PR → #70604
  • #62656 fix(gateway): respect params.profile in session.* WebSocket RPC dispatch · duplicate
  • #62836 fix(gateway): respect params.profile in session.* RPC methods · duplicate → #62509, #62503, #62656
  • #62876 fix(tui_gateway): honor params.profile in session.list and session.most_recent · duplicate
  • #63087 fix(tui_gateway): honor params.profile in session.* RPC methods · duplicate
Closed issues · 1
  • Closed#62503[Bug]: session.* RPC methods ignore params.profile in WebSocket dispatch
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.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
dashboard
Merged PRs
#70604
Closed issues
1
Attempts
5 PRs closed without merging
Fix link checked
24 Jul 2026

For your agent

The same facts, typed.

cluster/62503.json
cluster/62503.md