Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

feat(gmail): make gmail get --format raw text output the exact message, like drafts get --format raw

Open Beginner friendly
#1,276 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
go
Domain
cli

Research direction

Read internal/cmd/gmail_get.go around the raw text output and compare it with internal/cmd/gmail_drafts.go around drafts raw output. Check the workflow guidance in docs/gmail-workflows.md for the documented behavior. Done means gmail get --format raw text produces the exact decoded RFC 822 bytes without a heading or added newline, while IDs remain available through --json.

Written by the indexing model from the issue text.

Description

clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster P3

Summary

gmail get --format raw and gmail drafts get --format raw behave differently in text mode. drafts get writes the exact RFC 822 bytes, so > message.eml works. gmail get adds id, thread_id, and label_ids lines, a blank line, and a trailing newline, so the redirected file is not a valid .eml.

Current (v0.47.1)

gog --account [email protected] gmail get MESSAGE_ID --format raw > message.eml
head -4 message.eml
# id	MESSAGE_ID
# thread_id	THREAD_ID
# label_ids	INBOX,...
#

Suggested

Make gmail get --format raw text output match drafts get --format raw: the exact bytes, with no heading and no added newline. The IDs stay available in --json. If the heading matters for existing users, an --out <file> flag that writes the exact bytes would also cover saving a message as .eml.

Environment

gog v0.47.1 (also on main at 82e7fd6).

Dominant language
Go
Stars
8.5k
Forks
721
Avg merge
20h
Merged PRs (30d)
59

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openclaw/gogcli

All issues in openclaw/gogcli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.