Grok Bot 编排 + Mac 上 Codex 执行 + GitHub Issue 记账:一套多 Agent 团队 Harness 的完整搭建
Grok Bot orchestrates, Codex on a Mac executes, GitHub issues keep score: a full multi-agent team harness, from architecture to setup
X, @zhu185178, 2026-11-10
编程与仓库 生活助理 多 Bot 协作 上手教程 全文核对建议先读
https://x.com/zhu185178/status/2120052513496039702
场景
作者剪视频、写文章、做自用工具,同时开 3–5 个 Codex 会话后自己成了瓶颈:开会话、搬上下文、交代下一步都靠人
The author edits video, writes and builds personal tools; past 3-5 concurrent Codex sessions he became the bottleneck, opening sessions, carrying context and explaining the next step by hand
他们怎么做
四层:交互层(我 + Chief of Staff);编排层(Grok Bot 里的 Chief of Staff、各队 Team Lead、Worker、Reviewer、Publisher);执行层(Mac 上 Codex,经「Execution on Local Computer」以 headless 启动);状态层(GitHub Issue 作 ticket + 本地 Git)。流程:先更新 ticket 再用 Handoff 叫醒下一位;每个 Worker 一个 Webhook Routine,启动命令在 Codex 退出时回调(带 ticket 号与退出码),不轮询;一 ticket 一会话一目录,返工用 codex exec resume;审核开新的只读会话;Mac 最多并行 2 个 Codex;只保留三个定时:7:30 Team Lead 汇报、8:00 Chief 简报、每 2 小时心跳检查;临时讨论才开群聊。上下文分四层:角色(Bot 记忆)、流程(Skill)、项目(AGENTS.md)、任务(ticket)。九步落地:建独立 Mac 用户 agent、装 Codex、配 GitHub(hq 仓库、Issue 模板、状态标签、分支保护)、开本地执行并对个人用户设 Never、建 Chief of Staff 设为 Primary、先建一个小队、配回调、跑通第一张 ticket、再加定时并扩队;上线前自测五项:长任务、回调、用户隔离、重连、审批卡
Four layers: interaction (me + Chief of Staff); orchestration in Grok Bot (Chief of Staff, per-team Team Lead, Workers, Reviewer, Publisher); execution (Codex on a Mac, launched headless via Execution on Local Computer); state (GitHub issues as tickets plus local Git). Update the ticket first, then wake the next bot with a Handoff; each Worker has a webhook routine and the launch command calls back with ticket number and exit code when Codex exits, so nothing polls; one ticket, one session, one directory, with codex exec resume for revisions; reviews run in a fresh read-only session; at most two concurrent Codex runs; only three schedules (7:30 team reports, 8:00 Chief briefing, 2-hourly heartbeat); group chats only for temporary discussion. Context in four layers: role (bot memory), process (skills), project (AGENTS.md), task (ticket). Nine setup steps: a separate macOS user 'agent', install Codex, set up GitHub (hq repo, issue templates, status labels, branch protection), enable local execution only for that user, make the Chief of Staff the primary bot, build one small team, wire callbacks, run one ticket end to end, then add schedules and teams; five checks before leaving it unattended: long jobs, callbacks, user isolation, reconnection, approval cards
可以拿走的做法
ticket 先于 Handoff;Webhook 回调替代轮询;评审用只读新会话;上线前五项自测清单
Ticket before handoff; webhook callbacks instead of polling; reviews in a fresh read-only session; the five-point pre-flight checklist结果与限度
作者坦言 $100/月 方案通常用满周额度;文中界面示意图为 AI 生成、非真实截图;回调能否唤醒、长任务能否保持等五项需读者自测;Grok Bot 公测期功能变化快。
The author says his $100/month plan usually runs out its weekly allowance; the interface image is an AI mockup, not a screenshot; callbacks, long jobs and three other points must be verified by readers; features change quickly during the public beta.
来源
- 平台
- X
- 作者
- @zhu185178
- 日期
- 2026-11-10 15:14 Asia/Taipei (UTC+8)
- 日期依据
- 案例库画布,采集截止 2026-11-11 09:26 Asia/Taipei
- 时间窗
- 近7天 案例字段「近7天」相对采集截止 2026-11-11 09:26 Asia/Taipei,不是相对打开页面的今天
- 原分类
- 教程/多 Agent 编排
这条证据标签是什么意思
全文核对
来源已经读过(帖子、文章或字幕)。这只说明原文被读过,不代表本站复现了作者的结果。
标签不是评分。全文核对只表示来源被读过,不表示结果已被复现。