What a Marketplace Bot copy carries

Know what lands on your account when you add a Marketplace or other public Grok Bot template, so you stop expecting the creator’s computer, secrets, or chat history to travel with the recipe. Marketplace listings at x.ai/bot/marketplace are published Bots you install through the same template add path described in Create and manage Bots and Templates for Grok Bot.

What you need

A Marketplace or x.ai/bot/… preview you are about to add (or already added), plus the Grok Bot app so you can open the copy’s live profile after install. Neighboring jobs include Add a Bot from the Grok Bot Marketplace for the click path, Vet a Marketplace Bot before adding for the pre-install checklist, and Share a Grok Bot for the creator-side publish steps. More Grok Bot jobs live on the Grok Bot hub.

What the copy includes

Official Share a Bot docs say a public preview exposes the Bot’s shared configuration: identity, description, skills, and routines. Matt Palmer’s staff guide adds that a template packages instructions, relevant memories and skills, and specific first-party plugins — a blueprint the recipient’s Bot then runs as its own instance. After Add Bot, you get a distinct new Bot on your roster with that packaged setup attached.

What the copy leaves behind

The same docs state that adding a shared Bot creates a copy and does not give the recipient the creator’s computer, logins, or conversation history. Approvals, security, and privacy repeats that a public share link is a configuration copy, not a security boundary around the creator’s sessions. The templates guide says personal or internal memories stay out by default, secrets are not shared, and non-standard plugins such as custom MCP servers or custom scripts are not included — you reconnect first-party plugins and rebuild any custom tooling on your own computer. Routines may appear as triggers in the template, but they run under your account once you enable them.

After the copy exists

Reconnect plugins that need your OAuth or keys. Put durable approval rules in the Bot description and Auto-review for sending, publishing, deleting, purchasing, or production changes. Correct memories that do not match your company. Prefer Team Bots when the whole team should talk to one maintained Bot instead of each person owning a diverging copy — see Set up a Team Bot in Grok Bot and Use a published Team Bot.

Pitfalls

Assuming Marketplace install includes the creator’s API keys or browser logins leaves the Bot stuck until you supply your own credentials. Expecting edits on the creator’s Bot to sync into your copy fails once the install finishes — copies diverge. Skipping third-party bot terms at add time still binds the install; read them before you confirm.