Never let the LLM write the subject line
Never let the LLM write the subject line6th August, 2026·Posted in Email, Llm, Aws·By Dušan DželebdžićPhoto by engin akyurt on Unsplash The Fix (TL;DR)1.Gmail threads on References and a matching subject. You need both.2.Derive the reply subject in code: Re: <original>, never from the model.3.Carry the inbound Message-ID all the way to the send and set In-Reply-To / References.✓The LLM writes the body. The plumbing writes the envelope.I'm building biro.works, a website studio where AI agents handle the first line of everything: a lead emails us, an agent drafts the reply, a human approves it, the reply goes out.
- ▪Never let the LLM write the subject line6th August, 2026·Posted in Email, Llm, Aws·By Dušan DželebdžićPhoto by engin akyurt on Unsplash The Fix (TL;DR)1.Gmail threads on References and a matching subject.
- ▪You need both.2.Derive the reply subject in code: Re: <original>, never from the model.3.Carry the inbound Message-ID all the way to the send and set In-Reply-To / References.✓The LLM writes the body.
- ▪The plumbing writes the envelope.I'm building biro.works, a website studio where AI agents handle the first line of everything: a lead emails us, an agent drafts the reply, a human approves it, the reply goes out.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,858 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | ddz.dev LLC |
| Canonical URL | https://ddz.dev/blog/llm-subject-line-gmail-threading/ |
| Publication time | Thu, 06 Aug 2026 14:40:52 +0000 |
| Retrieval time | 2026-08-06T14:50:42.668Z |
| Last seen | 2026-08-06T14:50:42.668Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | f_pRA0F0xd3F · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Never let the LLM write the subject line6th August, 2026·Posted in Email, Llm, Aws·By Dušan DželebdžićPhoto by engin akyurt on Unsplash The Fix (TL;DR)1.Gmail threads on References and a matching subject. You need both.2.Derive the reply subject in code: Re: <original>, never from the model.3.Carry the inbound Message-ID all the way to the send and set In-Reply-To / References.✓The LLM writes the body. The plumbing writes the envelope.I'm building biro.works, a website studio where AI agents handle the first line of everything: a lead emails us, an agent drafts the reply, a human approves it, the reply goes out. The pipeline worked.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at ddz.dev LLC.
Discussion
0 commentsMore from ddz.dev LLC
