Cron job output wrapping and header suppression

NousResearch/hermes-agent · cluster 24020 · cron

Data as of

4 open items. Fix attempted, not merged.

The short answer

2open issues
2open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
2 issues and 2 PRs.

These issues and PRs concern removing or optionally suppressing the 'Cronjob Response' wrapper and header from no_agent cron job delivery output. Work spans a reported bug, fixes, and a new no_header option feature.

Open issues2

  • Issue#24020feat(cron): add no_header option to suppress 'Cronjob Response' prefix in delivery
  • Issue#57647no_agent cron 投递在 Telegram 上仍包含 "Cronjob Response" 封装层

Open PRs2

  • PR#52275feat(cron): add no_header option for clean delivery output
  • PR#57688fix(cron): deliver no_agent job output verbatim without the response wrapper

1 PR closed without merging

From the close comments: duplicate 1

  • #57773 fix(cron): skip delivery wrapping for no_agent jobs (#57647) · duplicate → #57688, #57647
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.34: 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

Subsystem
cron
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.