Nothing open on GitHub. Fix merged in #117630 on 20 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #117630. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #117630. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where the cron context_from self-continuity feature was injecting the previous run's prompt instead of its answer, and a related issue where head-truncation silently dropped the response marker, causing self-continuity to have no effect.
Open issues0
Open PRs0
Fixes on record
-
#117630 fix(cron): context_from self-continuity injects the previous answer, not the archived prompt (#117290, salvage #117302)
files:
cron/scheduler_prompt.py,tests/cron/test_context_from_response_extraction.py,tests/cron/test_cron_context_from.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#117302 fix(cron): inject the previous run's answer, not its prompt · merged via another change →
6bbfd63,#117630
Closed issues · 1
- Closed#117290cron context_from: head-truncation drops the previous "## Response", so self-continuity silently becomes a no-op
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.00means 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 LabAt a glance
- Merged PRs
- #117630
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 20 Sep 2026