Giving an agent to a team sounds simple until a teammate needs to correct it, a manager leaves, or private context appears in a shared channel. In Andrew Warner's conversation with Alex McDonnell, three approaches make the trade-offs unusually clear: Grok Bot Team Bots, Hyperagent's Rooms demo, and OpenAI Dots.
Ask three separate questions before choosing a team agent: Who shares its knowledge? Who can work with it in the same conversation? Who can maintain its configuration and connections? Grok Bot shares one configured Bot but gives each person a private in-app chat; Slack creates a shared discussion. Hyperagent's demo puts people and specialist agents in one room and its documented workspaces can give multiple editors control of a workspace-owned agent. A personal Dot works on its owner's behalf; it is not automatically a team-owned agent.
Watch the Team-Agent Interview
Credit: The Next New Thing interview with Andrew Warner and Hyperagent's Alex McDonnell, published 1 October 2026. This article draws on the supplied transcript and checks product claims against the vendors' current documentation. The video is presented by Zapier; the Hyperagent referral offer is a creator promotion, not independent evidence of product quality.
Grok Bot: One Team Bot, Separate In-App Conversations
At the start of the demo, Warner creates a finance Team Bot and selects what to share: connectors, secrets, skills, and files. He withholds his personal Gmail and other private material. That small choice is the most useful part of the setup: publishing an agent should not silently publish a person's whole account.
Grok Bot's Team Bots guide confirms the boundary. Teammates use one Bot and its approved team context, but each gets a private in-app conversation. The Bot's owner controls the shared configuration; teammates cannot change its plugins, secrets, skills, or files. If colleagues need to question the Bot together, they can add the published Bot to a Slack channel or thread. That gives the discussion a shared audience, but it does not make every participant a Bot administrator.
The vendor's documentation adds a subtle access rule: OAuth plugins can act through each teammate's own account, while key-based plugins may use one Bot credential. In shared conversations, the Bot asks before using an individual's personal connector. Keep shared keys narrowly scoped, prefer read-only service accounts, and remember that a Slack thread is visible to its participants.
Hyperagent Rooms: A Shared Conversation Needs Shared Stewardship
At 04:39, McDonnell shows a Rooms prototype designed around several humans and several specialist agents in one place. In the team's paid-ads example, a performance agent, creative agent, and website agent can participate in the same work while colleagues ask follow-up questions in the same thread. This is a product demo, not a measured productivity study; the point it illustrates is continuity of the conversation.
The maintenance model is more important than the chat surface. Hyperagent distinguishes workspace-owned agents from personal agents shared into a workspace. Everyone can run either, but Owners and Editors can maintain a workspace-owned agent, while a shared personal agent remains controlled by its author. Workspace roles separate use, editing, and administration. For a business-critical agent, create it in the workspace rather than leaving its connections and operating rules with one employee.
That does not make everything in a workspace visible to everyone. Hyperagent's privacy guide says Owners can review workspace threads, while ordinary Members and Editors do not gain blanket access to colleagues' conversations. Review thread audience, shared-library visibility, and credentials separately before adding customer or financial data.
Dots: Useful Personal Agent, Different Ownership Model
Warner brings his Dot into Slack, then asks whether a colleague can interact with it and whether it might expose his private ChatGPT context. The on-camera exchange shows a response after a delay, but it does not prove that the colleague can manage the Dot or safely access the owner's personal knowledge. Treat that as an unresolved demo question, not a tested sharing guarantee.
OpenAI describes the first Dot as a personal agent that works on its owner's behalf across ChatGPT and supported messaging channels. Its workspace guidance says only a Dot's owner can direct it in Slack or Teams, where available; other people's messages do not start work for that Dot. OpenAI's separately identified specialist Dots, with organizational identities and dedicated responsibilities, are in focused enterprise pilots. Do not treat that pilot as a generally available team-agent substitute.
A Pricing Correction Worth Reading Before Sign-Up
At 12:54, the interview celebrates connecting an existing ChatGPT subscription to Hyperagent. The useful claim is narrower than "Hyperagent is free": Hyperagent says supported GPT model usage can draw from that subscription, instead of Hyperagent credits. Other models, browser sessions, search, images, and connected-service actions can still use Hyperagent credits. ChatGPT usage limits still apply.
More importantly, Hyperagent's published billing guidance says users need an active monthly Hyperagent plan to keep the ChatGPT connection working. The creator's "no payment method" interpretation in the demo is therefore not a reliable statement of current pricing. Check the plan and any referral-credit terms before committing; a bonus credit is not the same thing as an ongoing free plan.
How to Test a Team Agent Without Sharing Too Much
Start with a workflow such as a weekly project-status brief or an internal FAQ. It should need collaboration but not production writes. A credible pilot has five parts:
- One shared job: Define the trigger, source documents, expected answer, and what the agent must refuse or escalate.
- One audience: Decide whether teammates need separate private chats, one shared channel, or both. Write down who can see the resulting conversation.
- One owner and backup: Make the agent workspace-owned where the platform supports it, or document a transfer path if it does not. Give edit rights only to maintainers.
- Small access: Use fictional or approved read-only material first. Test what happens when a user asks for a personal account, a restricted document, or an external action.
- Measured review: Have two people run the same task. Record correct answers, missed context, corrections, time spent, and model or tool charges. Require approval before sending messages or changing systems.
The strongest buyer proposition is not "an AI employee." It is a repeatable team workflow that survives handoffs, preserves context without oversharing, and produces an outcome someone can verify.
Build a Business Idea From This Pattern
Use this prompt to turn the shared-context versus shared-ownership distinction into a service or product idea for a buyer you can actually reach. It works in a general AI assistant; no Grok Bot, Hyperagent, or Dot account is required to draft the plan.
Design a team-agent pilot
Three offers, one guarded validation plan.
Video Chapters
- 00:00 Create a Grok Bot Team Bot
- 03:09 Bring an agent into Slack
- 04:39 Hyperagent Rooms demo
- 06:45 Paid-ads specialist agents
- 08:42 Multiple agents coordinate
- 09:27 Agent settings and integrations
- 11:33 Workspace roles and permissions
- 12:54 ChatGPT subscription connection
- 14:24 Dot in Slack
- 16:21 Personal versus specialist Dots
- 19:39 Other models and Hyperagent billing
Sources and Useful Links
- Primary interview: Andrew Warner with Alex McDonnell; The Next New Thing resources.
- Grok Bot: official Team Bots announcement and setup, permissions, and Slack documentation.
- Hyperagent: workspace agent ownership, roles, ChatGPT connection scope, and current billing guidance.
- OpenAI: Dots launch and workspace controls.
- Creator referral: Hyperagent link mentioned in the video. The video advertises $100 in bonus credits on a paid plan; eligibility and current terms should be checked at sign-up.