Share one Grok Bot roster across teammates

Co-founders often want one shared Bot roster (same bots, memory, files) with separate private chats per person. Cursor staff (Colin) stated the product today: share = copy. Deeper team collaboration is in progress with no ETA. Templates for sharing have shipped; live shared memory across accounts has not.

What share does today

1. Use the existing Share a Bot / copy flow to give a teammate a Bot.
2. That teammate gets a copy. Edits, memory, and files on their copy can drift from yours.
3. Your chats stay on your account; theirs stay on theirs. There is no documented “same roster, separate DMs” mode yet.

See also Share a Grok Bot for the copy mechanics, and Isolate parallel Grok Bot projects when one person needs separate workstreams on one account.

Practical team patterns until shared roster ships

1. Templates: start teammates from the shared template / copy so the system prompt and starter skills match, then expect drift.
2. One owner account: put the production roster on a single Cursor account that the team signs into only when necessary — and accept that chats and approvals are that account’s. Prefer this only with clear approval rules.
3. Docs outside the Bot: keep the durable playbook in Notion, Drive, or git so copies can re-read the same source of truth after they diverge.
4. Connectors: each teammate reconnects plugins on their own account; shared-computer sessions on one account give no multi-user security boundary (approvals, security, and privacy).

What to ask staff for

On the forum thread, describe: same bots + memory + files, separate private chats, no drift. Staff already marked deeper collaboration as in progress. Vote or bump with your team size and whether copy/templates are enough for now.

Pitfalls

• Treating a shared link as live sync — copies diverge as soon as either side edits memory or files.
• Putting multiple humans on one Cursor login without an approval policy — that is account sharing, not multiplayer.
• Distinct from Microsoft Teams “message humans as the Bot” (still a feature request without a staff product answer).