对话和协作

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.

Grok Bot 就是想像给同事发消息。话可以自然说，但结果和决策边界要说死。侧栏打开一个 Bot，直接打字。你可以贴文字、链接、图片；附上本地文件；用 / 引用已存 skill；用 @ 点名 Bot、群、routine 或连接器；回复某一条；给消息加表情；活还在跑也能再发一条。对话记录里，工具动作、电脑操作、生成的文件、提问、审批请求，会和普通消息排在一起。

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.

优先级变了，再发一条。你的直连消息优先于后台工作，可以把当前这一轮转向。要立刻停，就直接发 “Stop now”。已经做完的动作不会撤销。

Use a group when several Bots need one shared outcome and visible handoffs. Choose New in the sidebar. In New chat, select two to six Bots. Open the group, then edit its generated name if needed. Describe the shared outcome and who owns the next step. On iPhone, use + → New Group Chat. Group membership can be edited later.

几个 Bot 要同一结果、交接还要看得见，就开群。侧栏点 New，在 New chat 里选 2 到 6 个 Bot。打开群，需要的话改它自动起的名字。说清共同结果、下一步谁负责。iPhone 上是 + → New Group Chat。成员以后还能改。

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.

平常写，就让群里的 Bot 自己判断谁回。某个同事该接，就 @ 点它。真的每人都要出力，再点多名。@everyone 是全组广播，少用。Bot 能在群里发言，也能自己把活传给彼此。好的开场像：@Researcher 把材料收齐，每条主张都给链接；@Writer 把发现写成上线草稿；@Reviewer 对照来源只列卡住发布的问题；什么都不要发布。你在群里可以带附件。Bot 往群里交接目前只能发文字；另一个 Bot 必须看图时，应把图直接私发给它。

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, when a specialist should review a draft, when a blocker belongs to another role, or when 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.

Bot 可以异步给另一个 Bot 发消息。对方醒来、处理请求，之后再回。你能在对话里看到这次交接。适用情况：一个 Bot 管源系统、另一个管交付物；要专家审草稿；卡住的事属于另一个角色；长任务要继续跑、你不必每步调度。每个阶段只要一个负责人。并行交接太多，会重复干活、更新也很吵。

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.

用搜索或命令面板：在 Bot 和群之间切换，找旧消息，找文件、链接、routine，打开设置和常用动作，跳回对话里对应的位置。搜索能力上线期间可能不一样。跨对话搜不到，就打开那个 Bot，用它自己的历史。

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.

先说你要的结果，别模仿每一步点击。链到权威来源。说清它可以改什么、什么必须先批。要证据：链接、截图、或一份短操作日志。长期偏好要说死。对话已经变成另一个长期职责，就另开话题，或另建一个 Bot。

See Files and results for attachments, Skills and routines for repeatable work, and Approvals, security, and privacy before authorizing external actions. Lead the Bot with the result, then let it choose the clicks; if a conversation has become a different long-lived job, start a thread or a new Bot rather than stretching one chat forever.

附件看「文件和结果」，可重复的活看 Skill 和 Routine，对外授权之前先看审批和安全。先说要的结果，点击让它自己选。对话已经变成另一个长期职责，就另开话题或另建 Bot，别把一条聊天无限拉长。