kirodotdev/KiroCrew

Kiro Crew is an open-source development workspace for agent-driven work that outlives a single chat. It runs a Gateway on hardware you control — a Mac, a container, or a remote host — and keeps sessions, memory, schedules and task checkpoints there while you interact from a desktop app, web dashboard, CLI, or messaging surfaces like Slack and Discord. It fits people who want multi-step coding tasks to continue unattended, and who accept maintaining the runtime and its sign-in themselves.

What changes in practice

The central claim is continuity. Instead of a conversation that ends when the window closes, each conversation or background task is a logical agent session managed by the Gateway. Sessions can be resumed after Gateway restarts and run concurrently; scheduled or reactive work continues without someone at the terminal. Long-running tasks are given a specification, then plan, execute, validate, retry on failure and resume from checkpoints — the README example is a migration plan that stops if tests fail.

Two mechanisms carry this. First, corrections and task failures become durable lessons that change later behavior; lessons can be global or limited to one repository via repo_scope. Repeated patterns can be synthesized into reusable skills that you inspect, edit or delete. Second, delegation fans work out to isolated subagents and merges results back into the parent conversation, which is useful for parallel research or option comparisons.

Work surfaces stay interchangeable: desktop app, dashboard, CLI, or connected messaging channels, without moving the agent runtime or its state. The dashboard exposes tool calls, subagent progress, context usage, approvals, memory and logs, so unattended runs remain inspectable. Extensions come through MCP servers, markdown skills and hooks rather than core changes.

Requirements per install path

The default agent runs on kiro-cli, which must be installed and signed in separately on the Gateway host; first launch checks for it and points to the official setup guide. Desktop builds are offered for macOS, Windows x64, and Linux x86_64/aarch64 in deb, rpm and AppImage formats, with Stable, Insider and Nightly channels; the Linux install guide covers package choice and sandbox setup. The one-line installer fetches a signed Stable wheel and serves the dashboard on localhost, with version pinning available only from 0.1.2 onward. Docker ships a multi-arch image for always-on servers.

Building from source on macOS and Linux needs Python 3.12+ and Node.js 22.12+ (24 LTS recommended). Windows uses a separate native source-install guide. Other verified ACP harnesses have their own prerequisites.

Control, data and telemetry

Approvals, OS isolation where available, sensitive-path and credential guards, deny rules, audit events and optional governance profiles sit at the runtime boundary. The dashboard binds to loopback by default; any remote exposure requires authenticated configuration, and the security model should be read before widening it. User data lives under ~/.kiro/crew unless KIROCREW_HOME redirects it.

Anonymous telemetry is on by default: one heartbeat per day with exactly five fields, plus event-based install receipts for official catalog apps, starting only after the privacy disclosure. It can be disabled in Settings, via kirocrew telemetry disable, or with KIROCREW_TELEMETRY_DISABLED; it is forced off in CI and when KIROCREW_HOME is non-default, and administrators can pin it off through a security policy. Prompts, responses, file contents, paths, repository names and credentials are stated as never sent.

The code is Apache-2.0 licensed, with attribution in NOTICE.

HotRepo's take

Tracking shows one dated daily-board observation: 4,653 stars with +19 stars on 2026-10-30 board history. That single sample says nothing about momentum in either direction; treat the project on its documented behavior, not its trending status.