# NousResearch/hermes-agent · Profile skill scan caching and concurrency fixes

## Open now

- Nothing open on GitHub.

These items address performance and correctness issues around profile skill-count scanning, focusing on cache reuse, serialization of concurrent scans, and reducing read overhead on hot paths.

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

- #107151: \[Bug\]: Concurrent profile skill scans bypass cache reuse and publish expired counts

## Prior & competing PRs

- **#120402: perf(config): cheaper config and profile reads on hot paths**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `contributors/emails/1185614+dalzio@users.noreply.github.com`, `gateway/config.py`, `gateway/config_loader.py`, `gateway/readiness.py`, `gateway/session.py`, `hermes_cli/managed_scope.py`, `hermes_cli/plugins_cmd.py`, `hermes_cli/profiles.py`, `hermes_constants.py`, `plugins/plugin_loader.py`, `providers/__init__.py`, `tests/gateway/test_gateway_streaming_nested_config.py`, `tests/hermes_cli/test_profiles.py`, `tests/test_hermes_constants.py`
- **#107137: fix(profiles): serialize cold skill-count scans**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#120402`

## Fix status

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