Kiro

MCP client support spans local stdio and remote streamable HTTP servers with hot reloading configuration, a server directory, tool search and per agent server definitions, plus built in tools and deep AWS integration reaching IAM, S3, Lambda and Bedrock natively; Powers bundle MCP tools with skills for one click installation.

Sourcekiro.dev/docs/mcp, docs/tools and docs/powersread 2026-08-30

Spec driven development chains a multi step workflow: a prompt produces structured requirements, design and task documents which the developer reviews and approves, after which the agent implements across files against the task list; hooks chain further agentic work on repository events, custom agents can be defined per project, and Crew coordinates continuous multi agent operation.

Sourcekiro.dev/docs/specs, docs/hooks, docs/custom-agents and docs/crewread 2026-08-30

Crew Knowledge is a curated library of documents, folders and URLs the customer feeds the agent, ingested and searchable, and the CLI's knowledge management stores and searches context across chat sessions in knowledge bases. Tree-sitter and LSP code intelligence, steering files and specs add per task context.

Sourcekiro.dev/llms.txt (Crew Knowledge, CLI knowledge management) and docs/tools/code-intelligence; kiro.dev/docs/crew/features/knowledgeread 2026-09-29

Capability based permission rules allow or deny specific shell commands and file paths per agent, with organization level permission policies set in the enterprise console, trusted command configuration, .kiroignore file exclusions, and checkpoints allowing rewind of agent work. The spec workflow itself holds implementation until a person approves the requirements and design document.

Sourcekiro.dev/docs/permissions, docs/enterprise/governance/permissions and docs/specsread 2026-08-30

Enterprise governance covers identity provider connection with IAM Identity Center, permission policies, per organization MCP enable or disable with an allow list registry that fails closed if the governance API is unreachable, model governance, API key governance, web tool governance, monitoring and tracking, and managed updates. Privacy and security controls cover data protection, encryption, compliance validation, infrastructure security, IAM permissions, data perimeters and VPC endpoints via AWS PrivateLink.

Sourcekiro.dev/docs/enterprise/governance and docs/privacy-and-securityread 2026-08-30

Enterprise administrators get a monitor and track view of organization usage and activity, specs leave requirements, design and task documents as a durable record of intent, and checkpoints allow rewinding to an earlier point in a session. Kiro does not describe a per agent execution trace or an audit log that reconstructs tool calls and reasoning.

Sourcekiro.dev/docs/enterprise/monitor-and-track and docs/checkpointsread 2026-08-30

Kiro Web keeps a memory of what the agent learns from the task creator's feedback, shown in Settings where each memory can be deleted. Kiro Crew keeps six memory layers across sessions (preferences, projects, recent history with decay, semantic key value memory, episodic memory with vector search and time decay, and learned lessons). Specs and steering files hold standing instructions.

Sourcekiro.dev/docs/web/memory and docs/crew/features/memoryread 2026-09-29

Enterprise deployment covers supported AWS regions, VPC endpoints via AWS PrivateLink so traffic need not traverse the public internet, firewall, proxy and data perimeter configuration, deployment options and IAM integration. The client itself runs locally on desktop, CLI, web and mobile surfaces.

Sourcekiro.dev/docs/privacy-and-security/vpc-endpoints, docs/enterprise/supported-regions and docs/enterprise/deployment-optionsread 2026-08-30

Powers are installable plugins bundling MCP tools, skills and knowledge into a single package, browsable in the client or at kiro.dev/powers with one click install and dynamic context activation, built on the Agent Plugins specification with maintainers from Amazon, Cursor, Microsoft, OpenAI and Vercel; Agent Skills ship as standalone portable instruction packages, and a Power Builder converts older formats.

Sourcekiro.dev/docs/powers and docs/skillsread 2026-08-30

One agent harness fronts four surfaces, IDE, CLI, Web and Mobile, with configuration shared through .kiro so a spec started in the IDE continues in the CLI and hands off to the Web agent. Agent hooks fire on file save, commit and repository events, the CLI adds headless mode, ACP and voice, Crew runs continuously around the clock, and the Web surface adds autonomous mode and automations.

Sourcekiro.dev/docs, docs/hooks and docs/cli/headlessread 2026-08-30

Users choose among models from Anthropic (Claude Opus, Sonnet, Haiku and Fable), OpenAI (GPT-5.6 Sol, Terra and Luna), DeepSeek and MiniMax with a configurable reasoning effort, or let Auto route by task, and enterprise administrators govern which models their organization may use.

Sourcekiro.dev/docs/models/available-models and docs/enterprise/governance/modelread 2026-09-29

MCP servers are configurable per workspace, globally or per agent with hot reload, custom agents are defined declaratively in JSON with tools, permissions, resources and lifecycle hooks, Powers follow the open Agent Plugins specification and can be authored and published, and the CLI exposes headless mode and ACP for programmatic and third party client use. Kiro also publishes machine readable schemas and a markdown view of every documentation page.

Sourcekiro.dev/docs/mcp/configuration, docs/custom-agents/configuration-reference and docs/cli/acpread 2026-08-30

Hooks run tests, validate task completion against the spec's requirements document and trigger security scans on file save, commit or repository events, and the spec workflow supports verifying generated code against the written requirements. Those checks test the customer's code against intent, and there is no harness, replay or regression suite for the agent's own behavior.

Sourcekiro.dev/docs/hooks and docs/specsread 2026-08-30

Kiro Crew operates a real browser for the user, navigating, clicking, typing, submitting forms, inspecting accessibility and taking screenshots, through a native Browser tool in the packaged desktop app with a live panel the user can take over, or by attaching to the user's own Chrome when chosen, with approvals applying.

Sourcekiro.dev/docs/crew/features/browserread 2026-09-29