English | 简体中文
Help multiple Codex chats understand each other's work while coding together.
Several chats working on one project may edit the same file, build the same feature twice, or change an interface another chat is using. AgenticGit records their work, flags situations worth checking, and, with your permission, asks the relevant chats to inspect them and collects their replies.
Git saves code versions, compares changes and combines the results. AgenticGit helps with assignments and communication during development. Together, they connect parallel work with a reviewed delivery.
Each Codex chat is a colleague or lab member working on an assigned task. AgenticGit acts as a coordinator who watches for overlapping work and changes that need discussion. Git is the team's code archive, keeping versions and helping combine everyone's changes.
flowchart LR
Team["Team members<br/>Multiple Codex chats"]
AG["AgenticGit · Coordinator<br/>Understand assignments, alert members"]
G["Git · Code archive<br/>Save versions, combine changes"]
Result["Team reviews and delivers"]
Team -->|"Work in progress"| AG
AG -->|"Alerts and feedback"| Team
Team -->|"Completed code changes"| G
G --> Result
| Team situation | What Git does | What AgenticGit does | How they work together |
|---|---|---|---|
| Find out what everyone is working on | Shows recorded code changes and commits | Summarizes registered tasks and work areas | Check assignments during development and code results at delivery |
| Two members edit the same file | Compares changes; merging versions may reveal text conflicts | Asks affected chats to check their scope and agree on an order | Coordinate early, then inspect and merge actual changes |
| Two members build the same feature with different names | Saves both implementations; does not judge duplicate effort | Flags possible duplication using task descriptions and supported code structure checks | Members decide what to reuse, then save the result with Git |
| One member changes an interface another still uses | Records the interface code change | Uses registered dependencies to alert affected chats | Adapt the related code, test it and commit |
| Explain why something changed and who checked it | Shows code differences and commit messages | Keeps work records, inspection requests and replies | Connect code changes with the collaboration behind them |
| Undo changes or combine the results | Supports version recovery, branches and merges | Provides coordination information and advice | The team decides, then uses Git for version operations |
For example, two members implement order totals in different files using different function names. Git can save both implementations. When AgenticGit detects similar work, it asks the members whether both are needed. The team decides what to keep or share, tests it and commits the result.
AgenticGit supplies evidence to check; members still decide. Git's version history and merge tools remain the foundation for delivery.
Four parts form the system: coding chats supply work information, AgenticGit records and checks it, a coordinator handles alerts and replies, and Git saves the code results.
flowchart TB
subgraph Work["1 · Coding chats"]
Chats["Multiple Codex chats<br/>Take tasks, edit code"]
end
subgraph Core["2 · AgenticGit background service"]
Record["Work records<br/>Who is doing what, and where"]
Check["Collaboration checks<br/>Shared files, duplicate work, affected tasks"]
end
subgraph Talk["3 · Coordination and feedback"]
Coord["Coordinator chat<br/>Send alerts, collect replies"]
View["Summary and board<br/>Show progress to the user"]
end
subgraph Version["4 · Code version management"]
Git["Git<br/>Save versions, compare and merge changes"]
end
Chats -->|"Work information"| Record
Record --> Check
Check -->|"Advice"| Chats
Check -->|"Needs a member's inspection"| Coord
Coord -->|"Alert"| Chats
Chats -->|"Reply after checking"| Coord
Coord --> View
Chats -->|"Commit code results"| Git
Git -->|"Versions and changes"| View
The background service identifies situations worth checking. After you authorize it, the coordinator contacts other chats and collects their actual replies. See the architecture reference for implementation details.
flowchart TB
subgraph Start["1 · Get started"]
Install["Install and enable the plugin"]
Enable["Read the explanation<br/>Choose whether to enable coordination"]
end
subgraph Develop["2 · Develop together"]
Work["Chats describe their tasks and write code"]
Check["AgenticGit checks ongoing collaboration"]
Feedback["Alert relevant chats when needed<br/>Members inspect, reply and adjust"]
end
subgraph Finish["3 · Review and deliver"]
Review["Read the summary, test and review code"]
Git["Save or merge results with Git"]
end
Install --> Enable
Enable -->|"Agree and prepare a coordinator"| Work
Enable -->|"Leave coordination off"| Normal["Continue the usual workflow"]
Work --> Check
Check -->|"Something needs checking"| Feedback
Feedback --> Work
Check -->|"Development complete"| Review --> Git
The first offer is per workspace, usually at a new session or the start of work. Opening a file alone does not guarantee a popup. Automatic cross-chat alerts require your explicit consent and can be disabled at any time.
Requires Node 22.19+ and Codex with local plugin support. Install from source:
git clone https://github.com/yiweiqin/agentgit.git
cd agentgit
npm ci
node packages/cli/bin/agentgit.mjs install
codex plugin add agentgit@personal
node packages/cli/bin/agentgit.mjs install --enableReplace personal with the marketplace name printed by the installer. Enable the plugin and trust its hooks in Codex, start a new chat, and follow the explanation to choose whether to enable automatic coordination. Keep the source checkout: the plugin uses it at runtime.
Collaboration checks work in ordinary folders too; version history and merges require Git. See the usage guide for installation checks and troubleshooting.
Two-chat walkthroughs have verified alerts and replies for shared-file work and JS/TS implementations with different names but identical normalized structure. Similar-work detection has language and syntax limits. Alerts need inspection and do not replace testing or code review.
- Installation, automatic alerts, commands and limitations
- System architecture and implementation
- How changes affect other chats
- Experiments and validation
- Documentation index / 文档目录
MIT license.
A standalone Python implementation and reproduction guide are available in prototypes/structured-delta. See scope and evidence; this prototype is separate from the product runtime, and generated experimental artifacts stay local.