GNAP: cross-language agent coordination protocol for BotSharp agent networks

Hi BotSharp team 👋

BotSharp is one of the few serious multi-agent frameworks for .NET — which means it often needs to coordinate with agents in other runtimes (Python, Node, etc.). I wanted to share a protocol designed exactly for this cross-language coordination challenge.

GNAP (Git-Native Agent Protocol) is an open RFC for agent coordination using git as the message bus. Because the protocol is pure JSON files + git, it works identically regardless of what language or runtime the agent uses.

BotSharp-specific value:

BotSharp agents run in .NET but enterprise workflows often involve Python data science agents, Node.js integration agents, or human reviewers. GNAP provides a common coordination layer that works across all of them:

Integration idea for BotSharp:

BotSharp's IAgentService could have a GNAPBackend implementation that:

1. Writes task assignments to .gnap/tasks/ on agent dispatch
2. Polls via git pull in the heartbeat loop
3. Reads results from task JSON on completion
4. Provides full git-history audit trail

This would let BotSharp's orchestration layer coordinate .NET agents alongside Python, Node, or human agents without any API contracts or shared infrastructure beyond a git repo.

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

The proposal points to IAgentService, .gnap/tasks/, the heartbeat loop, task JSON, and the linked GNAP specification. Start by reviewing those integration points and the GNAP spec; done would require an agreed scope and acceptance criteria for a GNAPBackend, which the issue does not currently define.