Superhuman Go is here: AI that comes to you

[Ruggy-Joesten]

Hey all!

Today we launched Superhuman Go, our biggest Go update yet.

Shishir summed up the problem really well: even when AI is helpful, it can still feel like a detour. You have to stop what you’re doing, open a separate chat, explain the context, wait, then copy the answer back into your work.

Go is designed to remove that detour.

With Go, AI shows up where you already are: in your docs, inbox, browser tabs, and workflows. It can understand what you’re working on, bring in the right agent, and help without making you switch contexts.

A few highlights from the launch:

You can now build your own agents. Describe what you want, choose what should trigger it, connect the apps it should use, and Go can help create the agent for you.

Pre-built agents like the Knowledge Checker agent can verify claims against company data, catch outdated numbers, and help fix inaccuracies before you send or publish.

Go now works across more surfaces, including the Go app, Go Online, Go at Your Cursor, and Slack. It can also run in the background, search the web, ask clarifying questions, create shareable docs, and learn your preferences over time.

You can read the full launch post here: Go 1.0: Custom, Proactive Agents Everywhere You Write

We’d love to hear what you think! What kind of agent would you build first? And where would it save you the most time?

[Neil_Lavitt1]

BTW is there a way that I can exclude some SUperhuman (Coda Docs) from the sources for the agent. It seems like it is all or nothing right now and the agent I created that searches this seems to retrieve information even from Docs that I have archived. Clearly this is not what we want.

[Max_OBrien]

This topic has turned into a thread about account access.
Perhaps those posts need to be moved to a separate thread, @Ruggy-Joesten?

My 2 big reactions to this announcement are…

(1) Do not surprise us like this ever again! This forum (and several special Slack channels) are to be used to give advanced heads-up to champions and consultants of upcoming product announcements.

My clients are already building advanced Agentic Workflows using Superdocs. Now suddenly they see a ‘launch’ of a whole new and exciting feature in that same space.

But when they reach out to me for information, I had NO FLIPPING IDEA what they are talking about!

So many other NPI features are shared with us under NDA in Beta Test Programs.
Yet the MOST significant launch in the area of AI is not even hinted at?

TO SAY I AM DISAPPOINTED AND ANNOYED BY THIS
IS A POLITE UNDERSTATEMENT!

(2) HOW DO WE CREATE THESE NEW AGENTS?

The launch material is full of hype and a ‘kind’ of demo (is it real? or just demo ware?).
@noah presents some VERY powerful arguments and a rough demo - but neither myself nor my clients can see how to actually use the darn thing!

The launch video shows an amazing Dialog Modal where a user can fill out the Agent Name, Description, Instructions, Triggers, etc. Looks fantastic. But where is it?

TO SAY MY CLIENTS ARE DISAPPOINTED AND ANNOYED BY THIS
IS A POLITE UNDERSTATEMENT!

I should probably say I am sorry for all the capitalized SHOUTING in this post.
But the truth is; I am not sorry!

I am working my ass off to keep my most advanvced clients from moving to Notion.
Selling them the vision and promise of the great things being developed by the SH AI Teams.

Then THIS happens!
Seriously, I am losing my Faith, my Committement, and my Loyalty to this platform.
My clients are even further down this pipe, past the s-bend, and well on the way to the sewers!

Get it together guys - there is not much time left!

Max

[Elise_Tarabiscode.com]

I fully echo @Max_OBrien 's frustration here.

On my end, a prospect brought up these new Agent features and asked for my take on them, and that’s genuinely how I found out they existed. I had no idea these were even coming, let alone launching on that date. So there I was, expected to be the expert in the room, commenting on a feature I knew nothing about, learning it from someone outside the company.

But here’s what really gets me. After several back-and-forths with support, I finally got clarity on one thing: paid “à la carte” packs aren’t supported by the new bundle. That means migrating to the bundle would put those packs at risk of being lost. So anyone relying on “à la carte” packs is essentially stuck, they can’t migrate. And without migrating, they can’t access any of these new Agent features. In other words, you’re locking out some of Coda’s most advanced users, the very ones who invested in “à la carte” packs to go further than the base offering.

I love this product, and I spend a lot of time continuously training myself just to keep up with its evolution. But right now, it’s genuinely hard to keep up.

Honestly, I’m really disappointed. I don’t understand why Coda users, especially the most advanced ones, keep getting left behind. It’s such a shame.

[Ruggy-Joesten]

I know this is frustrating, and as we chatted about a bit offline, I’m truly sorry for the way this rolled out and caught you and others off guard. I especially understand how difficult that is when you are actively helping clients understand and adopt what we’re building.

A few of the plan-level differences are covered on the Go plans page, but I’ll expand on my understanding of the custom-agent access piece in case that’s what your clients are running into.

Custom agents are available on paid Go plans, but access varies by tier. Pro is the starting point for creating your own custom agents, while Business and Enterprise expand what teams can do with custom agents, especially around broader team workflows, sharing, and administration.

So if someone is watching the launch material and does not see the same “create an agent” or builder experience in their own account, it may not mean they are missing an obvious button. It may be related to their plan, workspace settings, admin configuration, or migration state. I would need more specific info on each client to help diagnose.

That said, I do want to take this back internally for an audit to make sure we have the clearest community-facing answers for:

• Where to go to create a custom agent
• More granularity around how access differs by plan
• What to check if the builder shown in the demo is not visible in your account
• How bundle migration affects folks using paid à la carte packs

And to both you and @Elise_Tarabiscode.com on the advance-notice and enablement point: I hear you both. I’m sorry that either of you was put in a position where you had to hear about Go for the first time from clients or prospects, without the context you needed to support them confidently.

This launch was tested internally, but I do think we missed an opportunity to get better enablement materials in front of many of you who are often the ones helping others understand what changed. If there had been a broader alpha or beta opportunity for this community, the two of you would be exactly who I would want involved.

I’m going to work with our teams to make sure this feedback is heard clearly, especially around advance notice, migration edge cases, and practical “how do I actually use this?” guidance. Y’all are some of the most invested and knowledgeable people in this community, and I really hope this moment does not make you feel like that investment is taken for granted.

[Christiaan_Huizer]

@Ruggy-Joesten

Y’all are some of the most invested and knowledgeable people in this community, and I really hope this moment does not make you feel like that investment is taken for granted.

To me it feels like the community is maybe too small or not relevant enough to be taken serious by the internal marketing departments.

[Ruggy-Joesten]

It’s definitely not that. It’s more a case of the left hand not talking to the right hand in this instance. Something I’m trying to get ahead of to avoid any future instances like these. Community is, and always will be, central to how we operate.