Cairn

Suppress empty or silent responses in cron delivery

NousResearch/hermes-agent · cluster 5023 · cron

Data as of

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

The short answer

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

These issues and PRs address cases where cron-triggered agent responses are empty, minimal, or explicitly marked [SILENT], causing unwanted or invalid messages to be sent via Slack and Telegram. The work involves guarding against empty text in chat.postMessage and suppressing delivery when responses should be silent.

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.

  • #69317 fix(slack): sanitize outbound Block Kit payloads — invalid_blocks / msg_too_long hardening

    merged to main

    files: contributors/emails/[redacted:email], contributors/emails/[redacted:email], contributors/emails/[redacted:email], plugins/platforms/slack/adapter.py, plugins/platforms/slack/block_kit.py, tests/gateway/test_slack.py, tests/gateway/test_slack_approval_buttons.py, tests/gateway/test_slack_block_kit.py, tests/gateway/test_slack_block_kit_adapter.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #52672 fix(slack): guard against empty text in chat.postMessage (#52663) · merged via another change → #69317
Closed issues · 2
  • Closed#5023Platform-level [SILENT] response suppression for cron jobs
  • Closed#52663BLOCKER: Slack chat.postMessage no_text when cron delivers empty/minimal agent response
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.39: 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
Merged PRs
#69317
Closed issues
2
Attempts
1 PR closed without merging
Fix link checked
22 Jul 2026

For your agent

The same facts, typed.

cluster/5023.json
cluster/5023.md