Dev Mesh coordinates multiple Agents working in one Git workspace. Before writing, an Agent records its task and intended scope. When scopes overlap, Dev Mesh coordinates waiting, handoff, or isolated work. Commits run serially through managed Git operations.
State remains under .dev-mesh/ in the workspace and does not depend on a remote service.
Working model
inspect -> join Run -> create or reuse Claim -> edit -> validate
-> finish the Claim or commit through it -> leave RunWithout cross-Run overlap, the routine path uses one Run and one Claim. A later Claim can wait when scopes overlap; handoff, exclusivity, and short-lived branches are used only when needed.
Console
The Observer collects workspace state read-only into an external SQLite catalog and serves the Console over loopback. The Console shows current Runs, Claims, contention, handoffs, recovery state, and cross-project relations. Active contention presents the participating Runs, declared scopes, and requested paths directly. The collaboration flow opens when useful causal history is available; closed contention and raw events remain available on demand.
Boundaries
The host environment sends messages and wakes tasks. Dev Mesh can record communication and handoffs after they occur.
The current write contract is dev-mesh.coordination@20260823.1. Materialized workspace state is authoritative; Events, the Observer, and the Console are diagnostic. Dev Mesh ships through the Glenzli Marketplace as a Codex plugin with coordination and read-only observation skills.