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.
EGO-A-005 manual_review
extensions should not access the clipboard directly
Direct clipboard access via `St.Clipboard.get_default()` requires reviewer scrutiny.
Kiro Crew
shell/updates.js:269
St.Clipboard.get_default()
| 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 |
1. Move line 19 `lib/localBootstrap.js` to `LocalBootstrap` class. 2. Use `Soup` instead of curl (line 89 `lib/profiles.js`). 3. Extension cannot use sudo (line 96, 98 `lib/profiles.js`). 4. You cannot use ssh in extensions (line 107, 189 `lib/profiles.js`). 5. `lib/remote.js` is the next file to review: https://extensions.gnome.org/review/77214 6. Move line 16-17 `shell/client.js` to `GatewayClient`. 7. Please move the logic out of this extension to an app and don't ship it via the extension package. It should be a dependency of this extension and use d-bus to communicate: [D-Bus Guide](https://gjs.guide/guides/gio/dbus.html)