Kiro Crew is an open source, Apache-2.0 licensed development workspace that runs on your own hardware, persists across sessions, and self-improves, built for developers and teams who want unattended agentic development work rather than a chat session that forgets everything when it closes.

What it is

Kiro Crew is an open source development workspace written in Python and released under the Apache-2.0 licence. It runs locally or remotely on your hardware, and it is persistent, self-learning, and self-evolving by design. It sits in the AI & Machine Learning / AI Development Platforms category and lives in the agentic AI and LLM tooling ecosystem, tagged agent, agentic-ai, agents, ai-agent, ai-agents, automation, devtools, kiro, and llm. You work with it through a desktop app, a web dashboard, and a CLI, and you can continue the same work through connection tools such as Slack and Discord.

The concrete problem it solves is continuity. Ordinary agent sessions end, and everything accumulated in them has to be rebuilt by hand; Kiro Crew replaces that one-session interaction model with a workspace where multi-step tasks can run unattended, recurring jobs run on your schedule, and heartbeats monitor systems until something needs attention. Kiro Crew Apps extend this by tailoring the experience to a specific job, combining a purpose-built interface with agents, skills, schedules, integrations, and backend services. The default agent runs on kiro-cli, which is installed and signed in to separately; first launch checks for that prerequisite and links to the official setup guide when it is missing.

Key capabilities

• Persistent workspace state that continues the same work across sessions, so an unattended multi-step task is not lost when a session ends.
• Scheduled execution: recurring jobs run on a schedule, and heartbeats monitor systems until something needs attention.
• Three primary interfaces — the desktop app, the web dashboard at http://localhost:5476, and the CLI — plus connection tools such as Slack and Discord for continuing the same work.
• Four documented ways to run it: the desktop app with automatic updates, a one-line install, the Docker image for always-on servers, or a build from source.
• Kiro Crew Apps, which pair a purpose-built interface with agents, skills, schedules, integrations, and backend services for a specific job.
• A bundled Gateway: the desktop app starts one when no local Gateway is already running, updates itself on the channel it was downloaded from, and can connect to a remote Gateway over an SSH tunnel.
• Native packaging for Linux in .deb, .rpm, and AppImage form on both x86_64 and aarch64, with the .deb and .rpm laying down the AppArmor profile the agent sandbox needs on Ubuntu 23.10 and later.

Who uses it and how

• Developers who want agent work to survive past a single session and who are willing to run the workspace on their own laptop, workstation, or remote host.
• Teams running always-on infrastructure, who use the Docker image so scheduled jobs and heartbeats keep running when no desktop app is open.
• Developers who already live in chat, who continue the same work through the Slack and Discord connection tools instead of switching to the dashboard.
• Operators who build or install a Kiro Crew App for a specific job, so the interface, agents, schedules, and integrations are assembled for that one workload.
• Linux users on Debian, Ubuntu, Fedora, RHEL, CentOS Stream, Amazon Linux 2023, or any FUSE-capable distro who want the on-PATH kirocrew command and service installation rather than the Electron shell.

Getting started

The smoothest path on Linux is the one-line install, curl -fsSL https://download.crew.kiro.dev/cli.sh | sh, which puts kirocrew on your PATH and makes kirocrew service install reachable; you then work in the dashboard at http://localhost:5476. Desktop builds are also published for macOS (Apple Silicon and Intel), Windows x64, and Linux in .deb, .rpm, and AppImage form, alongside a Docker image for always-on servers and a build-from-source path.

How it compares

This registry entry names no comparable tools and no list of paid products that Kiro Crew replaces, so no licence, hosting, or cost-model contrast can be drawn from the available facts. On the evidence provided, it stands alone in this registry.

When to use it — and when not to

A self-hoster takes on real operational surface: installing and signing in to kiro-cli separately, running and maintaining a Gateway, choosing between the Stable, Insider, and Nightly channels, and on Ubuntu 23.10 or later handling the AppArmor sandbox profile that the packaged installs set up but the AppImage leaves as a manual step. The project is active — last push on 2026-09-18 — but carries 1,885 open issues against 3,991 stars and 615 forks, a ratio that signals fast-moving, still-settling development. Anyone who does not want to own the prerequisite CLI, the Gateway, and the host itself should look elsewhere, and anyone needing a long-term stable surface should weigh that open-issue count before committing.

curl -fsSL https://download.crew.kiro.dev/cli.sh | sh

sudo apt install ./KiroCrew-x86_64.deb     # Debian, Ubuntu
sudo dnf install ./KiroCrew-x86_64.rpm     # Fedora, RHEL, CentOS Stream, AL2023