Cairn
NousResearch/hermes-agent

Voice vs. audio attachment handling in cron and gateway delivery

Cluster 132120 · cron. Data as of

Nothing open on GitHub. Fix merged in #143800 on 24 Oct 2026. Check it covers your case.

The short answer

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

Members concern how audio is delivered as voice notes versus attachments: one reports cron media delivery dropping the [[audio_as_voice]] flag for Telegram, and one proposes forwarding the voice flag in cron's send_voice call. A third addresses gateway behavior for plain audio on Discord and similar platforms, which is related but a distinct change.

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.

  • #143800 fix(gateway): send plain audio as an attachment, not a voice note (Discord + siblings, salvage #132126)

    merged to main

    files: cron/scheduler_delivery.py, plugins/platforms/bluebubbles/adapter.py, plugins/platforms/discord/adapter_media.py, plugins/platforms/feishu/adapter.py, plugins/platforms/whatsapp/adapter.py, plugins/platforms/whatsapp_cloud/adapter.py, tests/cron/test_scheduler_media_voice_flag.py, tests/gateway/test_discord_audio_delivery.py, tests/gateway/test_feishu_audio_delivery.py, tests/gateway/test_plain_audio_not_voice_note.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #132126 fix(cron): forward the voice flag when cron delivery calls send_voice · merged via another change → 43cc33e, #143800
Closed issues · 1
  • Closed#132120[Bug]: Cron media delivery drops `[[audio_as_voice]]`, so a cron job's TTS reply never arrives as a Telegram voice bubble
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.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
#143800
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
24 Oct 2026

For your agent

The same facts, typed.

cluster/132120.json
cluster/132120.md