NousResearch/hermes-agent

Anthropic client reuse across LLM calls

Cluster 77142 · agent. Data as of

Nothing open on GitHub. Fix merged in #86764 on 15 Aug 2026. Check it covers your case.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #86764. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items concern a performance issue where the Anthropic HTTP client (including TCP and TLS connections) was being rebuilt on every LLM call rather than reused. The cluster focuses on identifying and addressing this unnecessary per-call client reconstruction.

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.

  • #86764 perf: salvage query/serialization cluster — session-search I/O, adaptive hydration, Anthropic client reuse, parallel model fetches

    merged to main

    files: agent/agent_runtime_helpers.py, agent/tool_executor.py, contributors/emails/[redacted:email], hermes_cli/model_switch.py, hermes_cli/models.py, hermes_state_search.py, run_agent.py, tests/agent/test_anthropic_request_client_reuse.py, tests/hermes_cli/test_model_cache_parallel_prefetch.py, tests/run_agent/test_token_persistence_non_cli.py, tests/test_hermes_state.py, tests/tools/test_session_search.py, tools/session_search_tool.py, website/docs/user-guide/sessions.md

1 PR closed without merging

From the close comments: merged via another change 1

  • #77144 perf(run-agent): reuse Anthropic request-local client instead of rebuilding per call · merged via another change → #86764
Closed issues · 1
  • Closed#77142Anthropic-wire request client rebuilt (fresh TCP+TLS) on every LLM call instead of reused
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

Subsystem
agent
Merged PRs
#86764
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
15 Aug 2026

For your agent

The same facts, typed.