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
  • 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
Experimental
Troubleshooting0.x reference

CLI

What's new in 3.0
Setup & First Run
Terminal UI
Chat
Headless 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 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. Crew
  3. Configuration

Configuration


Most configuration is managed from the Settings panel in the dashboard. Open it from the sidebar — every setting has a description and type-safe controls. Changes take effect immediately.

Settings panel

The Settings panel is organized into sections:

SectionWhat you configure
OverviewQuick status and system info
ImportsImport settings from another instance
ChatSession timeout, autopilot default, bot name
DisplayThemes and color theme (14 themes with dark/light variants)
VoiceSTT provider, TTS voice and speed
NotificationsNotification preferences
ShortcutsKeyboard shortcut customization
SkillsSkill loading behavior
ChannelsSlack, Discord, Telegram, Teams, Webex, WeCom, WeChat credentials and settings
BrowserBrowser automation settings
Computer UseDesktop automation enable/disable
InstancesMulti-instance management
SecuritySandbox mode, denied commands, governance
DeveloperDeveloper-facing options
AboutVersion info and updates

CLI alternative

For headless environments or scripting, use kirocrew config:

bash
kirocrew config get # print full config kirocrew config get agent.sandbox # print one key kirocrew config set dashboard.bot_name "X" # set a key kirocrew config edit # open in $EDITOR

Setting a value auto-triggers a session pool restart so the change takes effect immediately.

Config file

Settings persist to ~/.kiro/crew/config.json. You can edit this file directly if you prefer — the format is standard JSON with missing keys falling back to defaults.

json
{ "agent": { "provider": "acp", "approval_mode": "interactive", "sandbox": "auto" }, "session": { "timeout_secs": 1800, "pool_size": 2 }, "dashboard": { "bot_name": "Crew" } }

Themes

14-theme color system with dark and light variants. Change from Settings → Display → Color Theme in the dashboard. You can also create custom themes or import themes shared by others.

Channel credentials

Channel tokens live in ~/.kiro/crew/.env (not in config.json) for security. Configure them from the dashboard's Settings → Channels panel, or set them manually:

SLACK_APP_TOKEN=xapp-… SLACK_BOT_TOKEN=xoxb-… KIROCREW_OWNER_ID=U0… DISCORD_BOT_TOKEN=… TELEGRAM_BOT_TOKEN=… WECOM_BOT_ID=… WECOM_SECRET=…

The file is enforced at mode 600 (owner-only read/write).

Environment variables

Two environment variables control runtime behavior that can't live in config.json:

VariableDefaultPurpose
KIROCREW_HOME~/.kiro/crewData directory — where config, memory, and credentials live
KIROCREW_PORT5476Port the gateway binds to

Set these before starting the gateway. Override the port per-invocation with kirocrew gateway --port <n>.

Data home

All persistent state lives under ~/.kiro/crew/ (or wherever KIROCREW_HOME points). See the Installation page for the full directory layout.

Page updated: August 4, 2026
Publishing & guidelines
Security