NousResearch/hermes-agent

Context propagation lost across background thread scheduling

Cluster 112965. Data as of 2026-10-26 12:29 UTC

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

open issues

open PRs

items grouped

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

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

Read #113063 Pick up a Lab task

These items address a problem where scheduling context or routed profile scope is not preserved when periodic scheduler callbacks execute on worker threads. The group covers the bug report and related fix attempts targeting context propagation across background thread hops.

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.

#113063 fix: background thread hops keep the routed profile scope (salvage #112845 #112599 #112593 #112938)

merged to main

files: agent/account_usage.py, agent/billing_usage.py, agent/periodic_scheduler.py, gateway/platforms/api_server.py, gateway/run_agent_cache.py, tests/agent/test_nous_usage_profile_context.py, tests/agent/test_periodic_scheduler_context.py, tests/gateway/test_reaper_profile_scope.py, tests/tools/test_async_delegation_stale_profile_scope.py, tools/async_delegation.py

1 PR closed without merging

From the close comments: merged via another change 1

#112938 fix(agent): preserve context across periodic scheduler callbacks · merged via another change → 26e9205, #113063

Closed issues · 1

Closed#112965PeriodicScheduler callbacks lose the scheduling Context on worker threads

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

Merged PRs: #113063
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 16 Sep 2026

For your agent

The same facts, typed.

cluster/112965.json
cluster/112965.md