NousResearch/hermes-agent

Run ownership and visibility across multiplexed profiles

Cluster 90415 · docs. Data as of

Nothing open on GitHub. Fix merged in #101256 on 2 Sep 2026. Check it covers your case.

The short answer

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

A fix and related documentation efforts addressing how run ownership is scoped to the requesting profile in a multiplexed API server setup, and clarifying that run status visibility is not fully isolated across profiles.

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.

  • #101256 fix(api_server): runs are owned by the requesting profile; handoff/readiness answer for the routed profile (#93689 #90415, salvage #93747 #100054 #94147)

    merged to main

    files: gateway/platforms/api_server.py, gateway/platforms/api_server_runs.py, hermes_cli/main.py, tests/gateway/test_api_server.py, tests/gateway/test_api_server_runs.py, tests/test_tui_gateway_server.py, tui_gateway/methods_config.py, tui_gateway/methods_session.py, website/docs/user-guide/features/api-server.md

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

  • #92822 docs(api-server): note multiplex run-status visibility · merged via another change → 16370ae, #101256
  • #94156 docs(api-server): document multiplex_profiles API isolation gap · superseded by another PR → #92822
Closed issues · 1
  • Closed#90415Docs: multiplex_profiles isolates execution but not GET /v1/runs/{id} — worth calling out explicitly
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.50: 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
docs
Merged PRs
#101256
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
2 Sep 2026

For your agent

The same facts, typed.