Developer releases Carbon–Neon orchestrator plugin for Antigravity
A developer open-sourced carbon-neon-orchestrator, a zero-dependency local Antigravity plugin that uses Gemini 4 Carbon for architecture and code review while assigning implementation work to concurrent Neon workers. The author says its PreInvocation hook and native swarm tools provide model-specific orchestration, avoid repeated rule injection and nested delegation, and support safeguards for small edits, context transfer, failed fixes, and shared workspaces. The plugin runs locally through Python’s standard library, requires Antigravity’s built-in swarm support, and can be enabled from the client’s customization panel.
The release provides a concrete way to combine stronger model-led planning with faster parallel execution, while documenting implementation safeguards for multi-agent coding workflows.
最近主力在用 Google 的 Antigravity 2.0 写代码,恰逢 Gemini 4 系列更新了 Carbon 和 Neon,官方也在模型下拉框里塞了几个新的 Orchestrator 模式(Orchestrator (Carbon)、Orchestrator (Neon)、Orchestrator (Argon))。
重度用了两天之后,我发现了一个特别拧巴的痛点:官方预设只能“同系模型一锅端”,偏偏缺了我最想要的 Carbon -> Neon 组合。
- 全员开 Carbon:拆复杂架构、推导算法确实稳,但连全库搜文件、写样板代码、跑单测修 Lint 这种体力活也全开 Carbon,不仅单轮响应偏重,配额掉得也是真肉疼;
- 全员开 Neon:手速飞快,并发干活很爽,但一旦遇到跨模块耦合重的设计或者深水区 Bug,总控大脑的架构把控力还是差点意思。
最理想的状态其实就跟真实开发团队一样:让一个顶配的 Carbon 当 Tech Lead 动脑子拆架构、审代码,手底下带一群手脚麻利的 Neon 并发干体力活。
既然官方没给这个挡位,干脆自己动手写了个零外部依赖的本地插件 carbon-neon-orchestrator 把这块拼图补上了,顺手开源出来分享下实现思路和踩过的几个坑。
#carbon-neon-orchestrator#Antigravity#Gemini 4 Carbon#Gemini 4 Neon