Cairn
NousResearch/hermes-agent

Gmail body newline/escape handling fixes and features

Cluster 43366 · skills. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 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 2 PRs.

These items address how literal escape sequences like \n and \t are handled in Gmail send/reply body text, including a bug where \n was sent literally instead of as a line break, fixes to decode shell escapes, and a related feature to support reading body content from a file.

Open issues1

  • Issue#43366productivity/google-workspace: Gmail send/reply can send literal \n instead of line breaks

Open PRs2

  • PR#113260feat(google-workspace): add --body-file for gmail send/reply
  • PR#125217fix(google-workspace): unescape literal \n/\t in gmail/calendar/docs text args (#43366)

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #43373 fix(google-workspace): decode literal shell escapes in gmail send/reply body · superseded by another PR → #113260
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

Subsystem
skills
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/43366.json
cluster/43366.md