Quick start
You choose how to run Kiro Crew: the desktop app with automatic updates, a
one-line install on your machine or a remote host, the Docker image for
always-on servers, or a build from source. The default agent runs on
kiro-cli, which you install and sign in to separately. First launch checks
that prerequisite and links to the official setup guide when it is missing.
App downloads
Each link fetches the newest build on that channel, and the app then updates
itself on the same channel. Take Stable unless you have a reason not to; see
Release channels below.
On Linux, start with the one-line install below and add a desktop package when
you want a native window and in-app updates. The
install guide owns
which Linux package to pick, platform requirements, and sandbox setup.
Release channels
Stable is the default; Insider follows release candidates, and Nightly follows
main. The release runbook owns the
current triggers, version shapes, promotion behavior, cadence, and update-lane
semantics.
One-line install
Install the signed Stable wheel without cloning the repository or building the
frontend:
curl -fsSL https://download.crew.kiro.dev/cli.sh | sh
Then open http://localhost:5476. Pass --version to pin an exact release —
the minimum pinnable release is 0.1.2, because 0.1.0 and 0.1.1 predate
manifest signing and have no signed manifest to resolve:
curl -fsSL https://download.crew.kiro.dev/cli.sh | sh -s -- --version 0.6.0
The install guide owns
channel selection, managed versus system Python, mirrors, first-run setup,
upgrades, and recovery.
Docker
For always-on servers, the Gateway ships as a public multi-arch image on GHCR:
docker run -d --name kirocrew \
-p 127.0.0.1:5476:5476 \
-v kirocrew-home:/home/kirocrew \
ghcr.io/kirodotdev/kirocrew:stable
See the Docker guide for first-run login, channel tags,
upgrades, and the container security
model.
Build from source
macOS and Linux require Python 3.12+, Node.js 22.12+ (24 LTS recommended), and
npm. The default ACP backend also requires
kiro-cli: install it on the Gateway host and run
kiro-cli login before using that backend. Other verified ACP harnesses have
their own prerequisites in the install guide. Windows
is supported through a native source install; follow the
Windows guide instead of the shell steps below.
# 1. Clone and build Kiro Crew
git clone https://github.com/kirodotdev/KiroCrew.git
cd KiroCrew
make build
source .venv/bin/activate
# 2. Configure, verify, and start
kirocrew setup
kirocrew doctor
kirocrew gateway
Why Kiro Crew
Most agent sessions end when the chat closes. Kiro Crew runs continuously on
hardware you control and keeps working between conversations.
Persistent. Sessions, memory, schedules, and task checkpoints survive
Gateway restarts, and scheduled or reactive work continues without someone at
the terminal.
Self-learning. Corrections and task failures become durable lessons.
Preferences and project context carry into new sessions.
Self-evolving. Repeated patterns become reusable skills. Memory, lessons,
and skills stay visible and editable, so each Kiro Crew grows more tailored to
the person and work around it.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
