Cairn
NousResearch/hermes-agent

Cron child output UTF-8 decoding bug on Windows

Cluster 115894. Data as of

Nothing open on GitHub. Fix merged in #116725 on 20 Sep 2026. Check it covers your case.

The short answer

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

These items address a bug where cron bot-chat delivery incorrectly decodes child process output using cp1252 on Windows instead of UTF-8, causing accented characters and failure diagnostics to be silently lost. The fixes apply UTF-8 (with lossy fallback) when reading that output.

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.

  • #116725 fix(cron): bot-chat delivery keeps accented replies on Windows and stray bytes no longer kill cron child output (#115894, #105582, salvage #105597)

    merged to main

    files: cron/scheduler_delivery.py, cron/scheduler_script.py, tests/cron/test_cron_bot_chat_delivery.py, tests/cron/test_cron_script.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · won't fix / by design 1

  • #105597 fix(cron): decode cron child output lossily, and as UTF-8 on Windows bot-chat delivery (#105582, #115894) · won't fix / by design → #115894, #115910
  • #115910 fix(cron): decode bot-chat delivery child output as UTF-8 on Windows · done elsewhere → b9f4b88, #116725, #115894, #105582, #105597
Closed issues · 1
  • Closed#115894[Bug]: cron bot-chat delivery decodes the child's output as cp1252 on Windows — captured reply and failure diagnostic are silently lost
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.50: 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
#116725
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
20 Sep 2026

For your agent

The same facts, typed.

cluster/115894.json
cluster/115894.md