Requirements get lost
需求容易散掉
Product decisions often stay in chat while developers work from incomplete context. Gitdex turns confirmed requirements into tracked GitHub issues.
产品决策经常停留在聊天里，开发却只能拿到不完整上下文。Gitdex 会把确认后的需求变成可跟踪的 GitHub issue。
GitHub Issue/PR based development agent
基于 GitHub Issue/PR 的项目开发智能体
Gitdex
Gitdex helps you turn a product idea into GitHub issues, assign Codex agents to implement and validate PRs, and keep project delivery visible from requirement to merge.
Gitdex 帮你把产品想法转成 GitHub issue，调度 Codex agent 实现和验证 PR，并让项目从需求到合并的每一步都可追踪。
What it solves
解决什么问题
AI coding needs project control, not just chat
AI 写代码需要项目控制，而不只是聊天
When multiple agents write code, the hard part is no longer a single patch. It is keeping requirements, issues, PRs, QA results, rebases, reviews, and merges aligned.
当多个 agent 参与写代码时，难点不再只是生成一个 patch，而是让需求、issue、PR、QA 结果、rebase、review 和 merge 始终对齐。
Agent work is hard to audit
Agent 工作难审计
Gitdex records who ran Dev, QA, Review, and Merge, what logs were produced, and which issue/PR the work belongs to.
Gitdex 记录 Dev、QA、Review、Merge 谁在跑、产出了什么日志，以及这些工作对应哪个 issue/PR。
PR state drifts from reality
PR 状态容易失真
Issue stage labels drive the workflow, so the UI, GitHub, and agents share one visible state for what should happen next.
工作流由 issue 阶段标签驱动，因此 UI、GitHub 和 agent 对下一步该做什么有同一个可见状态。
GitHub-native delivery loop
GitHub 原生交付闭环
From idea to issue, from PR to done
从想法到 issue，从 PR 到完成
Gitdex treats GitHub issues and pull requests as the delivery backbone. Agents do the judgment work; Gitdex keeps the state machine, history, and controls consistent.
Gitdex 以 GitHub issue 和 pull request 作为交付主线。Agent 负责判断和执行，Gitdex 负责状态机、历史记录和控制入口保持一致。
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。
Why it helps
为什么有用
A development agent that respects your repository workflow
尊重仓库工作流的项目开发智能体
Issue-first tracking
以 issue 为主体
Every feature request, bug fix, QA failure, review decision, and merge result is anchored to a GitHub issue.
每个需求、修复、QA 失败、review 决策和 merge 结果都绑定到 GitHub issue。
Role-specific agents
按角色分工
Agents are split by responsibility, so development, QA, review, merge, and operations do not blur into one opaque session.
Agent 按职责拆分，开发、QA、review、merge 和运维不会混成一个不可追踪的会话。
Live execution output
实时执行输出
Users can see which agent is working on which issue, how long it has run, and what it produced.
用户可以看到哪个 agent 正在处理哪个 issue、运行了多久、最终产出了什么。
Auto-run orchestration
自动推进
Auto Run keeps all runnable issues moving while respecting dependencies, blockers, and stage-specific controls.
Auto Run 会在尊重依赖、阻塞和阶段控制的前提下，持续推进所有可运行 issue。
Local-first runtime
本地优先
Gitdex runs on your machine with local data, local worktrees, your GitHub CLI, and your Codex login.
Gitdex 运行在你的机器上，使用本地数据、本地 worktree、本地 GitHub CLI 和 Codex 登录状态。
Service-ready install
可安装为服务
Install as a CLI, run in development mode, or register a user-level launchd or systemd service.
可以作为 CLI 使用，也可以运行开发模式，或注册为用户级 launchd/systemd 服务。
Stable release
稳定版本
Install Gitdex v0.2.0
安装 Gitdex v0.2.0
The installer uses the stable v0.2.0 tag, installs dependencies, builds the app, and links the gitdex command into ~/.local/bin.
安装脚本使用稳定的 v0.2.0 tag，安装依赖、构建应用，并把 gitdex 命令链接到 ~/.local/bin。