Message and collaborate

Grok Bot is designed to feel like messaging a teammate. Keep requests natural, but make the outcome and decision boundary explicit.

Open a Bot from the sidebar and type a message. You can:

• paste text, links, and images;
• attach local files;
• reference a saved skill with /;
• mention a Bot, group, routine, or connector with @;
• reply to a specific message;
• react to a message; and
• send another instruction while work is in progress.

The transcript shows tool activity, computer use, created files, questions, and approval requests alongside normal messages.

Send a new message when priorities change. A direct message from you takes priority over background work and can redirect the current turn.

Send a direct “Stop now” message when work should end immediately. This does not undo actions the Bot already completed.

Use a group when several Bots need one shared outcome and visible handoffs.

1. Choose New in the sidebar.
2. In New chat, select two to six Bots.
3. Open the group, then edit its generated name if needed.
4. Describe the shared outcome and who owns the next step.

On iPhone, use + → New Group Chat. Group membership can be edited later.

• Write normally to let the participating Bots decide who should respond.
• Type @ and select a Bot when one teammate owns the request.
• Mention multiple Bots when the request genuinely needs each of them.
• Use @everyone sparingly for a group-wide update.

Bots can post into the group and pass work among themselves. A useful kickoff looks like:

@Researcher gather the source material and link every claim. @Writer turn the findings into a launch draft. @Reviewer check the draft against the sources and list only blocking issues. Do not publish anything.

Your messages in a group can include attachments. Bot-to-group handoff messages are currently text-only, so a Bot should send an image directly to another Bot when that teammate must inspect it.

A Bot can send an asynchronous message to another Bot. The receiving Bot wakes, handles the request, and can reply later. You can see the handoff in the conversation.

This is useful when:

• one Bot owns a source system and another owns the deliverable;
• a specialist should review a draft;
• a blocker belongs to another role; or
• a long-running job should continue without you coordinating every step.

Ask for a single owner at each stage. Too many parallel handoffs can create duplicate work and noisy updates.

Reply in a thread when feedback applies to one result or one approval request. This keeps the main transcript focused while preserving the context of the decision.

Use reactions for lightweight acknowledgement. Use a written reply when the Bot needs a changed instruction; a reaction alone should not carry a safety-critical decision.

Use the search or command palette to:

• switch between Bots and groups;
• find prior messages;
• find files, links, and routines;
• open settings and common actions; and
• jump back to the matching place in a conversation.

Search availability can vary during rollout. If cross-conversation results are not available, open the relevant Bot and use its conversation history.

• Lead with the result you need, not a detailed imitation of every click.
• Link the source of truth.
• State what the Bot may change and what requires approval.
• Ask for evidence—links, screenshots, or a short action log.
• Correct lasting preferences explicitly.
• Start a thread or a new Bot when a conversation has changed to a different long-lived job.

See Files and results for attachments, Skills and routines for repeatable work, and Approvals, security, and privacy before authorizing external actions.