Kiro Rebuilt Its Harness as a Standalone ACP 1.0 Server Instead of a Per-Client Library
Kiro's August 3 engineering post describes replacing three diverging language-specific agent implementations with one standalone server process — explicitly 'not a library compiled into each client' — so the harness and its clients need not share a language or runtime. It serves Kiro IDE 1.0, Kiro CLI v3 (early access), Kiro on web (preview), and Kiro for iOS (preview) over Agent Client Protocol 1.0, extended with a custom WebSocket transport and a 'Kiro-ACP' namespace adding 20+ agent-callable and 15+ client-callable methods under `_kiro/`. Permissions use Cedar, a formally verified policy language, grouping tools by capability (fs_read, fs_write, shell). The out-of-process harness plus a formal policy language is a credible template if you're running one agent across CLI, editor, and mobile surfaces.
Source
↳ Follow the thread