Loading image...Kiro

Product

  • About Kiro
  • IDE
  • CLI
  • Web
  • Mobile
  • Crew
  • Pricing
  • Downloads

For

  • Enterprise
  • Startups
  • Students

Community

  • Overview
  • Ambassadors
  • Discord
  • Events
  • Powers
  • Shop
  • Showcase

Resources

  • Docs
  • Blog
  • Changelog
  • FAQs
  • Report a bug
  • Suggest an idea
  • Billing support

Social

Site TermsLicenseResponsible AI PolicyLegalPrivacy PolicyCookie Preferences
Loading image...Kiro
  • CLI
  • Web
  • Enterprise
  • Pricing
  • Docs
SIGN INDOWNLOADS
Loading image...Kiro

Get Started

InstallationAuthenticationYour first project

Models

OverviewAvailable modelsReasoning effort

Features

How Kiro works
Specs
Steering
Hooks
MCP
Permissions
Custom agents
Agent Skills
Powers
Cloud sessionsCompactionKiroignoreCheckpoints and rewind
Built-in tools
Configuration scopes

IDE 1.x

What's new in 1.0
Setup & First Run
Editor
Chat
Experimental
Troubleshooting0.x reference

CLI

What's new in 3.0
Setup & First Run
Terminal UI
Chat
Voice modeHeadless modeACPAuto complete
Experimental
2.x reference

Crew

Quick startInstallationRunning 24/7
Chat
Agent Capabilities
Features
Interfaces
Apps
ConfigurationSecurityTroubleshooting

Web - Preview

Setup & First RunIdentity Center
Connect your repositories
Working with the agent
Autonomous modeAutomationsMemory
Sandbox

Mobile - Preview

Overview

Commands and Reference

CLI commandsSlash commandsBuilt-in toolsExit codesSettings

Billing

OverviewManaging your subscriptionUpgrading your planDowngrading your planCancelling your planPurchasing add-on creditsManaging your paymentsManaging usage notificationsManaging your taxesContacting billing supportDeleting your accountRelated questions

Enterprise

ConceptsOnboarding quickstart
Connecting your identity provider
Subscribe your teamManage subscriptions
Governance
Monitor and track
SettingsManaged updatesBillingIAMSupported regions

Privacy and Security

OverviewData protectionCode referencesCompliance validationInfrastructure securityIAM permissionsFirewalls, proxies, and data perimetersVPC endpoints (AWS PrivateLink)

Guides

Overview
Language support
Learn by playing

Migration

Migrating from Q DeveloperMigrating from VSCodeUpgrading from Q CLI
  1. Docs
  2. Get Started
  3. Your first project
View as Markdown

Your first project

View as Markdown

This guide walks you through Kiro's essential features by working with a real project. You'll learn how to set up steering files, build features with specs, automate workflows with hooks, and extend capabilities with MCP servers.

Prerequisites

Before starting, ensure you have:

  • Installed Kiro
  • Signed in with your Kiro account
  • A project to work with (either an existing project or a new one)
  • Basic familiarity with your project's structure and technology stack

Open your project

  1. Launch Kiro and open your project:

    • Use File > Open Folder to select your project directory
    • Or drag and drop your project folder into Kiro
    • Or run kiro . from your project directory in the command line
  2. Access the Kiro Panel:

    • Click the Kiro Ghost icon in the activity bar (left sidebar)
    • This panel provides access to all of Kiro's AI-powered features
  3. Start a Chat Session:

    • The chat pane should be open by default
    • This opens Kiro's conversational interface where you interact with the AI

Set up steering files

Steering files provide context about your project, helping Kiro understand your codebase, conventions, and requirements. They are stored in .kiro/steering/ and shared across all Kiro surfaces.

Choose Generate Steering Docs from the Kiro panel. Kiro analyzes your repository and generates steering documents that guide its behavior, including:

  • Your product and its purpose
  • Technical stack and frameworks
  • Project structure and conventions

You can also create custom steering files by clicking the + button in the steering section to add coding standards, workflows, and team best practices.

View transcript: Generating steering documents in Kiro

Learn more about steering in the Steering documentation.

Build features with specs

Specs transform high-level feature ideas into detailed implementation plans through three phases:

  1. Requirements - User stories with acceptance criteria
  2. Design - Technical architecture and implementation approach
  3. Tasks - Discrete, trackable implementation steps

Create your first spec

  1. Start a new spec:

    • Click the Spec button in your chat session
    • Or choose the + button in the Kiro panel's Specs section
  2. Enter a feature description:

    • Describe your feature in natural language
    • Example: "Add a user authentication system with login, logout, and password reset functionality"
  3. Follow the guided workflow:

    • Requirements phase: Kiro structures your requirements using EARS notation
    • Design phase: Technical architecture and component design are documented
    • Implementation phase: Discrete tasks are generated for execution

View transcript: Creating a spec in Kiro

Execute spec tasks

Once your spec is complete:

  1. Review generated tasks in the tasks.md file
  2. Execute tasks by clicking on individual task items
  3. Track progress as tasks automatically update to "In Progress" and "Done"

Learn more about specs in the Specs documentation.

Automate workflows with hooks

Agent hooks eliminate manual work by automatically executing predefined actions when specific agent events occur, such as file changes, tool use, or task execution.

  1. Access hook creation:

    • Navigate to the Agent Hooks section in the Kiro panel
    • Click the + button to create a new hook
  2. Define hook behavior:

    • Describe what you want automated in natural language
    • Example: "When the agent saves a React component file, automatically create or update its corresponding test file"
  3. Configure hook settings:

    • Event type: Choose when the hook triggers - agent file events (created, saved, deleted), prompt and agent lifecycle events, or spec task events
    • File pattern: Specify which files should trigger the hook (e.g., src/**/*.tsx)
    • Instructions: Define the specific actions to perform

Learn more in the Hooks documentation.

Extend capabilities with MCP

Model Context Protocol (MCP) allows Kiro to access specialized tools, APIs, knowledge bases, and external services.

Set up MCP

  1. Open the Kiro panel by clicking the Kiro Ghost icon in the activity bar. Enable MCPs, then click the edit button (pencil icon) next to MCP in the panel.
  2. By default, Kiro ships with the fetch MCP server. Set disabled to false to connect to it.
  3. Add any MCP server by editing the JSON file:
json
{ "mcpServers": { "web-search": { "command": "uvx", "args": ["mcp-server-brave-search"], "env": { "BRAVE_API_KEY": "your-api-key-here" }, "disabled": false, "autoApprove": ["search"] } } }

Use MCP tools

Once configured, reference MCP tools in several ways:

  • Direct questions: Ask questions that leverage the server's capabilities
  • Explicit tool usage: Reference specific tools with the #MCP context provider
  • Integration: Combine MCP with hooks and specs for automated workflows

Learn more in the MCP documentation.

Next steps

Now that you've experienced Kiro's core features:

  • Try the interactive tutorial: Work through the hands-on game development tutorial
  • Explore specs in depth: Check out the Specs documentation for the full workflow
  • Learn about steering: Read the Steering documentation for advanced configuration
  • Join the community: Connect with other Kiro users on Discord
Page updated: August 21, 2026
Authentication
Models