GNAP: git-native task board as a persistence layer for BabyAGI's self-building agents
Proposal: GNAP as the coordination substrate for BabyAGI's function-based agents
BabyAGI's newest direction is fascinating — a self-building autonomous agent using functionz for storing, managing, and executing functions from a database. The graph-based function dependency tracking is particularly interesting for agent coordination.
GNAP (Git-Native Agent Protocol) could complement this vision. Rather than a database, GNAP uses git as the persistent task store: board/todo/ → board/doing/ → board/done/. It's the simplest possible coordination layer — no infrastructure, just git commits.
Applied to BabyAGI's self-building model:
BabyAGI currently logs function executions to a database. GNAP could serve as the coordination layer between multiple BabyAGI instances working on shared goals:
board/todo/build-web-scraper-function.md ← BabyAGI instance 1 creates
board/doing/build-web-scraper-function.md ← BabyAGI instance 2 claims
board/done/build-web-scraper-function.md ← Function code committed + registered
The git history naturally documents which functions were built, by whom, and in what order — a kind of distributed function registry that could replace or complement the SQLite database approach.
This aligns with BabyAGI's spirit of finding the simplest thing that works — GNAP is just git, which every developer already has.
Source: yoheinakajima/babyagi