Kiro Crew is an autonomous AI agent layer that runs on your own machine on top of the kiro-cli (KiroACP) backend. It adds persistent memory, scheduled jobs, background subagents, self-learning, and multi-session orchestration, and you talk to it from a web dashboard, from the terminal, or from messaging channels like Slack, Discord, and Telegram.
| Requirement | Needed for | Floor |
|---|---|---|
| Python + pip | Backend | >= 3.12 |
| Node.js + npm | Building the dashboard from source | >= 22.12 (24 LTS recommended) |
kiro-cli |
Driving the LLM | Required, on your PATH |
Node is only needed to build the dashboard. The prebuilt wheel, the macOS DMG, and the Linux AppImage all ship the dashboard already bundled, so if you install one of those you need neither Node nor a compiler.
Platforms: macOS, Linux, and Windows. Windows runs natively from a Python
source install and is launched as python -m kiro_crew gateway.
Embeddings need no setup step. They run in-process, and on first start the gateway downloads the embedding model (about 610 MB) in the background and verifies it against a pinned sha256. Until it lands, memory search falls back to keyword search and picks up semantic search automatically with no restart.
curl -fsSL https://download.crew.kiro.dev/cli.sh | shThis installs a signed, sha256-verified kirocrew wheel. stable is the
default channel; pass --channel insider or --channel nightly to track a
faster one, or --version X.Y.Z to pin an exact release. The installer uses
pipx when available, otherwise it creates a managed venv and symlinks
kirocrew into ~/.local/bin.
pip install kirocrew alone does not work: Kiro Crew is not published to
PyPI. To install with pip directly, point it at a release channel's index:
pip install --pre kirocrew \
--extra-index-url https://updates.crew.kiro.dev/feed/stable/simple/--extra-index-url (not --index-url) is required, because the channel index
carries only kirocrew and pip still needs PyPI to resolve its dependencies.
git clone https://github.com/kirodotdev/KiroCrew.git
cd KiroCrew
cd website && npm install && npm run build && cd ..
pip install -e ".[voice]" # [voice] adds the optional speech-to-text extrasThe dashboard has to be built before the backend install, because the built
website/dist is staged into the package and served by the gateway. make build does both steps plus a .venv.
kiro-cli is the only provider (agent.provider is fixed to acp). Install it
per its own docs, make sure the binary resolves on your PATH, and log in:
kiro-cli loginOn the first dashboard launch, the Set up Kiro page walks through installing the CLI and completing sign-in.
Already a kiro-cli user? Coming from kiro-cli covers
what carries over (agents, MCP servers, steering, your login), why a Crew chat
behaves differently from kiro-cli chat, and how to get CLI-style behaviour.
kirocrew setupThis interactive wizard detects kiro-cli on your PATH, saves the project
directory so Kiro Crew works from any working directory, installs the agent
config to ~/.kiro/agents/kirocrew.json, and walks through the workspace
directory, timezone, dashboard URL, and the http://kirocrew.localhost:5476
custom domain. It configures no messaging channels: connect them after setup
from the dashboard, or run kirocrew setup --slack for the guided Slack setup.
To browse, install the Playwright agent CLI (needs Node.js 20 or newer):
npm install -g @playwright/cli@latest
playwright-cli install-browser chromium
playwright-cli install --skills agents --globalinstall-browser downloads a separate Chromium build into your user cache and
needs no root. It does not install Google Chrome, and it does not install OS
libraries. If the download reports missing libraries, install them with your own
package manager; on Debian or Ubuntu sudo npx playwright install-deps chromium
does it. The Settings → Browser page runs the same download on the machine the
gateway runs on. On a Debian or Ubuntu (apt) host it first tries the download
with Playwright's --with-deps, which also installs the libraries, and retries
without it if that step is refused. It prints the library command for that
machine when one is still needed.
Having playwright-cli on your PATH is what makes browsing available, so
uninstalling it is how you take the capability away. Note that it covers
playwright-cli attach --extension, which drives your own running Chrome with
the sessions you are logged into. The dashboard's Browser panel shows the
live session and lets you take over with real mouse and keyboard, which is how
you complete a CAPTCHA or a 2FA prompt.
Use kirocrew setup --agent-only to reinstall just the agent config and skip
the other wizard steps. --electron-only installs only the desktop app (macOS),
and --clean treats the run as a fresh install rather than merging MCP servers
and tools from an existing config.
The default wizard configures no messaging channels — the dashboard and CLI need
none. Two channels have a guided terminal setup: kirocrew setup --slack, and
kirocrew setup --whatsapp, which reports the optional whatsapp extra and the
pairing state before enabling the channel. Both are ignored with --agent-only.
--slack prompts for:
SLACK_APP_TOKENstarts withxapp-SLACK_BOT_TOKENstarts withxoxb-KIROCREW_OWNER_IDis your Slack user ID (starts withU)
Use the user ID from the workspace where the bot is installed: your user ID is different in every Slack workspace. Only the owner is authorized to interact over Slack.
These are stored in ~/.kiro/crew/.env.
Every other messaging channel is connected from the dashboard — the roster is in the documentation index, and each channel has its own doc there.
kirocrew gatewayThis starts the full server: web dashboard, listeners for every configured
messaging channel, cron scheduler, heartbeat, and update checker. The dashboard
is at http://localhost:5476.
kirocrew chat # interactive REPL
kirocrew chat -m "what's the weather like?" # single messageLightweight mode: no messaging channels, no dashboard, just a terminal conversation.
kirocrew doctorReports, among other checks, the resolved platform edition, the kiro-cli binary
and login state, the project directory, the agent config and its MCP entries,
confinement and the sandbox, services, channels and access, workload, Slack
credentials, gateway status, and the embedding runtime and model. It repairs
missing MCP entries where it can, and prints a specific fix hint for anything it
cannot. kirocrew doctor --help lists its options.
kirocrew updateFor a source checkout this updates the checkout and rebuilds it. Restart the gateway with kirocrew restart to use the new version. Clicking "Update Available" in the dashboard topbar runs the same path.
kirocrew service install # launchd LaunchAgent on macOS, systemd unit on Linux
kirocrew service status
kirocrew service uninstallThe service survives an SSH disconnect, restarts on crash, and starts on boot.
On Linux the install prompts for sudo once to write the unit; the gateway
itself then runs as your own user. macOS needs no sudo.
Tail its output with kirocrew logs -f.
export KIROCREW_HOME=.kirocrew-dev
export KIROCREW_PORT=6777
kirocrew gatewayKIROCREW_HOME gives the instance its own data directory, so dev memory, crons,
and sessions never touch your real ~/.kiro/crew. KIROCREW_PORT lets a second
gateway run alongside the first. The two together are what make it safe to run
several Kiro Crew instances at once.