a2aproject/a2a-dotnet

C#/.NET SDK for A2A Protocol

Hosted by Linux Foundation

View on GitHub ↗Jump to charts ↓Open shareable report →

a2aproject/a2a-dotnet has 250+ stars and 60+ forks on GitHub, is written in C#, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on October 15th, 2026
Created on May 29th, 2025
Open Issues & Pull Requests: 32 (+0)
GitHub issues: Enabled
Number of forks: 68
Total Stargazers: 267 (+0)
Total Subscribers: 5 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 24.7 hours
Mean response time: 28.5 days
90th percentile: 59.1 days
Tracked items: 131

Maintainer activity

3 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 12% of issues opened in the past year have never received a reply. 64% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. 80% of issues opened in the past year have been closed, leaving a working backlog. Three people close 64% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 22
New in 7 days: 8
Closed in 7 days: 8
Avg open age: 232 days
Stale 30+ days: 11
Stale 90+ days: 8

Recent activity

Opened in 7 days: 8
Closed in 7 days: 8
Comments in 7 days: 4
Events in 7 days: 23

Top labels

  • bug (12)
  • enhancement (7)
  • v0.1.0-preview.2 (7)
  • v1.0.0 (6)
  • good first issue (4)
  • .NET (3)
  • blocked (3)
  • v0.2.5 (3)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

A2A .NET SDK is a C# library that implements the Agent2Agent (A2A) Protocol for building agentic applications as A2A-compatible servers.

The library addresses the need for standardized communication between AI agents and applications. It provides both high-level abstractions and fine-grained control over agent interactions, supporting three protocol bindings: JSON-RPC, HTTP+JSON REST with Server-Sent Events streaming, and gRPC with server-streaming. The core abstractions—IA2AClient for client operations and IA2ARequestHandler for server-side request handling—are shared across all bindings, allowing developers to write binding-agnostic code. Key capabilities include agent capability discovery through agent cards, direct stateless message-based communication, persistent long-running task management, and real-time streaming support.

Developers should adopt this tool if they are building .NET applications that need to communicate with A2A-compatible agents or expose agent functionality through standard A2A endpoints. It suits projects targeting .NET 8 and later that require interoperability with the broader A2A ecosystem. The library includes built-in ASP.NET Core integration for hosting agents in web applications, making it particularly valuable for teams already invested in the .NET platform. The README indicates that a backward-compatible v0.3 package is available for gradual migration, though upgrading to v1.0 involves breaking changes documented in a migration guide. The compatibility layer includes specific guidance on blocking behavior differences when v0.3 clients communicate with v1 servers.

The project maintains active development with regular updates to align with the A2A v1.0 specification. The codebase includes comprehensive documentation covering protocol bindings, migration paths, and integration patterns. The library is distributed across modular NuGet packages, allowing consumers to depend only on required components—the core library, ASP.NET Core extensions, or gRPC bindings—rather than forcing unnecessary dependencies.