# NousResearch/hermes-agent · Send Hermes User-Agent to RouterMint to avoid Cloudflare 1010

## Open now

- Nothing open on GitHub.

The three members concern RouterMint requests from Hermes lacking a User-Agent header, which an issue links to Cloudflare 1010 errors. Two pull requests propose sending a Hermes User-Agent, one of them also covering model probes and one described as a salvage of #14440.

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

- #14439: RouterMint custom-provider requests can fail with Cloudflare 1010 when Hermes omits User-Agent

## Prior & competing PRs

- **#15048: fix(providers): send Hermes User-Agent to RouterMint (salvage #14440)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_cli/doctor.py`, `hermes_cli/models.py`, `run_agent.py`, `scripts/release.py`, `tests/run_agent/test_provider_attribution_headers.py`
- **#14440: fix: send Hermes user agent to RouterMint and model probes**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#15048`

## Fix status

- Merged to main in PR #15048 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-04-24`. This confirmation is old and may be out of date (a revert/reopen would not have invalidated it here); re-verify.