{"repo":"NousResearch/hermes-agent","public_id":"43366","display_label":"Gmail body newline/escape handling fixes and features","summary":"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.","subsystem":"skills","counts":{"members":4,"open_issues":1,"open_issues_distinct":1,"open_prs":2,"closed_issues":0,"merged_prs":0,"attempt_prs":3},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.5},"fix_edges":[],"members":[{"kind":"issue","number":43366,"title":"productivity/google-workspace: Gmail send/reply can send literal \\n instead of line breaks","url":null,"state":"open"},{"kind":"pr","number":43373,"title":"fix(google-workspace): decode literal shell escapes in gmail send/reply body","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#113260","number":113260}],"category":"superseded_by_pr","implication":"superseded"},"merged":false},{"kind":"pr","number":113260,"title":"feat(google-workspace): add --body-file for gmail send/reply","url":null,"state":"open","close_reason":{"category":"implemented_elsewhere","implication":"superseded"},"merged":false},{"kind":"pr","number":125217,"title":"fix(google-workspace): unescape literal \\n/\\t in gmail/calendar/docs text args (#43366)","url":null,"state":"open","close_reason":{"category":"uncategorized","implication":"needs_llm"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}