Free agents: How AWS Kiro could untie agents from editors
Choosing a coding agent may soon no longer mean having to pick a new editor or terminal, too. That scenario The post Free agents: How AWS Kiro could untie agents from editors appeared first on The New Stack .
AWS has introduced a new architecture for its coding assistant, Kiro, by consolidating three separate agent harnesses into a single standalone agent harness that runs alongside the workspace. This consolidation, made possible by the adoption of the Agent Client Protocol (ACP), allows developers to choose their coding tools and AI agents independently, eliminating the need to pick a new editor or terminal.
AWS chose ACP as the interface between Kiro's clients and its own agent, treating the client-agent boundary as a standardized interface rather than a proprietary implementation detail. By moving the agent into a standalone process, the client now communicates exclusively through ACP, while the execution environment becomes an implementation detail, allowing for greater flexibility and easier extensibility.
This architectural decision aligns with the trend of multiple vendors adopting similar approaches, such as Microsoft's Intelligent Terminal and GitHub Copilot CLI, which are designed to support multiple implementations through the standardized protocol.
Brief written by urgent.news from The New Stack's own syndicated text. Machine-written — it may contain errors, so check the original before relying on it.
