# NousResearch/hermes-agent · Session chat stream missing reply text in run record

## Open now

- Nothing open on GitHub.

A bug where POST /api/sessions/{id}/chat/stream marks runs as completed without storing the reply text, preventing clients that lose the stream from recovering the agent's response via GET /v1/runs/{run_id}. The accompanying fixes ensure the reply text is recorded, matching the behavior of /v1/runs.

## 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 #112305. Verify it addresses your case.
- **Recommended:** read PR #112305 (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-112305`. 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

- #111728: \[Bug\]: \`POST /api/sessions/{id}/chat/stream\` records its run as completed without the reply text — a client that loses the stream sees \`completed\` on \`GET /v1/runs/{run_id}\` and cannot recover what the agent said

## Prior & competing PRs

- **#112305: fix(api-server): session chat stream records its reply text so a dropped client recovers it from GET /v1/runs/{run_id} (#111728, salvage #93409)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `gateway/platforms/api_server.py`, `tests/gateway/test_session_api.py`
- **#93409: fix(api-server): the session stream records its reply text, like /v1/runs does**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `bb89074ef2f0849ad2f19536886540422c266997`, `#111728`

## Fix status

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