Proposal: GNAP as an inter-agent coordination layer for ACI.dev-powered agent networks
ACI.dev hooks up 600+ tools into any agentic IDE or custom AI agent — unified MCP server, multi-tenant auth, granular permissions. When multiple ACI-powered agents need to coordinate work (one agent discovering tools, another executing them, a third synthesizing results), GNAP provides the coordination protocol.
GNAP (Git-Native Agent Protocol) uses a git repo as the task board: board/todo/ → board/doing/ → board/done/. Zero infrastructure — and since ACI agents already have access to tools including file systems and potentially git, GNAP participation is native.
Applied to ACI.dev multi-agent workflows:
An ACI-powered DevOps automation pipeline:
board/todo/provision-vercel-deployment.md ← Coordinator agent creates
board/doing/provision-vercel-deployment.md ← DevOps agent claims
# Uses ACI Vercel tool
board/done/provision-vercel-deployment.md ← Deployment URL committed
board/todo/configure-supabase-db.md ← DB agent picks up next
board/doing/configure-supabase-db.md # Uses ACI Supabase tool
board/done/configure-supabase-db.md ← DB connection string committed
board/todo/update-env-variables.md ← Links Vercel + Supabase
GNAP + ACI is a natural pairing for VibeOps — an agentic IDE can coordinate multiple ACI-powered agents via GNAP, each handling different platform tools, together assembling a complete deployment.
A GNAP tool in ACI.dev's 600+ tool catalog would make GNAP coordination accessible to every ACI user without any new infrastructure.
Spec: https://github.com/farol-team/gnap
Proposal: GNAP as an inter-agent coordination layer for ACI.dev-powered agent networks
ACI.dev hooks up 600+ tools into any agentic IDE or custom AI agent — unified MCP server, multi-tenant auth, granular permissions. When multiple ACI-powered agents need to coordinate work (one agent discovering tools, another executing them, a third synthesizing results), GNAP provides the coordination protocol.
GNAP (Git-Native Agent Protocol) uses a git repo as the task board:
board/todo/→board/doing/→board/done/. Zero infrastructure — and since ACI agents already have access to tools including file systems and potentially git, GNAP participation is native.Applied to ACI.dev multi-agent workflows:
An ACI-powered DevOps automation pipeline:
GNAP + ACI is a natural pairing for VibeOps — an agentic IDE can coordinate multiple ACI-powered agents via GNAP, each handling different platform tools, together assembling a complete deployment.
A GNAP tool in ACI.dev's 600+ tool catalog would make GNAP coordination accessible to every ACI user without any new infrastructure.
Spec: https://github.com/farol-team/gnap