Loading image...Kiro

Product

  • About Kiro
  • IDE
  • CLI
  • Web
  • Mobile
  • 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
  • IDE
  • Web
  • Mobile
  • 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
CompactionKiroignoreCheckpoints and rewind
Built-in tools
Configuration scopes

IDE 1.x

What's new in 1.0
Setup & First Run
Editor
Chat
Autopilot
Slash commands
Agent notifications
Dockable chat
Export sessions
Terminal
Dev servers
Experimental
Troubleshooting0.x reference

CLI

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

Web - Preview

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

Mobile - Preview

Overview

Commands and Reference

CLI commandsSlash commandsBuilt-in toolsExit codesSettingsIDE keyboard shortcuts

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. IDE 1.x
  3. Chat
  4. Terminal

Terminal integration


Kiro's terminal integration lets the agent run shell commands on your behalf. Describe what you want in natural language, like installing dependencies, checking git status, or running tests, and Kiro translates your request into the appropriate command. A built-in approval system keeps you in control of what executes.

Loading image...Kiro command approval dialog showing options to Allow, Always allow, Deny, or Always deny an npm install command
Tip

Long-running commands like Dev Servers are automatically managed by Kiro, running in dedicated terminals without blocking your workflow.

Command approval and security

When Kiro suggests a command, you have four options:

  • Allow: Execute the command once
  • Always allow: Execute and trust similar commands in the future
  • Deny: Reject execution
  • Always deny: Block similar commands going forward

You control which commands require approval through the Permissions system. Define shell capability rules in your permissions.yaml to allow, deny, or prompt for specific command patterns:

yaml
# ~/.kiro/settings/permissions.yaml rules: - capability: shell match: ["git *", "npm *", "npx *"] effect: allow - capability: shell match: ["rm -rf *", "sudo *"] effect: deny

For the full reference on configuring shell permissions, see Permissions.

Using terminal context

Reference recent output from your active terminal in your conversations with #terminal. Important: #terminal always refers to the currently active/visible terminal window. If you have multiple terminals open, make sure the terminal you want to reference is active before using #terminal in your chat.

This feature allows Kiro to analyze command results, debug errors, and suggest solutions based on your actual terminal session.

#terminal analyze the error from the last npm run build

Kiro maintains awareness of command history and outputs, enabling:

  • Error Analysis: Understanding why commands failed with specific error messages
  • Output Interpretation: Explaining complex command results and logs
  • Follow-up Actions: Suggesting next steps based on actual results
  • Pattern Recognition: Identifying recurring issues across multiple commands
  • Environment Debugging: Helping resolve system and dependency conflicts

Troubleshooting

For issues with terminal integration and manual setup instructions, see the Shell Integration troubleshooting guide.

Page updated: August 4, 2026
Export sessions
Dev servers