NousResearch/hermes-agent

Per-provider session affinity header opt-in feature

Cluster 104449. Data as of 2026-10-25 11:21 UTC

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

open issues

open PRs

items grouped

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

Next step: read #115904, then check it covers your case.

Read #115904 Pick up a Lab task

These items cover adding an opt-in per-provider configuration to forward a session affinity header (e.g. a session ID) to custom gateway endpoints. The feature allows providers like LiteLLM to receive conversation scope via a configurable header name.

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.

#115904 feat(providers): custom providers can carry the Hermes session id as an opt-in header (#86241, salvage #104566, supersedes #114496)

merged to main

files: agent/auxiliary_client.py, agent/chat_completion_helpers.py, agent/opencode_affinity.py, cli-config.yaml.example, hermes_cli/config.py, hermes_cli/config_providers.py, tests/agent/test_session_affinity_header.py, tests/hermes_cli/test_gateway_migrate_multiplex.py, tests/hermes_cli/test_web_server_idle_proof.py, website/docs/integrations/providers.md, website/docs/user-guide/configuring-models.md

1 PR closed without merging

From the close comments: merged via another change 1

#104566 feat(agent): per-provider session_affinity_header (#104449) · merged via another change → d6d9fac, #115904, #86241, #104566, #114496

Closed issues · 1

Closed#104449[Feature]: Per-provider `session_affinity_header` — send the conversation affinity scope to custom gateway endpoints (e.g. LiteLLM `x-litellm-session-id`)

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.67: 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

Merged PRs: #115904
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 19 Sep 2026

For your agent

The same facts, typed.

cluster/104449.json
cluster/104449.md