NousResearch/hermes-agent

Responses API history duplication bug and fix

Cluster 95137. Data as of 2026-10-30 11:57 UTC

Nothing open on GitHub. Fix merged in #115857 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 #115857. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #115857. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #115857 Pick up a Lab task

A bug in the API server causes chained conversation turns via previous_response_id to duplicate the entire message history on each turn, traced to a prefix-matching check that never matches. The members cover the bug report and related fixes addressing message identity and turn-start indexing logic.

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.

#115857 fix(api-server): chained /v1/responses turns store each message once instead of doubling history every turn (#95137, #101644, salvage #85678)

merged to main

files: contributors/emails/[redacted:email], gateway/platforms/api_server.py, gateway/platforms/api_server_openai_routes.py, hermes_cli/config_defaults.py, tests/gateway/test_api_server_responses_history_cap.py, tests/gateway/test_api_server_responses_history_dedupe.py, website/docs/user-guide/features/api-server.md

1 PR closed without merging

From the close comments: superseded by another PR 1

#95138 fix(api-server): match the turn-start prefix on normalized message identity · superseded by another PR → #70695

Closed issues · 1

Closed#95137Responses API: previous_response_id/conversation chaining duplicates entire history every turn (dict-== prefix check in _response_messages_turn_start_index never matches)

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: #115857
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 19 Sep 2026

For your agent

The same facts, typed.

cluster/95137.json
cluster/95137.md