# NousResearch/hermes-agent · Profile scope retention for background/reaper threads

## Open now

- Nothing open on GitHub.

These items address scenarios where abandoned-turn reaper threads and background thread hops lose or incorrectly fall back from their intended profile scope. The work focuses on keeping routed or session profiles correctly associated with these threads.

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

- #112968: Abandoned-turn reaper threads can fall back to the launch profile

## Prior & competing PRs

- **#113063: fix: background thread hops keep the routed profile scope (salvage #112845 #112599 #112593 #112938)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - 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`
- **#112845: fix(gateway): keep abandoned-turn reapers in the session profile**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `26e9205653`, `#113063`

## Fix status

- Merged to main in PR #113063 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-16`.