Duplicate a Grok Bot for a new scope

Duplicate a Bot when the same role should own a different region, client, or project. The copy keeps the profile, settings, enabled skills, routines, and avatar. It does not keep conversation history, learned memory, or attachments. Official guide: Work with Grok Bot → Organize your roster.

Use duplicate when the job is already working and you need another owner with the same playbook. Create a fresh Bot instead when the job, tools, or approval boundary are new.

When to duplicate

Duplicate works well for one account-health Bot per region, one expense Bot per entity, or one repro Bot per product line. The copied routines still fire on their schedules until you pause, edit, or delete them on the new Bot. Rename and rewrite the description before you assign real work so the copy does not act under the old scope.

Duplicate the Bot

1. Open the source Bot in the sidebar.
2. Open Bot actions and choose Duplicate.
3. Confirm a new Bot appears with the same name pattern, avatar, skills, and routines.
4. Open Bot actions → Edit Profile (or View conversation details → Agent settings) on the copy.
5. Rename the Bot, update the title, and rewrite the description for the new scope.
6. Review Routines on the copy. Pause or edit any schedule that should not run until the new scope is ready.
7. Send a first task that names the new sources, deliverable, and approval boundary.

What the copy keeps and drops

The copy keeps identity fields, notification preference, enabled skills, routines, and the avatar. It drops conversation history, learned memory, and attachments. The shared cloud computer is unchanged: browser sessions, /workspace files, and command-line credentials stay available to every Bot on your account, including the new copy.

Pitfalls

• Leaving the old name and description on the copy — the Bot will keep acting for the previous scope until you rewrite them.
• Expecting chat history or learned memory to transfer — they do not; restate durable facts in the description or ask the Bot to re-read current sources.
• Forgetting that copied routines can still fire — pause or edit them before the first real run if the new scope is not ready.
• Treating duplicate as a security boundary — the copy shares the same computer logins and files as every other Bot on your account.