5 phút đọc
kirodotdev/KiroCrew: A persistent workspace for development work that self-improves and continues beyond one se – Repository kirodotdev/KiroCrew. Mô tả: A persistent workspace for development work that self-improves and continues beyond one session.. 3318 stars, 395 forks, ngôn ngữ chính Python, cập nhật 2026-08-28.
1. Repository làm gì?
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
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. Every path runs on kiro-cli underneath, so the first launch installs it if needed and guides Kiro device-code sign-in.
The desktop app starts a bundled Gateway when no local Gateway is already running, updates itself on the channel you download, and can connect to a remote Gateway over an SSH tunnel. See the desktop app guide.
On Linux, start with the one-line install — it is the smoothest path, works on every distro and both architectures, and puts kirocrew on your PATH, which is what makes kirocrew service install (and the AppArmor profile the agent sandbox needs on Ubuntu 23.10+) reachable:
2. Dữ liệu và cấu trúc đáng chú ý
You then work in the dashboard at http://localhost:5476. Add a desktop package when you want what only the Electron shell gives you: an application-menu entry and icon, a native window, a taskbar badge, a system-wide hotkey, a Gateway that starts and stops with the app, and in-app updates. A .deb or .rpm installs to a fixed path under /opt, which is what lets it set the AppArmor profile up for you; the AppImage needs no root but needs FUSE and carries a manual sandbox step. uname -m prints which architecture you need.
The Linux desktop app needs glibc 2.34 or newer (Ubuntu 22.04+, Debian 12+, Fedora, CentOS Stream 9, Amazon Linux 2023). On an older host — Ubuntu 20.04, Debian 11, Amazon Linux 2 — use the one-line install above.
Every architecture below is a first-class lane: each gets its own build, its own auto-update feed, and its own SLSA provenance attestation.
Take Stable unless you have a reason not to — the table below says who each channel is for.
Every install path — desktop app, CLI, Docker image — offers the same three channels. Pick by how much churn you can absorb, not by version number:
Stable and Insider are two update lanes of the same app. The desktop app switches between them in Settings → About, a CLI install switches by re-running the installer with –channel, and a container switches by pulling a different tag. Either way, the other lane's current version then arrives as an ordinary update.
Nightly is a separate app with its own name and icon, so it installs alongside a Stable or Insider one rather than replacing it. It is not a sandbox, though: it reads the same ~/.kiro/crew data home unless you point it elsewhere with KIROCREW_HOME.
3. Khả năng ứng dụng và giới hạn
Running Insider or Nightly is a real contribution. When something looks wrong, please open an issue so it gets fixed before it reaches Stable.
Install the prebuilt, SHA-256-verified wheel from the release CDN without cloning the repository or running npm and a local build.
Track a faster channel, insider or nightly (see Release channels for who each one is for):
Experimental — run on a fully managed Python instead of the system one. The installer fetches a SHA-256-pinned uv and provisions a self-contained CPython 3.12 into ~/.kiro/crew-python, so the install never depends on (or breaks with) the system interpreter:
The choice is sticky: it is recorded next to the channel, so later re-runs of the installer — including the one kirocrew update performs — keep using the managed interpreter without the flag. Opt back out with –system-python.
Open http://localhost:5476 and start a conversation. The web dashboard works without messaging credentials. Add a messaging channel — Slack, Discord, Telegram, Teams, Webex, WeCom, WeChat, or WhatsApp — when you want to continue working with the same agent away from the dashboard. Apart from Teams (which needs a public HTTPS webhook — see its guide), these channels connect outbound, so you do not need to expose the dashboard port publicly.
For always-on servers, the Gateway ships as a public multi-arch image on GHCR:
See the Docker guide for first-run login, channel tags, and the container security model.
macOS and Linux require Python 3.10+, Node.js 22+ (24 LTS recommended), npm, and kiro-cli. The first desktop or dashboard launch can install Kiro CLI on the Gateway host and guide device-code sign-in before chat opens. Windows is supported through a native source install; follow the Windows guide instead of the shell steps below.
Số liệu repository có thể thay đổi; nên mở liên kết nguồn để kiểm tra README, giấy phép và trạng thái phát hành.
Nguồn tham khảo: Xem bài gốc
