# NousResearch/hermes-agent · Cron job prompt-cache scope stability for Codex sessions

## Open now

- Nothing open on GitHub.

The three members all concern how cron jobs derive their prompt-cache scope in the Codex transport, including a mention of the legacy cron_<job>_<timestamp> session id and the goal of having repeated fires share one scope. The titles do not show what the final behavior is or whether any change was merged.

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

- #139434: codex transport: cron prompt-cache scope still keys off the legacy cron_<job>_<timestamp> session id

## Prior & competing PRs

- **#139876: fix(cron): every fire of a cron job shares one prompt-cache scope (#139434, salvage #139440)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `agent/transports/codex.py`, `gateway/session_cron.py`, `tests/agent/transports/test_codex_transport_cron_scope.py`
- **#139440: fix(cron): stabilize Codex cache scope for local sessions**. closed without merge
  - maintainer direction: category `wontfix_bydesign`; implication `wontfix`; refs `e912bdbdffb`

## Fix status

- Merged to main in PR #139876 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-10-16`.
- Subsystem: `agent`