DevOps / SRE / Platform · 06.08.2026, 18:09 UTC
Free agents: How AWS Kiro could untie agents from editors
| Schweregrad | info |
|---|---|
| Kategorie | DevOps / SRE / Platform |
| Quelle | The New Stack ↗ |
| Veröffentlicht | 06.08.2026 UTC |
Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.
Choosing a coding agent may soon no longer mean having to pick a new editor or terminal, too. That scenario came a step closer to reality this week, when AWS explained how Kiro replaced three separate agent harnesses with a single architecture built around the Agent Client Protocol. The move lets Kiro’s clients communicate with its agent through a shared protocol. It could eventually let developers choose their coding tools and AI agents independently.
The IDE relied on a TypeScript harness, the CLI used Rust, and the web experience depended on Python. These have now been consolidated into a single standalone agent harness that runs as a separate process alongside the workspace.
The engineering simplification is noteworthy, but the architectural decision is more consequential: AWS chose the Agent Client Protocol (ACP) as the interface between Kiro’s clients and Kiro’s own agent. ACP originated at Zed and is now jointly developed with JetBrains. By adopting an ecosystem protocol even for its first-party components, AWS is treating the client-agent boundary as a standardized interface rather than a proprietary implementation detail.
The protocol became the architectural boundary
Kiro’s engineers describe an evolution familiar to anyone who has built extensible software. Earlier attempts using shared libraries failed to maintain separation. Client applications gradually accumulated agent-specific logic by reaching into internal APIs, making the boundary increasingly porous.
Moving the agent into a standalone process solved that problem. The client now communicates …