SpaceXAI has launched Team Bots, shared Grok agents designed to work from a team’s collective context instead of serving one user at a time.
Each Team Bot can combine internal files and instructions with plugins, API credentials, and persistent memory. Teams can give a bot its own Slack handle, connect services such as GitHub, Notion, Linear, Salesforce, and Datadog, and configure recurring work such as morning briefings, bug triage, analytics queries, or brand reviews.
The shared model does not make every interaction public. SpaceXAI says individual conversations and memories remain private while approved skills and organizational context are shared.
SpaceXAI reports that its engineering Team Bot coordinated hundreds of cloud agents and helped a five-person team ship more than 100 pull requests per day while building the product. That is a vendor-reported internal result, not an independent benchmark, but it demonstrates the intended architecture: one persistent agent coordinating people, tools, and specialist agents across an ongoing workflow.
Team Bots is available in public beta on SpaceXAI’s Teams and Enterprise plans.
Why it matters
Most workplace agents still belong to an individual account or isolated chat. Team Bots treat the agent as durable infrastructure: a shared operational layer that retains decisions, follows established procedures, and can continue working as employees rotate through a project.
The product builds on the persistent identity, computer, memory, tools, and routines introduced with Grok Bot, then adds an organizational layer that multiple people can use without collapsing all of their private context into one shared transcript.
For builders, the important pattern is the combination of:
- shared organizational context;
- private user-specific memory;
- governed application and API access;
- scheduled background work;
- coordination of additional agents;
- human approval before consequential changes.
That architecture could make persistent agents more useful for software delivery, customer operations, analytics, and content workflows—provided teams carefully control permissions, credentials, and the information committed to long-term memory.