Multiple Bots, projects and handoffs#
Start with one Bot. Add another when it has a distinct ongoing role. For example:
| Role | Responsibility | Handoff |
|---|---|---|
| Researcher | Collect evidence | Links, notes and uncertainty |
| Writer | Draft from the material | A draft with identifiable factual claims |
| Reviewer | Compare the draft with sources | Specific corrections and open questions |
On desktop, create a group through New by selecting two to six Bots. For approvals and sign-in, also check the individual Bot’s conversation; the group does not show every such step. Collaboration details.
Prepare one briefing on [topic] together. The researcher supplies direct sources; the writer prepares the draft; the reviewer checks each factual claim against its source. The writer applies the review and delivers one final version and unresolved questions. At every handoff, identify the current files. Nobody publishes anything.
Three agreeing answers do not establish correctness. The reviewer should open the original source. Separate roles, names and conversations also do not create separate access boundaries on the shared computer.
Three different collaboration models: a group connects your Bots; a template gives another user a copy of the configuration; a Team Bot provides a shared, managed configuration, with members holding their own conversations. Check what access and material will become available before sharing.
Grok Bot, @bot and @grok on X: the distinction for Slovakia#
Grok Bot is the app and Bot system. @bot on X forwards a request to your Bot; you follow the work in its conversation. @grok is a different account and interaction on X. The names are not interchangeable. X’s explanation.
For a Slovak account, do not make tagging @bot under a post your first step. If you have access to the Grok Bot app, paste the link and assignment there directly. This is a separate route; it does not bypass the regional rule for tagging on X.
The X plugin provides additional tools for X content. Connecting it does not itself establish eligibility for @bot tagging. Review the requested permissions and terms in your particular account before connecting it.