{"full_name":"kirodotdev/KiroCrew","owner":"kirodotdev","name":"KiroCrew","shard":"1","url":"https://github.com/kirodotdev/KiroCrew","description":"A persistent workspace for development work that self-improves and continues beyond one session.","homepage":"https://kiro.dev/crew/","topics":["agent","agentic-ai","agents","kiro","ai-agent","ai-agents","automation","devtools","llm"],"tag_pages":["agent","agentic-ai","agents","ai-agent","ai-agents","automation","devtools","kiro","llm"],"language":"Python","license":"Apache-2.0","avatar":"https://avatars.githubusercontent.com/u/207925904?v=4","created_at":"2026-07-16T21:21:54Z","pushed_at":"2026-11-16T09:23:55Z","metrics":{"stars":4953,"forks":1046,"watchers":27,"issues":14629,"prs":23013,"releases":121,"issues_open":1867,"issues_closed":12762,"prs_open":756,"prs_closed":2944,"prs_merged":19313,"discussions":14},"growth":{"day":{"stars":9,"forks":3,"base_day":"2026-11-15"}},"history":{"dates":["2026-11-11","2026-11-12","2026-11-13","2026-11-14","2026-11-15","2026-11-16"],"stars":[4892,4912,4927,4937,4944,4953],"forks":[1015,1021,1027,1036,1043,1046],"watchers":[25,26,26,26,26,27],"issues_open":[1716,1770,1761,1870,1862,1867],"prs_open":[776,791,775,889,792,756]},"boards":{},"same_owner":[],"issues":[{"number":36565,"title":"Main ratchet drift detected","comments":69,"created_at":"2026-11-13T10:19:15Z"},{"number":36261,"title":"Flaky: test_ssrf_guard_fail_closed node subprocess tests time out on Linux shard 7","comments":22,"created_at":"2026-11-13T01:05:24Z"},{"number":22733,"title":"Nightly GUI user test FAIL: notifications-bell-sheet-open-close, notifications-center-empty-state, crewmate-chat-clean, crewmate-panel-tabs, settings-chat-toggle-show-timestamps, settings-security-docs-section, settings-security-layers-section","comments":22,"created_at":"2026-10-21T10:10:51Z"},{"number":20772,"title":"ux(members): I couldn't tell who wrote the replies: the bubbles have no avatar or name, and there's an…","comments":20,"created_at":"2026-10-15T10:05:07Z"},{"number":10871,"title":"Persist inbound images for the non-Slack channels; namespace the uploads directory per session","comments":16,"created_at":"2026-09-14T21:23:21Z"},{"number":22314,"title":"Flaky: E2E (stub ACP backend, offline) member-memory.spec V2-previews-concurrent-correction times out the gateway (-14)","comments":15,"created_at":"2026-10-19T22:36:00Z"},{"number":12800,"title":"ci: CodeBuild runner queue stalls head-of-line-block main (jobs wait hours for a runner; concurrency group holds every later push)","comments":15,"created_at":"2026-09-22T12:30:28Z"},{"number":9909,"title":"Expose memory and lessons context blocks to config: disable toggles and size caps","comments":15,"created_at":"2026-09-10T14:46:03Z"}],"discussions":[{"number":30504,"title":"Kiro Crew 0.12.0 removed in-app browser","comments":1,"category":"General","created_at":"2026-11-05T15:31:11Z"},{"number":17099,"title":"Neovim TUI for Kiro Crew","comments":0,"category":"Show and tell","created_at":"2026-10-05T18:44:47Z"},{"number":14808,"title":"Group-owned agent tasks: event-triggered, skill-based procedures with branching steps","comments":0,"category":"Ideas","created_at":"2026-09-28T19:45:30Z"},{"number":13785,"title":"Federated lesson-sharing between isolated crews (event replication, not a shared brain)","comments":6,"category":"Ideas","created_at":"2026-09-25T10:32:55Z"},{"number":13752,"title":"Change in version v0.7.1","comments":0,"category":"Q&A","created_at":"2026-09-25T08:11:57Z"},{"number":10836,"title":"Appetite for multi-principal collaboration (implementing Tenets 6 & 7)?","comments":2,"category":"Ideas","created_at":"2026-09-14T18:36:33Z"},{"number":7723,"title":"claude and codex support","comments":2,"category":"Q&A","created_at":"2026-09-01T20:40:17Z"},{"number":6126,"title":"Idea: a remote backend for `kirocrew pod` (run isolated instances off-box)","comments":0,"category":"Ideas","created_at":"2026-08-26T19:35:29Z"}],"latest_release":{"name":"v0.12.2","tag":"v0.12.2","published_at":"2026-11-12T06:52:52Z","body":"A second hot patch for 0.12.0, on top of 0.12.1: Kiro Crew no longer restarts a running gateway to install an update, chats keep their approvals, queued messages and streams straight under failures, and the KAS engine reads more of a kiro-cli agent spec. Slack, Teams, Telegram and Discord keep each turn's reply in the right place, and security, Windows, cloud crew and accessibility fixes land with them. The Decisions model card gains a SageMaker endpoint option.\n\n### Updates\n\nKiro Crew never restarts a running gateway to install an update. A new version downloads in the background, clicking Update only marks it for the next start, and the desktop app installs it when you quit. An install that was interrupted finishes at the next app start before the gateway starts, and the agent cannot write the record that arms an update.\n\n### Notable fixes\n\n**Chat and sessions.** An old approval answer no longer approves a later tool, approval cards stay answerable when a stop fails, and a streaming turn keeps running when its send fails late. A closed tab stays closed when its late save lands, a requeued message runs on its own row instead of a duplicate, a resume joins the agent already starting, and the reply that streamed before a compaction is kept. The agent greeting shows early, mermaid label images no longer load on render, and clicking a linked image opens only the viewer.\n\n**KAS engine.** A kiro-cli agent's `allowedCommands` patterns (`\\d`, `\\s`, `\\w`, `{n,m}` and Rust style expressions) and read `allowedPaths` are honoured at Crew's gate, shell allowlist grants survive a policy that pins built-in rules, and `trustedAgents` allows apply after every deny. An `mcp.json` `tools` allowlist and `useLegacyMcpJson` are read, a project agent file can switch a user-level MCP server off, a model pin the KAS model list does not offer is refused, a host with a too-old glibc is refused before the install begins, and a broken engine copy that kiro-cli left behind is moved aside once. Steering files that may be auto-included are sent by path instead of the whole tree, a runtime start no longer waits on an empty tree scan, spec hook context is sent again after a compaction, and Crew's MCP servers connect before the agent's own.\n\n**Claude and other harnesses.** A start that dies at once reports the real exit status, a failed kiro sign-in is reported as unfinished with a one click retry, and a kiro-cli engine the host cannot run is reported as such. A Kiro CLI that rejects `--auth-method` is told once to update, its out of date card lifts when config leaves the KAS relay, and KAS users reach the Kiro sign-in from the account popup, where a bare refusal names the start URL before the region. A Claude session that asks for auto approval keeps Crew's tools beside a foreign settings file, `cli.json` is kept whole when the gateway cannot read it, and Codex Crew servers carry the gateway instance environment.\n\n**MCP servers.** A user MCP server whose name contains a colon stays in the default agent spec, a Windows launcher is probed once whatever its spelling, a copied gateway entry drops its provenance records, and a dead pooled backend is named. The launch approval and settings cards of the MCP gateway behave, a KAS MCP sign-in is saved where KAS chats read it, a remote server's sign-in settings always reach the engine, and KAS says when it cannot sign in to a server with its own client. A KAS MCP server's launch reference is shared across sessions, and a conductor is told which of its worker's MCP servers failed.\n\n**Bots, crews and the work ledger.** The Bot editor, agent picker and roster get four fixes, a Bot whose memory database was deleted reopens, and a `.kirobot` file that starts with a byte-order mark imports. A new chat never suggests a Bot's home folder, a Bot chat outside its own thread is told to do the work itself, and the custom agents tab lists spec files it used to hide while reserving their names. A folder agent named like a Bot is ask","is_prerelease":false},"readme":true,"readme_zh":false,"news":[],"stale":false,"snapshot_at":"2026-11-16T09:23:14Z","history_start":"2026-09-06"}