Cairn

Cron context_from truncation bug with embedded headings

NousResearch/hermes-agent · cluster 128543

Data as of

Nothing open on GitHub. Fix merged in #130599. Check it covers your case.

The short answer

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

These issues and pull requests concern a bug where the cron context_from function incorrectly truncates responses that contain embedded ## Response headings. The fixes involve preserving such headings and ensuring complete response frames survive the round-trip.

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.

  • #130599 fix(cron): context_from injects the full previous answer when it contains a "## Response" heading (#128543, salvage #128685)

    merged to main

    files: contributors/emails/[redacted:email], cron/scheduler.py, cron/scheduler_prompt.py, tests/cron/test_context_from_response_extraction.py

4 PRs closed without merging

From the close comments: merged via another change 4

  • #128555 fix(cron): preserve embedded response headings · merged via another change → dad9c56, #130599
  • #128565 fix(cron): stamp the response length so context_from can't truncate on an embedded heading · merged via another change → dad9c56, #130599
  • #128685 fix(cron): round-trip complete response frames through context_from · merged via another change → dad9c56, #130599
  • #130524 fix(cron): preserve complete context answers with compatible archive framing · merged via another change → dad9c56, #128685, #130599
Closed issues · 1
  • Closed#128543Cron context_from truncates answers containing an embedded ## Response heading
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.33: 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
#130599
Closed issues
1
Attempts
4 PRs closed without merging
Fix link checked
1 Oct 2026

For your agent

The same facts, typed.

cluster/128543.json
cluster/128543.md