Cairn
NousResearch/hermes-agent

Unicode normalization fixes across slash commands

Cluster 2925 · gateway. Data as of

3 open items. Fix merged in #108905. Check it covers your case.

The short answer

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

These issues and pull requests address bugs and fixes related to non-ASCII characters—curly/smart quotes and Unicode dashes—being mishandled in slash command parsing across multiple components including kanban, gateway, CLI, and Telegram. The work involves normalizing these characters to their ASCII equivalents for consistent input handling.

Open issues1

  • Issue#40915[Bug]: /kanban create fails when curly quotes wrap a title

Open PRs2

  • PR#40935fix(kanban): accept slash-command arguments delimited by curly quotes
  • PR#41018fix(cli): support smart quotes in kanban slash parser

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #108905 fix(telegram): command menu no longer rejected for Unicode dashes in descriptions (#2925, salvage #106899)

    merged to main

    files: hermes_cli/commands_platforms.py, tests/hermes_cli/test_commands.py

3 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1 · other 1

  • #2927 fix(telegram): normalize em/en dash to ASCII hyphen in bot command descriptions · other
  • #40925 fix(kanban): normalize curly quotes in slash-command input · superseded by another PR → #40935
  • #106899 fix(telegram): normalize unicode dashes in bot menu descriptions · merged via another change → 75ade17, #108905, #2925
Closed issues · 1
  • Closed#2925[Bug]: hermes-agent: normalize dashes bug report
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.23: 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
gateway
Merged PRs
#108905
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
12 Sep 2026

For your agent

The same facts, typed.

cluster/2925.json
cluster/2925.md