Expose Message-ID and threading headers in message JSON
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start with the hey thread read --json output and the SDK's GetMessage to see which message fields are currently returned. First check whether the HEY API response includes Message-ID, In-Reply-To or References at all, since that decides whether this is a model and JSON change or needs raw source access. Done means the chosen fields (or the raw source) appear in the JSON output for a message, confirmed against version 1.8.0. The issue leaves open which of the two approaches to take, so confirm that with a maintainer first.
Written by the indexing model from the issue text.
Description
hey thread read --json and the SDK’s GetMessage currently return HEY’s internal IDs, but not the email headers Message-ID, In-Reply-To, or References. I also couldn’t find a way to retrieve the raw message source.
I’m migrating to HEY and collecting mail from several external addresses, so the same email can appear in more than one mailbox. Without the original Message-ID, I have to match those copies by sender, subject, and timestamp, which isn’t reliable. The threading headers would also help reconstruct conversations that started outside HEY.
Could the message model and JSON output expose these fields where available?
message_idin_reply_toreferences
Alternatively, access to the raw message source would let me extract the headers myself.
Tested with version 1.8.0.
Related: #468, which covers outgoing mail only.
- Dominant language
- Go
- Stars
- 409
- Forks
- 49
- Avg merge
- 23h 49m
- Merged PRs (30d)
- 70
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from basecamp/hey-cli
-
TUI Calendar: Enter does nothing on a highlighted event (Day/Week), though the help bar shows "enter: open"Possibly taken @albertreig claimed this 33 days ago. OpenCLI Only
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
CLI Only
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
basecamp/hey-cli#408 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
basecamp/hey-cli#556 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 18/100
Maintainers usually reply within 1 day
All issues in basecamp/hey-cli
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
product/backlog
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
TencentBlueKing/bk-nodemgr#3645 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
modelcontextprotocol/go-sdk#1387 ·
Maintainers usually reply within 1 day
-
docs(prompt): filer socket fragment hardcodes an issue-intent cap of 8 that Chore runs overrideOpenagent-butler-finding chore
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
jordansmall/spindrift#5128 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 2 days