Requirements get a place to land
需求有地方落下来
The PM agent helps turn rough intent into executable work. GitHub stores the resulting spec so later agents have a shared reference.
PM agent 帮助把粗略想法整理成可执行任务。GitHub 保存产出的规格，让后续 agent 有一个共同参考。
Open-source control room for coding agents
面向编码 Agent 的开源控制台
Gitdex
AI coding works better with rails than with a loose chat thread. Gitdex gives PM, Planner, Dev, QA, Review, and Merge agents a small control room, while GitHub stores the trail.
AI 写代码需要流程约束，而不是只靠一串聊天推进。Gitdex 给 PM、Planner、Dev、QA、Review、Merge agent 一个小型控制台，GitHub 负责保存痕迹。
Why this exists
为什么需要它
Chat alone is a shaky delivery system
只靠聊天，交付通常不可靠
AI agents can write patches quickly. Coordination is the harder part: who owns the next step, who validates, who reviews, who rebases, and what context survives.
AI agent 写 patch 很快。更难的是协作：谁负责下一步、谁验证、谁审核、谁 rebase、哪些上下文能留下来。
Agents leave a trail
Agent 留下痕迹
Dev, QA, Review, and Merge agents can produce logs, comments, labels, and PRs. GitHub acts as the ledger; agents do the work.
Dev、QA、Review、Merge agent 可以产生日志、评论、标签和 PR。GitHub 像账本，agent 负责行动。
State survives the session
状态不依赖会话
Agents may stop, retry, or hand off. Keeping state in GitHub labels, comments, issues, and PRs gives the next run a better chance to continue cleanly.
agent 可能停止、重试或交接。把状态放在 GitHub 标签、评论、issue 和 PR 中，可以让下一次运行更容易接上。
Agent-native execution loop
Agent 原生执行闭环
Help agents behave more like a team
让 Agent 更像一个团队
Gitdex gives each agent role a control point and keeps a durable record for the handoff. GitHub is the storage layer; the agent workflow is the core idea.
Gitdex 给每个 agent 角色一个控制点，并为交接留下持久记录。GitHub 是存储层，agent 工作流是核心想法。
Clarify
澄清需求
The PM agent helps shape a rough request into a clear requirement before any GitHub issue is created.
PM agent 先帮助用户把模糊想法澄清成明确需求，再进入 GitHub issue。
Plan issues
拆分 issue
The planner creates GitHub issues with owned paths, dependencies, acceptance criteria, and whether work can run in parallel.
Planner 创建 GitHub issue，明确 owned paths、依赖、验收标准，以及哪些工作可以并行。
Develop and QA
开发与 QA
Developer agents open PRs from isolated worktrees; QA agents validate test coverage and user-visible behavior before review.
Developer agent 在隔离 worktree 中创建 PR；QA agent 在 review 前验证测试覆盖和用户可见行为。
Review and merge
审核与合并
Reviewer and merge agents check PR readiness, route rebase or spec blockers, merge approved work, and close the issue.
Reviewer 和 Merge agent 检查 PR 就绪状态，处理 rebase 或规格阻塞，合并通过的工作并关闭 issue。
What you get
你得到什么
An agent system that tries to stay debuggable
一个尽量保持可调试的 Agent 系统
Agents first, GitHub persisted
Agent 优先，GitHub 持久化
The workflow is agent-driven, while specs, QA failures, reviews, and merge results are stored where engineers already look.
流程由 agent 驱动，同时把规格、QA 失败、审核和合并结果保存在工程师本来就会看的地方。
Agents with jobs
Agent 有明确岗位
Planner plans, Dev builds, QA checks, Review challenges the diff, Merge closes the loop when the issue is ready.
Planner 负责拆解，Dev 负责实现，QA 负责检查，Review 负责挑战 diff，Merge 在 issue 就绪后闭环。
Watch the machine run
看得见机器在跑
See which agent is working, which issue it owns, how long it has run, and the raw execution output.
看到哪个 agent 在跑、负责哪个 issue、跑了多久，以及原始执行输出。
Auto-run without magic
自动推进，但不装神秘
Gitdex can keep runnable work moving, pause on blockers, and expose controls instead of hiding automation behind a spinner.
Gitdex 可以推进可运行任务，遇到阻塞时暂停，并把控制点暴露出来，而不是只把自动化藏在转圈里。
Runs where your repo lives
运行在你的仓库旁边
Local data, local worktrees, your GitHub CLI, your Codex login. It is designed to run close to the repo, not behind an opaque queue.
本地数据、本地 worktree、你的 GitHub CLI、你的 Codex 登录。它设计为运行在仓库旁边，而不是藏在不透明队列后面。
Hackable by default
默认可折腾
Install the CLI, run dev mode, wire it as a service, fork the workflow, change the prompts, and make the control room fit your repo.
装 CLI、跑 dev mode、注册服务、fork 工作流、改 prompt，让这个控制台适配你的仓库。
Stable release
稳定版本
Install Gitdex v0.2.2
安装 Gitdex v0.2.2
One command pulls the stable v0.2.2 tag, installs dependencies, builds Gitdex, and links the gitdex CLI into ~/.local/bin.
一条命令拉取稳定的 v0.2.2 tag，安装依赖、构建 Gitdex，并把 gitdex CLI 链接到 ~/.local/bin。