# NousResearch/hermes-agent · Duplicate message storage bug in /v1/responses turns

## Open now

- Nothing open on GitHub.

A bug in the /v1/responses endpoint causes conversation history to grow incorrectly across turns, storing messages multiple times. Related fixes address both the doubling behavior and the transcript prefix matching logic that contributes to it.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #115857. Verify it addresses your case.
- **Recommended:** read PR #115857 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-115857`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #101644: \[Bug\]: v0.21.0 named /v1/responses conversations duplicate stored history (2 turns: 3 -> 8 messages)

## Prior & competing PRs

- **#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 · fix tier `verified`
  - maintainer direction: category `merged`
  - 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`
- **#101728: fix(api-server): match /v1/responses transcript prefix semantically, not by strict dict equality**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `bd0affe5e5f723579df8902852f5d0c47795f355`

## Fix status

- Merged to main in PR #115857 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-19`.