Installation - Crew - Docs - Kiro Loading image... 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 * * * * * * * English Site Terms License Responsible AI Policy Legal Privacy Policy Cookie Preferences English Loading image... * Apps * CLI * Web * Enterprise * Pricing * Docs * Community * Resources SIGN IN DOWNLOADS Loading image... Get Started Installation Authentication Your first project Models Overview Available models Reasoning effort Features How Kiro works Specs Steering Hooks MCP Permissions Custom agents Agent Skills Powers Cloud sessions Compaction Kiroignore Checkpoints and rewind Built-in tools Configuration scopes IDE 1.x What's new in 1.0 Setup & First Run Editor Chat Experimental Troubleshooting 0.x reference CLI What's new in 3.0 Setup & First Run Terminal UI Chat Voice mode Headless mode ACP Auto complete Experimental 2.x reference Crew Quick start Installation Running 24/7 Chat Agent Capabilities Features Interfaces Apps System & storage Configuration Security Troubleshooting Web Setup & First Run Identity Center Connect your repositories Working with the agent Autonomous mode Automations Memory Configuration Sync Sandbox Mobile - Preview Overview Commands and Reference CLI commands Slash commands Built-in tools Exit codes Settings Billing Overview Managing your subscription Upgrading your plan Downgrading your plan Cancelling your plan Purchasing add-on credits Managing your payments Managing usage notifications Managing your taxes Contacting billing support Deleting your account Related questions Enterprise Concepts Onboarding quickstart Connecting your identity provider Deployment options Subscribe your team Manage subscriptions Governance Monitor and track Settings Managed updates Billing IAM Supported regions Privacy and Security Overview Data protection Code references Compliance validation Infrastructure security IAM permissions Firewalls, proxies, and data perimeters VPC endpoints (AWS PrivateLink) Guides Overview Language support Learn by playing Migration Migrating from Q Developer Migrating from VSCode Upgrading from Q CLI * Docs * * Crew * * Installation Copy page View as Markdown Installation Copy page View as Markdown Crew ships as a Python package that bundles the React dashboard. There are four ways to install it — pick whichever fits how you'll run it. All builds are driven by plain pip + npm /Vite + pytest . No proprietary tooling. Prerequisites Requirement Needed for Notes Python 3.10+ Backend runtime 3.12 recommended Node.js 22+ Building the dashboard from source 24 LTS recommended. Not needed for the prebuilt wheel, desktop app, or Docker image kiro-cli Talking to the LLM Installed via the dashboard or desktop app on first launch Crew drives an LLM through kiro-cli over the Agent Client Protocol . It is the only provider ( agent.provider = acp ). The first desktop or dashboard launch can install Kiro CLI on the Gateway host and guide device-code sign-in before chat opens. kirocrew doctor reports whether the binary is found and logged in. Semantic memory needs no setup. Embeddings run in-process and the Gateway downloads its embedding model (~610 MB) in the background on first start, verifies it, and stores it under ~/.kiro/crew/models . Until the model lands, memory search falls back to keyword matching and picks up embeddings automatically without a restart. Set KIROCREW_EMBED_MODEL_URL to point at a mirror for airgapped installs. Choose an installer Desktop app One-line wheel From source Docker Download Kiro Crew for macOS (signed .dmg ), Windows (signed installer), or Linux ( .deb , .rpm , or .AppImage ). The app starts a bundled Gateway when no local Gateway is already running, and agent sessions and ACP processes then run on demand on the same machine. It can connect to a remote Gateway over an SSH tunnel instead. The Windows installer is signed and updates itself in the background on the stable channel, alongside macOS and Linux. On Linux, the .deb and .rpm packages install to a fixed path, register a desktop entry, and update in place per format. The Linux desktop app needs glibc 2.34 or newer, which excludes older hosts such as Ubuntu 20.04, Debian 11, and Amazon Linux 2. On an older host, install the one-line wheel instead (see the next tab) and open the dashboard in your browser. Linux ships native builds for both x86_64 and ARM64 (aarch64) , published with an architecture check so you don't install the build for the wrong architecture. You can also build the app yourself with make desktop . Windows Crew supports Windows natively. Use CPython 3.12 + a venv + pip install -e . tzdata , and launch with python -m kiro_crew gateway . powershell py - 3 . 12 - m venv . venv . venv\Scripts\activate pip install - e . tzdata python - m kiro_crew gateway All POSIX-only process, signal, file-lock, and metrics calls are routed through kiro_crew.platform_compat . The OS-level filesystem sandbox (Linux namespaces / macOS Seatbelt) is not available on Windows; every other feature works, and Computer Use drives native Windows applications through UI Automation. The interactive web-terminal and the SSO-login PTY degrade to a clear "not supported on Windows" response rather than crashing. Configure and verify For the one-line wheel, source build, and Docker installs, set up and verify after installing: bash kirocrew setup # interactive wizard: data dir, agent, credentials kirocrew doctor # verify everything is wired up kirocrew gateway # start the server → http://localhost:5476 kirocrew doctor reports the status of the kiro-cli binary, its authentication, Ollama/embeddings, Slack tokens, config validity, and MCP servers. Info The desktop app handles this automatically — it starts a bundled Gateway on launch and guides kiro-cli installation and sign-in from the app itself. These steps are only needed for the CLI-based install paths. Data home All persistent state lives under ~/.kiro/crew/ (override with KIROCREW_HOME ): ~/.kiro/crew/ ├── config.json # user configuration ├── .env # Slack tokens, owner ID, other credentials ├── workspace/ │ ├── memory/ # preferences.md, projects.md, history/ │ ├── lessons.jsonl # learned corrections │ └── knowledge/ # ingested documents (FTS5 + vectors) ├── conversations/ # JSONL session logs ├── crons.json # scheduled jobs ├── audit.log # bash command audit trail └── agents/ # generated kiro-cli agent configs Environment variables Variable Default Purpose KIROCREW_HOME ~/.kiro/crew Data directory (config, credentials, databases) KIROCREW_PORT 5476 Port the gateway binds to KIROCREW_EMBED_MODEL_URL (CDN) Override the embedding-model download URL (for mirrors) Both KIROCREW_HOME and KIROCREW_PORT are validated at CLI entry, not stored as config keys. Pass --port on the CLI to override the env var per-invocation. Optional extras Install with pip install "kirocrew[<extra>]" : Extra Adds voice boto3 , amazon-transcribe for cloud speech-to-text aws boto3 for AWS integrations Piper TTS is the default text-to-speech provider and runs locally — no extra install needed. Page updated: August 31, 2026 Crew Running 24/7