Cairn
NousResearch/hermes-agent

Gmail reply recipient and non-ASCII header fixes

Cluster 74675 · skills. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 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
1 issue and 1 PR.

These issues and fixes address two related bugs in the Google Workspace Gmail integration: replies targeting the wrong recipient on own messages, and non-ASCII display names causing invalid address header errors.

Open issues1

  • Issue#74675google-workspace: gmail reply targets the wrong recipient on own messages; non-ASCII display names yield 'Invalid To header'

Open PRs1

  • PR#130883fix(google-workspace): correct gmail reply recipient, non-ASCII address headers and RE: prefix

1 PR closed without merging

From the close comments: partial fix 1

  • #74676 fix(google-workspace): correct gmail reply recipient and non-ASCII address headers · partial fix → 556b708, #74675, #74676, #1, #15803, #14532, #6, #9, #374151, #4338
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
skills
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/74675.json
cluster/74675.md