agentclientprotocol/agent-client-protocol

A protocol for connecting any editor to any agent

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 39 minutes ago
Added to GitGenius on September 16th, 2026
Created on June 23rd, 2025
Open Issues & Pull Requests: 46 (+0)
GitHub issues: Enabled
Number of forks: 389
Total Stargazers: 4,263 (+0)
Total Subscribers: 24 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.8 hours
Mean response time: 3.7 days
90th percentile: 13.3 days
Tracked items: 36

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 16% of issues opened in the past year have been closed. Three people close 94% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 9
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 92 days
Stale 30+ days: 7
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Detailed Description

Agent Client Protocol is a protocol specification for connecting editors to AI agents.

The protocol solves the problem of fragmented integrations between text editors and AI agent tools. Rather than requiring each editor to build custom support for each agent and vice versa, the protocol establishes a standardized interface that allows any editor to communicate with any agent through a common language. This approach decouples editor implementations from agent implementations, enabling both to evolve independently while maintaining compatibility.

Developers should adopt this protocol when building either editor integrations or agent tools and want to avoid lock-in to specific platforms. It suits projects where interoperability across the editor and agent ecosystem is a priority. Teams building agents benefit from reaching users across multiple editors without custom work per editor. Editor developers gain the ability to support multiple agents through a single integration path. The protocol is particularly valuable for organizations that use heterogeneous tooling and want standardized agent connectivity rather than maintaining separate integrations.

The project shows active engagement with its specification and reference implementation. Development includes regular updates to the protocol definition and supporting code. The project maintains documentation and examples to guide implementers. Community contributions are being integrated into the specification as the protocol matures. The codebase reflects ongoing refinement of the interface design based on practical implementation experience.