A preview shows users inspecting a bot's instructions, memories, skills, routines and integrations before adding it to a team.
By Ryan Merket · Published
Primary source: X - @blankspeaker
Why it matters #
A marketplace for complete Bots would let developers distribute reusable AI workers, not just integrations. Those workers can inherit routines and operate inside a shared, authenticated cloud computer, making review and permissions central to adoption.
SpaceXAI appears to be preparing a Grok Bot Marketplace that will let users add third-party AI teammates directly to their existing bot teams, extending the product's current plugin catalog into a distribution channel for complete agent configurations.
https://x.com/blankspeaker/status/2093399672803176787 The feature surfaced on August 28th in a two-post thread on X from Grok community moderator @blankspeaker, who posted a video of the interface. The preview divides the marketplace into two categories: Plugins, which are already available, and Bots, which the post described as coming soon.
The distinction matters. Plugins connect an agent to a service or package a narrower capability. A marketplace Bot would arrive as a reusable worker with its own instructions and operational setup. According to the preview, users will be able to inspect a Bot's instructions, memories, skills, routines and integrations before adding it to a team.
That turns Grok Bot's marketplace from a connector directory into a potential distribution system for agent developers. A builder could package a sales researcher, recruiting coordinator or support operator instead of asking every customer to recreate the role, prompts, tools and recurring workflows from scratch.
From shared links to a catalog
SpaceXAI already allows users to share individual Bots through public links. Its Bot management documentation says a recipient can preview a shared configuration on x.ai and add a copy to Grok Bot. The copied material can include the Bot's identity, description, skills and routines, while excluding the original owner's computer, account logins and conversation history.
The Marketplace would put discovery around that existing sharing mechanism. Instead of receiving a link from a specific creator, users could browse third-party Bots inside Grok Bot and review their capabilities before installation.
The catalog is still being curated manually. In a reply to the thread, @blankspeaker said SpaceXAI staff currently add Bots and advised users to review everything a Bot does before placing it on a team. The post did not describe an open submission flow, payments for creators or a public review process.
SpaceXAI's current plugin settings documentation already directs users to a Marketplace for connectors and packaged skills. Plugins can authenticate with external services, and administrators can restrict their availability. For teams, SpaceXAI says Grok Bot inherits Cursor's existing plugin and Model Context Protocol policies, including server allowlists and controls over whether members may add their own servers.
SpaceXAI also maintains an official plugin marketplace repository for Grok Build. That catalog accepts first-party and third-party packages containing skills, agents, hooks, commands and MCP servers. Remote plugin sources must be pinned to a specific commit, a supply-chain control intended to prevent an upstream repository change from silently replacing installed code.
The installation screen carries real security weight
Grok Bot launched in early beta on August 11th as a collection of persistent agents that work on a cloud computer. SpaceXAI describes each Bot as a named teammate with its own job and conversation. The agents can browse websites, use connected services, run terminal commands and retain working context across sessions.
All of a user's Bots share the same cloud computer, including its files, browser sessions and command-line credentials. SpaceXAI's security guidance explicitly warns users against treating separate Bots as security boundaries and recommends keeping actions such as sending messages, publishing, purchasing, deleting data and changing production systems behind approval.
A third-party Bot therefore brings a wider trust surface than a prompt template. Its instructions can shape how it interprets work, its routines can repeat actions while the user is away, and its integrations can provide access to external systems. The marketplace preview's review screen is central to the product rather than decorative metadata.
SpaceXAI has expanded access quickly since the August 11th beta release. Cursor's current plans documentation says Grok Bot is included with every paid individual Cursor plan and Cursor Teams, while individual SuperGrok subscribers can link eligible subscriptions to a Cursor account for usage.
A built-in Bot marketplace gives SpaceXAI a way to make that broader distribution useful without requiring each new user to design an agent roster alone. It also gives agent builders a direct route into persistent workspaces where bots can use authenticated tools and collaborate with other bots. The eventual submission, review and permission model will determine whether that becomes a durable developer channel or a tightly managed gallery of approved configurations.