NousResearch/hermes-agent

Performance fixes for registry and agent hot paths

Cluster 106062. Data as of 2026-10-24 04:06 UTC

Nothing open on GitHub. Fix merged in #120406 on 23 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

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

Next step: read #120406, then check it covers your case.

Read #120406 Pick up a Lab task

These issues and PRs address inefficient operations in tool registry lookups and agent hot paths, including unnecessary full-registry copies on single-tool lookups and quadratic or per-character work in frequently executed code.

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.

#120406 perf(agent): remove quadratic and per-character work from agent hot paths

merged to main

files: agent/agent_runtime_helpers.py, agent/codex_responses_adapter.py, agent/message_sanitization.py, agent/moa_loop.py, agent/prompt_caching.py, agent/redact.py, contributors/emails/[redacted:email], contributors/emails/[redacted:email], tests/agent/test_moa_loop_mode.py, tests/agent/test_prompt_caching.py, tests/agent/test_redact.py, tests/tools/test_registry.py, tools/registry.py

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

#106076 perf(tools): resolve registry entries without copying all tools · merged via another change → #120406
#106092 perf(tools): resolve get_entry with two O(1) lookups, not a registry copy (#106062) · superseded by another PR → #120406, #106076

Closed issues · 1

Closed#106062perf(tools): get_entry copies the full registry for every single-tool lookup

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.50: 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

Merged PRs: #120406
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 23 Sep 2026

For your agent

The same facts, typed.

cluster/106062.json
cluster/106062.md