GNAP: git-native task board for ChatDev 2.0's zero-code multi-agent orchestration

Proposal: GNAP as a coordination protocol for ChatDev's evolving agent topologies

ChatDev 2.0 (DevAll) is a compelling evolution — from a linear software company simulation to a zero-code multi-agent orchestration platform. Your MacNet work on directed acyclic graph topologies for 1000+ agents is especially interesting. As orchestration scales, the coordination layer becomes critical.

GNAP (Git-Native Agent Protocol) proposes git itself as the coordination substrate: board/todo/ → board/doing/ → board/done/. Tasks are files, transitions are commits. No message broker needed — any agent can participate via git.

Applied to ChatDev's zero-code agent system:

When a user configures a ChatDev 2.0 workflow (say, data visualization pipeline with a planner agent, coder agent, and renderer agent), GNAP could serve as the durable task handoff layer:

board/todo/viz-plan-dataset-47.md      ← Planner agent writes spec
board/doing/viz-plan-dataset-47.md     ← Coder agent claims
board/done/viz-plan-dataset-47.md      ← Code artifact committed

board/todo/render-output-dataset-47.md ← Renderer agent picks up

This is particularly compelling given ChatDev's MacNet research on DAG topologies — GNAP's git history naturally records the execution DAG of agent interactions, which could feed back into your orchestration RL work.

Also relevant to your NeurIPS 2025 paper on evolving orchestration — GNAP's audit trail would make it possible to study which agent sequences actually got committed vs planned.

Spec: https://github.com/farol-team/gnap

Start by reading the linked GNAP specification and the ChatDev 2.0 and MacNet material mentioned in the proposal. The issue names no ChatDev files, entry points, tests, or acceptance criteria, so the integration scope and definition of done would need to be established before implementation.