Agenten-Kompass

AGENT PROFILES

Kiro

AWS · Coding agents

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

Develop software

Kiro · Coding agent across multiple interfaces

Product and access

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

01

Core features

6 features from provider sources · sources reviewed on September 30, 2026. Availability and limitations are listed directly below.

  • One agent core across multiple interfaces

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

    Source 2

  • Plan features with specs

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

    Source 1

  • Share project rules through steering

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

    Source 4

  • Automate workflows with hooks

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

    Source 5

  • Connect tools through MCP

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

    Source 1

  • Control access with permission rules

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

    Source 6
02

Requirements and limits

‘Still open’ means the reviewed sources do not answer this point clearly.

  • Limitation

    Feature scope differs by interface

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

    Source 2

  • Requirement

    Deliberately version project configuration

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

    Source 2

  • Requirement

    Set permissions locally

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

    Source 6
03

Practical tasks

Editorial examples based on documented features. No product tests performed.

01

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.
02

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.
EDITORIAL EXAMPLE

Plan and implement a feature with requirements, design, and tasks, then check it against project-wide rules.

Your possible prompt

Read the project rules. Investigate [error], propose a small change, and run the relevant checks. Show me the diff and any remaining uncertainties.

Getting-started idea based on documented capabilities. Not an executed product test. Adapt the task, data, and permissions.

04

What you should know first

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

Requirements & limitations

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

Setup

Choose the appropriate access point, open the repository, and set project configuration under .kiro.

Pricing model

Check plan / usage. Check current terms and included quotas with the provider.

The classification indicates the scope of effort. It is not a price or performance commitment.

05

Sources from the provider

Editorial team: Michael Meierhoff · sources reviewed on . Provider information is not independent evidence of performance.

Read profile as Markdown

How we assess the sources