Grok Bot 多机器人分工工作流拆解
作者按 xAI 文档画出 Grok Bot 的 chief/tester/docs/patcher/Jev 分工架构,人只需读摘要、点批准、合并。
holy sh*t. most people still use Grok Bot like a chat window one prompt, one answer, then an hour of babysitting xAI's own docs describe the opposite: one owner bot per job, a small crew under it, and you only show up at the end. i drew the whole thing out: > chief: holds the full repo in Grok 4.7's 500K context and owns the job start to finish > tester: reruns whatever failed and names the line that broke > docs: pulls the real SDK page before anyone writes a guess > patcher: ships the fix to a branch and kicks CI again > jev: the referee. every yes/no fork goes through it, typed answers back in milliseconds the rule i would steal first: docs isn't allowed to act alone. it asks Jev first that one line is why the crew doesn't loop all night your part of the whole run: -> read the summary -> click approve -> chief merges one click per job. that's the entire human workload honestly the hardest part for me was keeping my hands off the keyboard bookmark it, the setup i run is below ⭣
这条是引用着另一条写的:x.com/savipww/status/2102720919185617314