# NousResearch/hermes-agent · Cap proxy error response body reads in gateway

## Open now

- 1 issue, 1 PR open on GitHub.
- #55015: Gateway proxy mode reads error responses without a body cap
- PR #55016: fix(gateway): bound proxy error response reads

These issues and pull requests address unbounded reading of error response bodies in gateway proxy mode, which risks memory exhaustion. The work involves adding a size limit to proxy error response reads.

## TL;DR

- 3 member(s): 1 open issue(s), 0 closed issue(s), 1 open PR(s), 0 merged PR(s), 1 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. 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.

## Open related issues

- #55015: Gateway proxy mode reads error responses without a body cap

## Prior & competing PRs

- **#55016: fix(gateway): bound proxy error response reads**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`
  - files: `gateway/run.py`, `tests/gateway/test_proxy_mode.py`
- **#55251: fix: cap proxy error response body to prevent memory exhaustion**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#55016`

## Fix status

- No merged fix on record.
- Subsystem: `gateway`