This release adds Agent Client Protocol (ACP) support for integrating Kiro into ACP-compatible IDEs and clients, a Help Agent for instant CLI guidance, and a range of tool and configuration improvements.

Agent Client Protocol (ACP) Support

ACP-compatible editors like JetBrains IDEs and Zed can now use Kiro as a custom agent. Run kiro-cli acp to start Kiro as an ACP-compliant agent that communicates over stdin/stdout using JSON-RPC. Kiro supports standard ACP methods plus extensions for slash commands, MCP tools, and session management. Learn more ->

Help Agent

Get instant answers about Kiro CLI without leaving your conversation. The built-in Help Agent uses documentation to answer questions about commands, tools, settings, and configuration — and can even create config files in .kiro/ for you. Use /help to switch to the Help Agent, or /help How do I configure MCP? to ask directly. Learn more ->

Enterprise Web Tools Governance

Administrators can now disable web_search and web_fetch tools organization-wide. Users see a notification in /tools when web access is disabled by their organization. Learn more ->

Subagent Access Control

New availableAgents and trustedAgents settings give fine-grained control over which agents can be spawned as subagents. Both support glob patterns like test-*. Learn more ->

Exit Codes for CI/CD

Kiro CLI now returns structured exit codes for automation. Use --require-mcp-startup to exit with code 3 when MCP servers fail to start — ideal for CI/CD pipelines that depend on MCP tools. Learn more ->