Kiro Crew

A persistent workspace for development work that self-improves and continues beyond one session.

Kiro Crew is an open source development workspace that runs locally or remotely on your hardware. It is persistent, self-learning, and self-evolving. Work with it from the desktop app, web dashboard, and CLI, or continue the same work through connection tools like Slack and Discord. Your multi-step tasks can run unattended, recurring jobs run on your schedule, and heartbeats monitor systems until something needs attention. Kiro Crew Apps tailor that experience to a specific job, combining a purpose-built interface with agents, skills, schedules, integrations, and backend services.

Quick start · Build from source · Why Kiro Crew · Capabilities · How it works · Security · Install · Telemetry · Docs

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, 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.

Runs where you choose. Your Mac, a local container, or a remote machine you control.

One Gateway, many surfaces. Work directly in the desktop app or web dashboard, or continue the same work from the CLI and messaging surfaces like Slack and Discord.

What Kiro Crew does