Why are outbound emails from our shared inbox creating a weird email threading bug for Gmail users and how do we patch it today?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
Why are outbound emails from our shared inbox creating a weird email threading bug for Gmail users and how do we patch it today?
2 real searches · 1 real-search pass
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
ChatGPT real searches (2)
Classes come from the query-classifier (a local Laya model). 2 of 2 calls are low-confidence (under 50%) — hover a query in the table to see its confidence.
Searches and sources
ChatGPT2 real searches · gpt-6
Gmail email threading requirements Message-ID In-Reply-To References Gmail API threadId documentation Google ↗
RFC 5322 Message-ID In-Reply-To References email threading headers Google ↗
- RFC 5322: Internet Message Format · rfc-editor.org
- RFC 5322 · datatracker.ietf.org
- Manage threads | Gmail | Google for Developers · developers.google.com
- REST Resource: users.messages | Gmail | Google for Developers · developers.google.com
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
Gmail email threading requirements Message-ID In-Reply-To References Gmail API threadId documentation OBSERVED | Google ↗ AI Mode ↗ | — | Instruction | — | — | 1x of 1 | |
RFC 5322 Message-ID In-Reply-To References email threading headers OBSERVED | Google ↗ AI Mode ↗ | — | Reason | — | — | 1x of 1 |