XNews

Grok Bot Templates Feature Launch

Grok Bot Templates Feature Launch

Grok launched a Bot Templates sharing feature that packages a bot's configuration without exposing private data. When a user triggers “Share as template”, the bot decides what to include: it retains skills, selected memories, official plugins, and routines (default paused and marked untrusted), while stripping private keys, custom MCP/scripts, session history, and personal memories. The generated draft is unpublished and sanitized; the user can inspect details before publishing. Publishing is limited to “public” or “team only”. The recipient opens a link, reviews context and integrations, and adds the template as a new, separate bot—not merged with any existing bot. Official connectors (e.g., Pstack, GitHub, Cursor) are included but need re-confirmation; non-officiale dependencies (MCP, scripts) must be provided by the receiver. For complex templates relying on API keys or custom setups, the creator can ask the original bot to write installation instructions directly into the template. The recommendation is to evaluate templates like software deliverables—review details and integrations before installing—not as simple prompts.

Key insights

Templates sanitize bot configuration by design, excluding secrets and custom code

The share-as-template feature automatically strips sensitive data. The bot decides what to keep for utility: skills, selected memories, official plugins, routines (suspended by default) are included. Private keys, custom MCP/scripts, session history, and personal memories are excluded. This design ensures recipients get usable configurations without inheriting secrets or internal ties.

Publishing scope is intentionally narrow—public or team-only

Templates can only be published to the public or restricted to a team; no other visibility options exist. The example notes a bot tied to internal SpaceX code processes would be shared with team only, enforcing organizational access control. This simple two-tier model prevents unintended exposure of sensitive workflows.

Installed templates create a new standalone bot, not a merge

When a recipient installs a template, the result is a fresh bot with its own identity and icons, not an augmentation of an existing bot. Official plugins need to be re-installed/confirmed on the new account; non-officiale dependencies (MCP, scripts) must be supplied by the receiver. This isolation prevents cross-contamination of bot configurations.

Complex templates can embed setup instructions written by the original bot

For templates requiring API keys, MCP, or custom flows, installation is not fully automated. The creator can ask the source bot to analyze what a new user needs and write a configuration guide directly into the template. This makes advanced setups reproducible while leaving environment-specific steps to the recipient.

Templates should be reviewed as software artifacts, not as prompts

The guidance emphasizes reviewing template details and integrations before installation, treating them like external software that can act on the user’s behalf. This mental model shift reduces security risks and ensures the recipient understands exactly what the bot will do, especially for third-party templates.

Source posts