GNAP: git-native task persistence for PraisonAI multi-agent workflows #1117
Description
Hi PraisonAI team 👋
PraisonAI's focus on low-code multi-agent systems that deliver to Telegram, Discord, and WhatsApp resonates with real-world deployment patterns. I wanted to share a coordination protocol that could add durability to PraisonAI's multi-agent pipelines.
GNAP (Git-Native Agent Protocol) turns any git repo into a zero-server coordination layer for AI agents. No Redis, no Celery, no extra services — just 4 JSON files and git push/pull.
PraisonAI-specific integration value:
PraisonAI already has handoff, guardrails, and memory — GNAP adds durable task queuing:
| Feature | PraisonAI today | With GNAP |
|---|---|---|
| Task state | In-memory | Durable git commits |
| Multi-machine agents | Not native | Shared git repo |
| Audit trail | Logs | Git history |
| Human override | Dashboard | Edit JSON + commit |
| 100+ LLM support | ✅ | ✅ (protocol agnostic) |
Concrete scenario:
A PraisonAI research pipeline running overnight: if the process crashes, tasks in GNAP survive — agents pick up where they left off on restart. For Telegram/Discord bots that run 24/7, this means no lost work.
The zero-infrastructure approach fits well with PraisonAI's goal of making multi-agent accessible — users who can set up PraisonAI can definitely set up a git repo.
Protocol spec: https://github.com/farol-team/gnap