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
Fullscreen modeVoice modeHeadless modeACPAuto complete
Experimental
2.x reference

Crew

Quick startInstallationRunning 24/7
Chat
Agent Capabilities
Features
Interfaces
Apps
System & storageConfigurationSecurityTroubleshooting

Web

Setup & First RunIdentity Center
Connect your repositories
Working with the agent
Autonomous modeAutomationsMemoryConfiguration Sync
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
Deployment optionsSubscribe 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
View as Markdown

Configuration

View as Markdown

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" } }

Runtime, safety, and preview settings

The following keys are useful when you manage config.json directly. Missing keys use their defaults.

KeyDefaultMeaning
agent.chat_turn_timeout_secs14400Maximum wall-clock time for one chat turn, up to 24 hours.
agent.subagent_timeout_secs10800Maximum wall-clock time for a subagent. 0 uses the default.
agent.subagent_max_turns100Default tool-call budget per subagent. Values are capped at 1000.
agent.session_controltrueLets an agent open, stop, read, and send to eligible sessions in the same workspace. Set it to false to withdraw that capability from every agent.
orchestrator.max_plan_duration_seconds7200Whole-plan limit for unattended auto-run plans. Set 0 to remove the limit. Plans that advance through stage gates are exempt because each stage needs your approval.
agent.sandbox"auto"Chooses the normal sandbox posture for agent subprocesses.
agent.sandbox_allow_unsandboxed_execfalseAllows execution without a sandbox backend only when explicitly set to true. Leave it false to fail closed when no backend is available.
dashboard.terminal.completion.enabledtrueSet to false to disable inline completion menus in the built-in terminal.
telemetry.enabledfalseEnables local metrics collection under ~/.kiro/crew/metrics. It does not enable network export by itself.
instances.enabledfalseEnables multi-instance management and SSH tunnels to connected Kiro Crew gateways.
instances.warm_set_cap0Number of connected instances kept warm with a live tunnel. 0 sizes the warm set automatically for eligible instances, capped at 8.
instances.tunnel_base_port7778First local port used for SSH tunnels to connected instances.
instances.max_recovery_attempts8Reconnect attempts before an instance is marked unreachable.
instances.recover_backoff_max_secs30Maximum wait between reconnect attempts.
instances.probe_failure_threshold3Consecutive failed health probes before recovery starts.
capabilities.publishDisabled by defaultGovernance capability for artifact publishing. Configure it through the applicable governance policy, not config.json.
publish.allowed_destinations[]Publish-provider IDs the operator permits. An empty list allows registered destinations, subject to the capabilities.publish governance ceiling.

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.

Language

The dashboard interface ships in twelve languages: English, German, Spanish, French, Italian, Portuguese, Russian, Hindi, Bengali, Chinese, Korean, and Japanese. Change the interface language from the dashboard Settings panel. CJK (Chinese, Japanese, Korean) text renders correctly throughout, including bold, italic, and strikethrough in prose.

Language applies to the interface. The agent responds in whatever language you write to it in, independent of this setting.

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: September 12, 2026
System & storage
Security