Team Bots gives colleagues a shared Grok teammate
The September launch brings shared skills, application connections and memory to a role-based bot.
THE STORY IN THREE POINTS
- Team Bots launched on September 28.
- Bots combine files, skills, plugins and memory.
- The announcement distinguishes shared expertise from private user conversations.
The announcement
The Grok team launched Team Bots on September 28 as shared agents organized around a team role or workflow. The product brings together files and instructions, plugins, credentials and memory. The announcement says colleagues share a Bot’s expertise while individual conversations and personal context remain private. It also describes Slack collaboration and internal examples in sales, engineering, marketing and analytics. These are the company’s product descriptions and case studies.
Editorial context
Shared expertise could reduce repeated explanations when several people depend on the same process. It also creates a maintenance task: someone has to own the instructions, decide which changes apply to everyone and retire stale knowledge. The editorial question is whether the shared agent makes collaboration clearer or introduces another place where conflicting assumptions can accumulate.
Editorial context: what to watch
A pilot could give one Bot a narrow job and define who can change its skills or connections. Useful measures would include repeated questions avoided, incorrect shared facts and time spent reviewing output. Testing private and shared conversations separately would help a team understand the product’s boundaries before relying on it for a broader role.
Sources: Official Team Bots launch, September 28 ↗
