Focus recovery is replaying an agent suggestion that users already saw.
Fast streaming protects writing flow while duplicate state makes the same assistance look unreliable.
Who you’d be doing this for
“I had two different follow-ups appear in the same client reply, and my account lead asked which one I sent.”
Tala Ozturk · Agency Account Director
An email-heavy client-facing knowledge worker who uses Go to draft client responses in Superhuman Mail.
What is at stake
Duplicate suggestions appear in 4.8% of affected compose sessions after users return to a tab. You have to weigh a narrow client-state fix against a trigger change that affects every streamed suggestion.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- fluid streaming vs duplicate rendering
- narrow client fix vs upstream behavior change
- release speed vs regression confidence
Why Superhuman
Go’s Chrome extension puts inline assistance inside externally visible Superhuman Mail drafts.
Written with these in mind
Not your kind of problem? 30 more at Superhuman, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.