返回首页

对比阅读

对比阅读:Codex Goes Multi-Agent: Coding Tools Learn to Team Up 与 Codex 让多个 AI 同时改一份代码 — 编程工具开始学团队协作

AEN
CodexOpenAIAI Coding·

Codex Goes Multi-Agent: Coding Tools Learn to Team Up

What This Is

OpenAI's latest Codex CLI update added a toggle — letting multiple AI sessions edit code simultaneously in separate working copies. It looks like a minor change; in practice, it's coding tools moving from solo operations to multi-agent parallelism.

Codex CLI is OpenAI's command-line coding assistant. When you create a new task, it now asks: continue in the current project, or open an independent "working copy" (Git's worktree mechanism) to run in.

In plain terms: you have one AI modify module A while another AI modifies module B — each works independently, without overwriting the other's changes. This isolation doesn't rely on re-cloning the codebase; it rides on Git's built-in lightweight mechanism, so multiple AI sessions can run in parallel.

Industry View

Supporters see this as the inevitable trajectory of AI coding tools toward "multi-agent collaboration" — writing code, writing tests, fixing bugs, once queued sequentially, can now run in parallel to speed things up.

But some developers are skeptical. First, this feature is essentially a wrapper around Git worktree — not technically an AI innovation. Second, having multiple AIs modify the same codebase actually increases the risk of merge conflicts, and humans still end up doing the merging. Sharper critiques go further: more code AI writes doesn't translate to faster delivery — code review costs may climb rather than fall.

Impact on the Rest of Us

For individual careers: non-programmers can sit this one out for now, but be aware that "AI collaboration" is moving from solo to team play. Other tools will catch up.

For enterprise IT: R&D teams adopting such tools will need to redesign their code review processes. AI submission frequency and parallelism will rise significantly.

For consumer markets: future tools aimed at ordinary users (not just coding) will likely grow similar multi-task isolation designs — a directional signal for product form.

来源: juejin.cn
BZH
CodexOpenAIAI编程·

Codex 让多个 AI 同时改一份代码 — 编程工具开始学团队协作

这是什么

OpenAI 最近的 Codex CLI 更新里多了一个开关 — 让多个 AI 会话在不同工作副本里同时改代码。这看似不起眼,实质是编程工具从单兵作战走向多 Agent 并行的产品信号。

Codex CLI 是 OpenAI 的命令行编程助手。它新建任务时会问一句:接着当前项目继续,还是开一个独立「工作副本」(Git 的 worktree 机制) 跑。

简单说,你让一个 AI 改 A 模块,同时让另一个 AI 改 B 模块,两人各改各的、不会互相覆盖对方的修改。这种隔离不靠重新下载一遍代码,靠 Git 自带的轻量机制,所以多个 AI 会话可以并行干活。

行业怎么看

支持方认为这是 AI 编程工具走向「多 Agent 协作」的必然 — 写代码、写测试、修 bug,过去一个接一个串行排队,现在可以并行提速。

但有开发者持保留态度。一是这功能本质是 Git worktree 的封装,技术上不算 AI 创新;二是多个 AI 同时改同一份代码反而增加合并冲突 (merge conflict) 的风险,最后还是要人来合并。还有更尖锐的声音:AI 改得越多,不等于交付越快,代码审查环节的成本可能上升而不是下降。

对我们的小影响

对个人职场:非程序员暂时可以旁观,但要意识到「AI 协作」正从单兵走向团队,未来其他工具也会跟进。

对企业 IT:研发团队若引入这类工具,需重新设计代码审查流程,AI 提交频率和并行度会显著上升。

对消费市场:未来面向普通人的工具 (不只写代码) 大概率会长出类似的多任务隔离设计,是产品形态的一个方向信号。

来源: juejin.cn