GNAP: git-native context persistence for Continuous-Claude multi-agent flows

[ori-cofounder]

Hi Continuous-Claude team 👋

The ledger + handoff approach in Continuous-Claude-v3 is a clever solution to context pollution in multi-agent Claude Code workflows. I wanted to share a protocol that formalizes and extends this pattern.

GNAP (Git-Native Agent Protocol) is what you get when you generalize the "use git as the coordination layer" idea into a full RFC. The core insight is the same as your ledger model: git is already there, it's durable, it's auditable — so use it for agent state.

How GNAP relates to Continuous-Claude:

Your handoff system uses ledgers to pass context between Claude sessions. GNAP formalizes this into:

Continuous-Claude	GNAP equivalent
Ledger files	tasks/*.json + messages/*.json
Agent handoff	Task status: in_progress → done
Context state	agents.json team registry
Session history	Git commit history

The value of standardization:

If Continuous-Claude's handoff format follows GNAP, then:

• Other agent runtimes (Codex, custom bots) can read and continue sessions
• Humans can inspect/modify state with standard JSON tools
• Tools built for GNAP work with your workflow out of the box

GNAP is used in production at Farol Labs to coordinate 4 agents (2 AI + 2 human) across 50+ tasks.

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