Superhuman pushes its Go assistant everywhere
- ID
- 48285
- Status
- summarized
- Published
- 19 Nov 2026, 10:00 PM
- Fetched
- 20 Nov 2026, 2:22 AM
- Provider
- TechCrunch
- Category
- technology
- Original URL
- https://techcrunch.com/2026/11/19/superhuman-pushes-its-go-assistant-everywhere/
- Source URL
- https://techcrunch.com/feed/
Summary
- Score
- 3.5
- Created
- 20 Nov 2026, 2:22 AM
- Tags
- Audience
- developersvibe_codersai_agent_userssaas_founders
What happened
Superhuman (formerly Grammarly) is expanding its Go assistant beyond inline writing help: Go now learns context across connected tools, runs proactively against your calendar and email to draft replies, and manages other agents. The rollout adds 20 connected agents via a Go SDK — including DeepL, Legora, Amplitude, Databricks and Blackboard — plus native agent support in Docs, background task routines triggered by events, and enterprise search across a company knowledge base and connected tools. Go also replaces AI as the central tool in Superhuman Mail, and follows the September acquisition of notetaker Fathom with live collaborative notetaking and post-meeting actions like drafting an initial proposal.
Why it matters
The concrete decision here is whether to build on Superhuman's Go SDK as a distribution channel for your own agent — the 20 launch partners (DeepL, Databricks, Amplitude, Blackboard, Legora) show the shape of what gets listed — versus treating Go as a competitor to your inbox/docs workflow. If you do adopt it, the proactive mode (watching email and calendar, auto-drafting) and event-triggered routines mean you're granting standing permissions, not one-off prompts, so scope those before enabling. Nothing in the text gives pricing, availability dates, or an independent evaluation, so treat the personalization and 'manages other agents' claims as unverified.
Discussion angle
An assistant that 'manages other agents' and acts proactively on your inbox and calendar is a permissions and audit problem more than a UX one — what would you need (logging, dry-run mode, approval gates) before letting it send on your behalf?