Command your own AI crew from the GNOME top bar. One glance tells you what every agent is doing — the ghost glows Kiro purple while they work, amber when one needs you, red when something breaks. Click to jump straight to the session that wants you. Your crew runs on YOUR machine via the local Kiro Crew gateway; this is the control panel. To reach a gateway on another machine, connect it in the Kiro Crew dashboard under Settings → Remote Crew — it opens and keeps that connection itself.
Note: Binary files aren't shown on the web site. To see all files, please download the extension zipfile.
| Version | Status |
|---|---|
| 0.1.7 (8) | Active |
| 0.1.6 (7) | Rejected |
| 0.1.5 (6) | Rejected |
| 0.1.4 (5) | Rejected |
| 0.1.3 (4) | Rejected |
| 0.1.2 (3) | Rejected |
| 0.1.1 (2) | Rejected |
| 0.1.0 (1) | Rejected |
A few notes to help the review: What it does: a top-bar indicator for a local "Kiro Crew" gateway (an HTTP/WebSocket service on 127.0.0.1). It shows aggregate agent status and offers start/stop/restart/update of that gateway via the gateway's own API or systemd D-Bus. Subprocess: the only subprocess is ssh, used to reach a gateway on another machine. It is spawned from an argv array (never a shell string), with the host passed after --, forwards bound to 127.0.0.1 only, and BatchMode=yes so it never waits on a password. The host is validated against a regex that cannot be read as an ssh option. No bundled binaries. Process separation: extension.js/shell/* import no Gtk/Adw/Gdk; prefs.js/prefs/* import no St/Clutter/Meta/Shell; shared lib/* import no UI at all. Everything created in enable() is torn down in disable(), and async work is cancelled via Gio.Cancellable. shell-version includes 51: GNOME 51 is a current stable release (shipped 2026-09-16). If a linter flags EGO-M-004 for "51", that is a false positive from a linter version predating GNOME 51, not a future-version claim. Happy to clarify or adjust anything. Thanks!
Kiro Crew