# Kiro

Coding agent with a shared agent core for IDE, CLI, web, and mobile. Specs, Steering, hooks, skills, and MCP structure development work.

Canonical profile: https://agenten-kompass.mmeierhoff.chatgpt.site/en/agents/kiro/
Editor: [Michael Meierhoff](https://agenten-kompass.mmeierhoff.chatgpt.site/en/about/)
Sources reviewed: 2026-09-30
Basis: provider documentation. Examples are editorial suggestions, not hands-on product tests.

## Overview

IDE, CLI, web, and mobile use the same Kiro agent core. Project configuration under .kiro can be shared across interfaces and team members.

- Provider: AWS
- Product family: Kiro
- Profile type: Coding agent across multiple interfaces
- Environment: IDE, CLI, web, mobile, and cloud sandbox
- Connections: Repository, shell, web tools, MCP, skills, hooks, and Agent Client Protocol
- Setup: Choose the appropriate access method, open the repository, and set project configuration under .kiro
- Pricing model: Check plans and usage

## Key features

### One agent core across multiple interfaces

IDE, CLI, web, and mobile access the same agent core and share central project configuration.

Source: https://kiro.dev/docs/how-kiro-works/

### Plan features with specs

Specs structure development work into requirements, design, and actionable tasks.

Source: https://kiro.dev/docs/

### Share project rules through steering

Markdown files keep architecture, conventions, and project knowledge permanently in context.

Source: https://kiro.dev/docs/steering/

### Automate workflows with hooks

Events involving files, tools, and tasks can trigger shell commands or agent actions.

Source: https://kiro.dev/docs/hooks/

### Connect tools through MCP

MCP connects external tools, APIs, and data sources to the agent.

Source: https://kiro.dev/docs/

### Control access with permission rules

Rules for files, shell, MCP, and other capabilities allow, prompt for, or deny individual actions.

Source: https://kiro.dev/docs/cli/chat/security/

## Requirements and limits

### Feature scope differs by interface

Limitation: Not every capability is equally available in IDE, CLI, web, and mobile; availability is stated on the respective feature pages.

Source: https://kiro.dev/docs/how-kiro-works/

### Deliberately version project configuration

Requirement: Shared Specs, Steering, agents, and hooks are stored in the repository under .kiro and apply to team members and other interfaces.

Source: https://kiro.dev/docs/how-kiro-works/

### Set permissions locally

Requirement: Fine-grained rules and interactive approvals are documented for IDE and CLI; web and mobile have different limits.

Source: https://kiro.dev/docs/cli/chat/security/

## Example workflows

### Implement a feature using a spec

- Your input: A product idea, project rules, and testable requirements.
- Possible result: Requirements, design, tasks, and step-by-step implementation.
- What to check: Review the spec, diff, tests, and compliance with steering rules.

### Enforce quality checks with a hook

- Your input: A repository, defined verification commands, and the appropriate hook trigger.
- Possible result: Automatically run lint, formatting, or test checks at defined points.
- What to check: Test hook permissions, exit codes, logs, and behavior on every interface used.

## Context

The interfaces support individual features differently. Check project configuration, permissions, and cloud access before working.

Current Kiro documentation for the unified agent core. The documentation specifies availability for each interface.

## Sources

- https://kiro.dev/docs/

- https://kiro.dev/docs/how-kiro-works/

- https://kiro.dev/docs/ide/

- https://kiro.dev/docs/steering/

- https://kiro.dev/docs/hooks/

- https://kiro.dev/docs/cli/chat/security/

[Sources and method](https://agenten-kompass.mmeierhoff.chatgpt.site/en/sources/)