48 of 51 criteria have a sourced finding; 46 were also cross-checked by a second agent. Every comparison that includes Kiro links here for scope, limitations, atomic answers and sources.
Humans approve the rubric, templates and prototype; they do not review every finding. An agent source cross-check is not a hands-on product test. A missing sourced finding is not evidence that a capability is absent.
The IDE supports macOS, Windows and listed modern Linux distributions; Crew has separate desktop support. Android is publicly distributed through Google Play on paid Kiro plans. iPhone remains limited invitation-only TestFlight early access. Crew also provides a phone-accessible HTTPS browser dashboard on a user-operated gateway.
Scope
Surfaces: Kiro CLI, Kiro Crew, Kiro IDE, Kiro mobile preview, Kiro Web · Version: Kiro Crew v0.12.2 (b6599234221cfc492c0dd95fdd53643e710c9f28) where named; managed Kiro cloud/mobile documentation checked 2026-11-13; no installed-product test. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
The scoped first-party source pass does not establish editor_extensions, notifications. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
9 atomic answers
Desktop os [supported] IDE supports macOS Intel/Apple Silicon, Windows 10/11 x64/ARM64 and listed modern Linux distributions; Crew has separate desktop support. Sources: kiro:nov07-installation.
Mobile apps [partial] Android is publicly distributed; iPhone remains invitation-only TestFlight early access and does not count as publicly available. Sources: kiro:facet38-mobile.
Browser [supported] Kiro Web uses a modern browser without local installation. Sources: kiro:nov07-installation.
Mobile browser [supported] Crew provides a phone-accessible HTTPS browser dashboard on the user-operated gateway. Sources: kiro:facet38-crew-phone.
Cli [supported] CLI supports macOS, Windows 11 PowerShell and Linux glibc 2.34+ or musl variants. Sources: kiro:nov07-installation.
Editor extensions [supported] Kiro for VS Code (Marketplace and Open VSX, local workspaces); JetBrains and Zed connect over ACP. Sources: kiro:b09-install, kiro:b09-vscode, kiro:b09-acp.
Task actions [supported] The mobile guide names starting and steering cloud sessions; the cloud sessions guide says Mobile can also review diffs and answer approval requests. Detailed mobile documentation is still marked coming soon. Sources: kiro:nov07-mobile, kiro:nov07-cloud.
Notifications [partial] IDE native OS notifications for agent events and 80% credit alerts; push on other surfaces was not found. Sources: kiro:b09-notify, kiro:b09-usage-notify.
Cross device continuity [supported] IDE, CLI, Web and Mobile can create, resume and steer the same cloud session, subject to the matrix and version minimums. Sources: kiro:nov07-cloud.
Crew 0.12 exposes a fixed registry of Kiro/KAS, Claude Code, Codex, OpenCode, Pi, Goose, DeepSeek, Strands and GitHub Copilot CLI backends. Developer Mode has been removed; non-Kiro backends remain experimental. New sessions choose a supported installed harness, and the runtime rejects arbitrary unknown backend IDs. Configured MCP tool commands are separate from coding-agent adapters.
Scope
Surfaces: Kiro IDE, Kiro CLI, Kiro Web, Kiro mobile preview, Kiro Crew · Version: Kiro Crew v0.12.2 (b6599234221cfc492c0dd95fdd53643e710c9f28) where named; managed Kiro cloud/mobile documentation checked 2026-11-13; no installed-product test. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
The scoped first-party source pass does not establish model_providers. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
5 atomic answers
Harnesses [supported] Crew 0.12 adds Strands and GitHub Copilot CLI to the existing Claude Code, Codex, OpenCode, Pi, Goose, DeepSeek and Kiro harness options; non-Kiro backends remain experimental. Sources: kiro:facet38-crew-release.
Model providers [supported] Auto routing or a chosen OpenAI, Anthropic, xAI or open-weight model on Kiro credits. Sources: kiro:b09-pricing.
Custom adapters [unsupported] The inspected runtime accepts only its fixed known-backend set and rejects arbitrary backend IDs. Edition registration exposes known adapters, while arbitrary MCP tool commands are not coding-harness adapters. Sources: kiro:facet38-harness-registry.
Session integration [supported] Backend is fixed when the session starts; compaction is supported for Codex and OpenCode. Sources: kiro:gap07-backends.
Mixed harness operation [partial] New Crew sessions can select different harnesses; observed simultaneous cross-harness operation was not tested. Sources: kiro:gap07-backends.
Crew external backends reuse their own native sign-ins and credential stores. Managed Kiro clients use Kiro sign-in and credits; using Kiro model access through third-party automation outside Kiro interfaces is restricted.
Scope
Surfaces: Kiro Crew, Kiro IDE, Kiro CLI, Kiro Web, Kiro mobile preview · Version: Kiro Crew v0.12.2 (b6599234221cfc492c0dd95fdd53643e710c9f28) where named; managed Kiro cloud/mobile documentation checked 2026-11-13; no installed-product test. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Crew external backends use their own native accounts; managed Kiro clients require Kiro sign-in and credit entitlement. The native-interface restriction does not assert that every Crew backend uses Kiro credentials. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
The scoped first-party source pass does not establish api_accounts, local_models, account_switching, vendor_account_requirement, provider_restrictions. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Agent subscriptions [supported] Crew runs Claude Code and Codex using each harness native sign-in and own credential store, reusing the external agent account independently of the Kiro account. Sources: kiro:facet38-native-auth.
Api accounts [unknown] Not established for api accounts in the named first-party source pass. Product access and scenario tests were not run.
Vendor credits [supported] The managed Kiro Agent backend uses the Kiro sign-in and Kiro credit entitlement; external backends have separate account routes. Sources: kiro:facet38-crew-release.
Local models [unknown] Not established for local models in the named first-party source pass. Product access and scenario tests were not run.
Account switching [unknown] Not established for account switching in the named first-party source pass. Product access and scenario tests were not run.
Vendor account requirement [supported] Kiro-native IDE, CLI, Web and Mobile require Kiro sign-in. Crew external-agent backends have the separate native account routes described above. Sources: kiro:b09-auth.
Provider restrictions [supported] Use through third-party automation harnesses outside Kiro's interfaces is not permitted. Sources: kiro:b09-pricing.
IDE installation requires sign-in and opening a project; measured setup time was not tested. Cloud provisioning clones selected GitHub/GitLab repositories server-side rather than uploading the local checkout. Further scoped facts are recorded in the atomic answers.
Scope
Surfaces: Kiro CLI, Kiro Crew, Kiro IDE, Kiro mobile preview, Kiro Web · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: local, managed-cloud, self-hosted · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Onboarding and project prerequisites: first-party sources in this pass did not establish no_git, local_git_without_remote, hosted_git, prerequisite_guidance. Detailed client actions, provider-specific eligibility and first-run prerequisites need targeted access; no install timing or external-tool fixture was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
7 atomic answers
First task setup [supported] IDE installation requires sign-in and opening a project; measured setup time was not tested. Sources: kiro:nov07-installation.
No git [partial] The IDE starts a session on an opened folder; Git is not named as a requirement. Sources: kiro:b09-install.
Local git without remote [partial] IDE and CLI open a local folder; docs do not require a remote. Sources: kiro:b09-install.
Hosted git [supported] Kiro Web works on GitHub repositories and GitLab projects. Sources: kiro:b09-github, kiro:b09-gitlab.
Prerequisite guidance [unknown] Not established for prerequisite guidance in the named first-party source pass. Product access and scenario tests were not run.
Managed cloud setup [supported] Cloud provisioning clones selected GitHub/GitLab repositories server-side rather than uploading the local checkout. Sources: kiro:nov07-cloud.
Byo vps onboarding [supported] Crew setup configures credentials and starts a Gateway dashboard; remote service installation needs the separate 24/7 guide. Sources: kiro:nov07-crew.
kiro-cli runs headless with a paid-plan API key; the Enterprise Management API is in preview; ACP connects clients.
Scope
Surfaces: Kiro IDE, Kiro CLI, Kiro Web, Kiro mobile preview · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Kiro CLI headless runs and cloud sessions; ACP connects first-party and compatible clients. The Enterprise policy-management API is an administrative service in preview and not publicly released; headless API keys require an eligible paid plan and managed-account enablement. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Api [partial] Enterprise Management API (16 policy operations) is in preview and not yet publicly released; ACP connects clients. Sources: kiro:b09-em-api, kiro:b09-acp.
Sdk [unknown] Not established for sdk in the named first-party source pass. Product access and scenario tests were not run.
Mcp server [unknown] Not established for mcp server in the named first-party source pass. Product access and scenario tests were not run.
Webhooks [unknown] Not established for webhooks in the named first-party source pass. Product access and scenario tests were not run.
Kiro documents MCP, project agent definitions and steering across IDE, CLI, Web and Mobile. Global agent selection and capability-rule editing have client-specific limits; admins can restrict MCP. Crew parity is unestablished.
Scope
Surfaces: Kiro IDE, Kiro CLI, Kiro Web, Kiro mobile preview · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Kiro-native clients, with client-specific MCP, custom-agent, instruction and permission controls. MCP tools work across these four clients; global custom agents and editable agent settings are IDE/CLI controls, while Web/Mobile use project-level definitions. No Crew parity is established here. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Web/Mobile MCP OAuth uses Powers; Mobile has no server-provided prompt/resource mention menu. Client-specific MCP capabilities are not uniform.
7 atomic answers
Mcp client [supported] MCP servers work on IDE, CLI, Web and Mobile. Sources: kiro:b09-mcp.
Plugins [supported] Powers package tools and knowledge activated on demand. Sources: kiro:b09-powers.
Custom tools [supported] Custom agent definitions select tools, permissions and context. Project agents load on IDE/CLI/Web/Mobile; primary-agent selection and editing are IDE/CLI controls, while Web/Mobile invoke project agents as subagents. Sources: kiro:b09-agents.
Authentication [unknown] Not established for authentication in the named first-party source pass. Product access and scenario tests were not run.
Permission scope [supported] IDE and CLI capability rules include MCP server/tool match patterns. Web separately uses sandbox tool approvals; identical permission interfaces across clients are not established. Sources: kiro:b09-perms.
Integration owner [supported] Admins can disable MCP or restrict it to an allow-listed registry. Sources: kiro:b09-governance.
The Kiro license page states that Chromium is the IDE’s underlying engine. Vendor license attribution explicitly names Chromium for IDE and Bun for CLI frontend; source implementation was not inspected.
Scope
Surfaces: Kiro IDE, Kiro CLI, Kiro Web, Kiro mobile preview, Kiro Crew · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Desktop implementation [supported] The Kiro license page states that Chromium is the IDE’s underlying engine. Sources: kiro:gap07-license.
Mobile implementation [unknown] Not established for mobile implementation in the named first-party source pass. Product access and scenario tests were not run.
Hybrids [supported] Every client speaks ACP to a standalone harness process, local or in a cloud sandbox. Sources: kiro:b09-how, kiro:b09-acp.
Implementation evidence [supported] Vendor license attribution explicitly names Chromium for IDE and Bun for CLI frontend; source implementation was not inspected. Sources: kiro:gap07-license.
Crew Projects accepts a prompt or uploaded Markdown specification for a task run. Task Runner persists its run projection and scheduling queue locally. Each concurrent task run has a collision-resistant task_id.
Scope
Surfaces: Kiro IDE, Kiro CLI, Kiro Web, Kiro mobile preview, Kiro Crew · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
A spec produces requirements.md or bugfix.md, design.md and tasks.md. Spec refinement produces Goal, Requirements and Acceptance Criteria. IDE Markdown Review and CLI phase checkpoints let users comment on planning documents. The runner converts the spec into ordered executable steps with commits and reviewer sessions. kirocrew run automatically resumes a saved checkpoint after restart.
Scope
Surfaces: Kiro CLI, Kiro IDE, Kiro Web · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
Unknown after the targeted first-party documentation, release and repository pass: revisions, amendment. No configured product fixture was run; documentation does not establish successful hands-on behavior.
7 atomic answers
Plans [supported] A spec produces requirements.md or bugfix.md, design.md and tasks.md. Sources: kiro:nov07-specs.
Editors [supported] IDE Markdown Review and CLI phase checkpoints let users comment on planning documents. Sources: kiro:nov07-specs.
Revisions [unknown] Not established for revisions in the named first-party source pass. Product access and scenario tests were not run.
Implementation links [supported] The runner converts the spec into ordered executable steps with commits and reviewer sessions. Sources: kiro:gap07-runner.
Amendment [unknown] Not established for amendment in the named first-party source pass. Product access and scenario tests were not run.
Restart persistence [supported] kirocrew run automatically resumes a saved checkpoint after restart. Sources: kiro:gap07-runner.
Steps can declare dependencies; independent tasks run in batches. Only ready steps without unmet cross-dependencies run in parallel batches. force_approval steps pause before execution even in YOLO mode.
Scope
Surfaces: Kiro CLI, Kiro IDE, Kiro Web · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Workflow-based answers depend on opt-in Workflows, which docs say are not yet available on every account (2026-11-22).
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Epics [unknown] Not established for epics in the named first-party source pass. Product access and scenario tests were not run.
Hierarchy [unknown] Not established for hierarchy in the named first-party source pass. Product access and scenario tests were not run.
Blockers [supported] Steps can declare dependencies; independent tasks run in batches. Sources: kiro:gap07-runner.
Readiness [supported] Only ready steps without unmet cross-dependencies run in parallel batches. Sources: kiro:gap07-runner.
Enforcement [supported] force_approval steps pause before execution even in YOLO mode. Sources: kiro:gap07-runner.
State propagation [unknown] Not established for state propagation in the named first-party source pass. Product access and scenario tests were not run.
Task to epic [unknown] Not established for task to epic in the named first-party source pass. Product access and scenario tests were not run.
Identity retention [unknown] Not established for identity retention in the named first-party source pass. Product access and scenario tests were not run.
Workspace .kiro/steering and AGENTS.md guide sessions; global local files do not automatically appear in cloud sandboxes. Kiro can retain learned commands, corrections and debugging insights across sessions when enabled. Local memories belong to the user account and are shared by IDE and CLI on the machine. Use-and-learn or read/write modes permit user-requested memory changes; read-only modes forbid writes. Read/write modes permit deleting memories; read-only modes do not. Memories can be refined during later work; automatic expiry is not established.
Scope
Surfaces: Kiro CLI, Kiro Crew, Kiro IDE, Kiro mobile preview, Kiro Web · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: local, self-hosted · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Instructions [supported] Workspace .kiro/steering and AGENTS.md guide sessions; global local files do not automatically appear in cloud sandboxes. Sources: kiro:nov07-steering.
Freshness [partial] Memories can be refined during later work; automatic expiry is not established. Sources: kiro:gap07-memory.
Takeover continuity [unknown] Not established for takeover continuity in the named first-party source pass. Product access and scenario tests were not run.
Steering files can carry product, technology and project-structure context; runtime architectural compliance was not tested. Requirements analysis finds cross-requirement contradictions and conflicting constraints. Analysis is optional and can be skipped; it is not a mandatory delivery gate.
Scope
Surfaces: Kiro CLI, Kiro IDE, Kiro mobile preview, Kiro Web · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Code search [unknown] Not established for code search in the named first-party source pass. Product access and scenario tests were not run.
Indexing [unknown] Not established for indexing in the named first-party source pass. Product access and scenario tests were not run.
External knowledge [supported] Steering files can carry product, technology and project-structure context; runtime architectural compliance was not tested. Sources: kiro:nov07-steering.
Multimodal inputs [unknown] Not established for multimodal inputs in the named first-party source pass. Product access and scenario tests were not run.
Freshness [unknown] Not established for freshness in the named first-party source pass. Product access and scenario tests were not run.
Crew Projects creates task runs from a prompt or uploaded spec. An interrupted run can resume with passed/skipped steps preserved. Run starts the task, while pause/cancel controls are available in its sidebar. A task run persists across fresh per-step sessions and reviewer sessions. Run records include task_id, step attempts, work directory and branch. Step states include PENDING, REVIEWING and PASSED; checkpointed progress survives restart.
Scope
Surfaces: Kiro Crew · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: local, self-hosted · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
Unknown after the targeted first-party documentation, release and repository pass: edit, discuss, prioritize, label, assign, search, filter, archive, project_epic_views, idea_parking, external_tracker_requirement. No configured product fixture was run; documentation does not establish successful hands-on behavior.
17 atomic answers
Create [supported] Crew Projects creates task runs from a prompt or uploaded spec. Sources: kiro:gap07-runner.
Edit [unknown] Not established for edit in the named first-party source pass. Product access and scenario tests were not run.
Discuss [unknown] Not established for discuss in the named first-party source pass. Product access and scenario tests were not run.
Prioritize [unknown] Not established for prioritize in the named first-party source pass. Product access and scenario tests were not run.
Label [unknown] Not established for label in the named first-party source pass. Product access and scenario tests were not run.
Assign [unknown] Not established for assign in the named first-party source pass. Product access and scenario tests were not run.
Search [unknown] Not established for search in the named first-party source pass. Product access and scenario tests were not run.
Filter [unknown] Not established for filter in the named first-party source pass. Product access and scenario tests were not run.
Archive [unknown] Not established for archive in the named first-party source pass. Product access and scenario tests were not run.
Reopen [supported] An interrupted run can resume with passed/skipped steps preserved. Sources: kiro:gap07-runner.
Project epic views [unknown] Not established for project epic views in the named first-party source pass. Product access and scenario tests were not run.
Idea parking [unknown] Not established for idea parking in the named first-party source pass. Product access and scenario tests were not run.
Explicit dispatch [supported] Run starts the task, while pause/cancel controls are available in its sidebar. Sources: kiro:gap07-runner.
Task session separation [supported] A task run persists across fresh per-step sessions and reviewer sessions. Sources: kiro:gap07-runner.
Metadata [supported] Run records include task_id, step attempts, work directory and branch. Sources: kiro:gap07-runner.
Durable states [supported] Step states include PENDING, REVIEWING and PASSED; checkpointed progress survives restart. Sources: kiro:gap07-runner.
External tracker requirement [unknown] Not established for external tracker requirement in the named first-party source pass. Product access and scenario tests were not run.
Task Runner injects the spec, working memory and prior Git state into each step. The runner decomposes the spec into steps with acceptance criteria and dependencies. Steps transition through REVIEWING to PASSED or retry/failure. Task steps declare dependencies for parallel execution. Passed steps create Git commits; reviewer sessions inspect actual diffs. The dashboard shows task progress, step status, approval buttons and pause/cancel controls.
Scope
Surfaces: Kiro IDE, Kiro CLI, Kiro Web, Kiro mobile preview, Kiro Crew · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
Unknown after the targeted first-party documentation, release and repository pass: shared_ids, update, claim, assign, children, attribution, permissions, conflicts. No configured product fixture was run; documentation does not establish successful hands-on behavior.
14 atomic answers
Shared ids [unknown] Not established for shared ids in the named first-party source pass. Product access and scenario tests were not run.
Read [supported] Task Runner injects the spec, working memory and prior Git state into each step. Sources: kiro:gap07-runner.
Create [supported] The runner decomposes the spec into steps with acceptance criteria and dependencies. Sources: kiro:gap07-runner.
Update [unknown] Not established for update in the named first-party source pass. Product access and scenario tests were not run.
Claim [unknown] Not established for claim in the named first-party source pass. Product access and scenario tests were not run.
Assign [unknown] Not established for assign in the named first-party source pass. Product access and scenario tests were not run.
State changes [supported] Steps transition through REVIEWING to PASSED or retry/failure. Sources: kiro:gap07-runner.
Feature specs persist requirements.md, design.md and tasks.md. Humans refine user stories, acceptance criteria, design and task priorities. Kiro generates and refines the specification documents. The Requirements-First workflow requests user confirmation before advancing phases. tasks.md contains executable implementation tasks derived from requirements/design. Analysis can be rerun after requirements edits; automatic implementation-to-spec drift enforcement was not established. Requirements analysis streams issues with suggested fixes and updates requirements.md from answers.
Scope
Surfaces: Kiro CLI, Kiro IDE, Kiro Web · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
Unknown after the targeted first-party documentation, release and repository pass: revisions, later_retrieval. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Later retrieval [unknown] Not established for later retrieval in the named first-party source pass. Product access and scenario tests were not run.
Drift detection [partial] Analysis can be rerun after requirements edits; automatic implementation-to-spec drift enforcement was not established. Sources: kiro:gap07-requirements-analysis.
Review integration [supported] Requirements analysis streams issues with suggested fixes and updates requirements.md from answers. Sources: kiro:gap07-requirements-analysis.
Spec task execution can run independent tasks in parallel on IDE, CLI and Web; the matrix excludes mobile. The guide permits up to ten concurrent cloud sessions.
Scope
Surfaces: Kiro CLI, Kiro IDE, Kiro mobile preview, Kiro Web · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Parallel work: first-party sources in this pass did not establish concurrent_sessions, observed_concurrency, status_visibility. No concurrent-worker, duplicate-claim, delegation-retention or twelve-state fleet fixture was run. UI labels alone do not establish enforcement.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
5 atomic answers
Concurrent sessions [supported] Up to 10 concurrent cloud sessions. Sources: kiro:b09-cloud.
Concurrent tasks [supported] Spec task execution can run independent tasks in parallel on IDE, CLI and Web; the matrix excludes mobile. Sources: kiro:nov07-specs.
Quotas [supported] The guide permits up to ten concurrent cloud sessions. Sources: kiro:nov07-cloud.
Observed concurrency [unknown] Not established for observed concurrency in the named first-party source pass. Product access and scenario tests were not run.
Status visibility [unknown] Not established for status visibility in the named first-party source pass. Product access and scenario tests were not run.
GitHub issues are assigned to the agent per user with write permission; the same issue assigned by two users creates two tasks.
Scope
Surfaces: Kiro Web · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Kiro Web GitHub-issue assignment with repository write permission; assignments are per user, and two users assigning the same issue create separate tasks. No general exclusive task lock is established. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
7 atomic answers
Human assignment [partial] Each user controls their own agent tasks; others cannot assign on their behalf. Sources: kiro:b09-github.
Agent assignment [supported] The kiro label or /kiro comment assigns a GitHub issue to the agent. Sources: kiro:b09-github.
Claims [unknown] Not established for claims in the named first-party source pass. Product access and scenario tests were not run.
Queues [unknown] Not established for queues in the named first-party source pass. Product access and scenario tests were not run.
Routing [unknown] Not established for routing in the named first-party source pass. Product access and scenario tests were not run.
Duplicate prevention [unsupported] If several users assign the same issue, Kiro creates a separate task for each. Sources: kiro:b09-github.
Ownership enforcement [supported] Assigning requires write permission on the repository. Sources: kiro:b09-github.
Kiro supports custom-agent subagents and opt-in Workflows in IDE, CLI and Web, with results returning to the parent. Crew separately spawns subagents and offers Experimental external-agent backends. Workflow controls differ by client and account enablement.
Scope
Surfaces: Kiro Crew, Kiro IDE, Kiro CLI, Kiro Web · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Native custom-agent subagents and opt-in Workflows in IDE, CLI and Web; Workflows are not yet enabled on every account. Crew orchestration and Experimental third-party backends are separate scopes; no Mobile Workflows parity is established. · OS: Not specified · Execution modes: local, self-hosted, managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Inspectable delegation and communication: first-party sources in this pass did not establish roles, model_harness_effort, messages, results_return, cross_harness, activation, authentication, live_progress, retained_results, followup, invocation. No concurrent-worker, duplicate-claim, delegation-retention or twelve-state fleet fixture was run. UI labels alone do not establish enforcement.
Workflow-based answers depend on opt-in Workflows, which docs say are not yet available on every account (2026-11-22).
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Model harness effort [supported] Workflow steps can set custom agents, models and effort. These Workflow features are opt-in in IDE, CLI and Web and are not yet available on every account; Mobile parity is unestablished. Sources: kiro:b09-workflows.
Messages [unknown] Not established for messages in the named first-party source pass. Product access and scenario tests were not run.
Results return [supported] Workflow results return to the parent session. These Workflow features are opt-in in IDE, CLI and Web and are not yet available on every account; Mobile parity is unestablished. Sources: kiro:b09-cloud, kiro:b09-workflows.
Cross harness [partial] Crew sessions can run Claude Code, Codex, OpenCode and other backends, marked Experimental. Sources: kiro:b09-backends.
Orchestration owner [supported] Crew separately spawns isolated subagents and synthesizes their results; native Kiro subagent and Workflow behavior is established by the other cited, client-specific atoms. Sources: kiro:nov07-crew.
Activation [unknown] Not established for activation in the named first-party source pass. Product access and scenario tests were not run.
Authentication [unknown] Not established for authentication in the named first-party source pass. Product access and scenario tests were not run.
Live progress [supported] Running step sessions can be paused, resumed or steered; progress returns to the parent. These Workflow features are opt-in in IDE, CLI and Web and are not yet available on every account; Mobile parity is unestablished. Sources: kiro:b09-workflows, kiro:b09-cloud.
Retained results [unknown] Not established for retained results in the named first-party source pass. Product access and scenario tests were not run.
Followup [supported] Workflow step sessions can be revisited with follow-up questions (opt-in Workflows). Sources: kiro:b09-workflows.
Invocation [unknown] Not established for invocation in the named first-party source pass. Product access and scenario tests were not run.
Crew Schedule creates recurring jobs in separate sessions; continued execution depends on its Gateway host.
Scope
Surfaces: Kiro Crew, Kiro Web · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: local, managed-cloud, self-hosted · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Unattended triggers: first-party sources in this pass did not establish events, recurring_tasks, completion_conditions, scheduler_location, overlaps, retries, client_independence. No concurrent-worker, duplicate-claim, delegation-retention or twelve-state fleet fixture was run. UI labels alone do not establish enforcement.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
8 atomic answers
Schedules [supported] Crew Schedule creates recurring jobs in separate sessions; continued execution depends on its Gateway host. Sources: kiro:nov07-crew.
Events [supported] Hooks fire on file, prompt, stop and tool events; the GitHub kiro label starts work. Sources: kiro:b09-hooks, kiro:b09-github.
Recurring tasks [supported] Scheduled tasks can be edited, disabled and re-enabled. Sources: kiro:b09-schedule.
Completion conditions [unknown] Not established for completion conditions in the named first-party source pass. Product access and scenario tests were not run.
Scheduler location [supported] Web schedules run in Kiro's cloud; Crew schedules run on the user's own host. Sources: kiro:b09-schedule, kiro:b09-crew.
Overlaps [unknown] Not established for overlaps in the named first-party source pass. Product access and scenario tests were not run.
Retries [unknown] Not established for retries in the named first-party source pass. Product access and scenario tests were not run.
Client independence [supported] Web scheduled tasks run without a session being started or a client attached. Sources: kiro:b09-schedule.
Approvals requested with no client attached wait for the next attaching client.
Scope
Surfaces: Kiro CLI, Kiro IDE, Kiro mobile preview, Kiro Web · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Cloud-session resumption and steering span the named native clients; Workflow pause/resume is documented only in IDE, CLI and Web, is opt-in and is not enabled on every account. Mobile Workflow controls remain unestablished. · OS: Not specified · Execution modes: local, managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Intervention and attention: first-party sources in this pass did not establish pause, stop, resume, steer, notifications, escalation, visible_errors, chat_terminal_parity, retained_history. No concurrent-worker, duplicate-claim, delegation-retention or twelve-state fleet fixture was run. UI labels alone do not establish enforcement.
Workflow-based answers depend on opt-in Workflows, which docs say are not yet available on every account (2026-11-22).
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Pause [supported] Opt-in Workflows in IDE, CLI and Web support pausing and resuming step sessions, when enabled for the account. Mobile Workflow controls are not established here. Sources: kiro:b09-workflows.
Stop [unknown] Not established for stop in the named first-party source pass. Product access and scenario tests were not run.
Resume [supported] Reattach to a cloud session from any surface and resume. Sources: kiro:b09-cloud.
Steer [supported] Steer a cloud session from IDE, CLI, Web or Mobile. Sources: kiro:b09-cloud.
Pending decisions [supported] Approvals requested with no client attached wait for the next attaching client. Sources: kiro:nov07-cloud.
Escalation [unknown] Not established for escalation in the named first-party source pass. Product access and scenario tests were not run.
Visible errors [unknown] Not established for visible errors in the named first-party source pass. Product access and scenario tests were not run.
Chat terminal parity [unknown] Not established for chat terminal parity in the named first-party source pass. Product access and scenario tests were not run.
Retained history [supported] The transcript replays on reattach. Sources: kiro:b09-cloud.
Default chat for quick tasks, custom agents, prompt-generated or recipe workflows (opt-in) and mid-session autonomy changes.
Scope
Surfaces: Kiro IDE, Kiro CLI, Kiro Web · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Web collaborative/autonomous chat plus opt-in Workflows in IDE, CLI and Web, with different launch and interaction controls. Workflows are not yet enabled on every account; no Mobile or Crew workflow parity is established. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Workflow-based answers depend on opt-in Workflows, which docs say are not yet available on every account (2026-11-22).
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
10 atomic answers
Quick task [supported] Kiro Web's default mode is a collaborative chat. Sources: kiro:b09-web.
Growing epic [unknown] Not established for growing epic in the named first-party source pass. Product access and scenario tests were not run.
Presets [supported] Shipped recipes: investigate, feature-pipeline and publish-pr. Sources: kiro:b09-workflows.
Natural language [supported] Kiro generates a workflow from a prompt and asks for approval first. Sources: kiro:b09-workflows.
In run changes [supported] Toggle autonomous mode at any point in a Web session; steer running workflow steps. Sources: kiro:b09-autonomous, kiro:b09-workflows.
Live roles [unknown] Not established for live roles in the named first-party source pass. Product access and scenario tests were not run.
Retained relationships [unknown] Not established for retained relationships in the named first-party source pass. Product access and scenario tests were not run.
Discoverability [unknown] Not established for discoverability in the named first-party source pass. Product access and scenario tests were not run.
Auth friction [unknown] Not established for auth friction in the named first-party source pass. Product access and scenario tests were not run.
Crew runs on the user's machine, container or controlled remote host; the desktop app can connect through an SSH tunnel. Managed cloud sessions run in isolated Kiro sandboxes in the profile Region (us-east-1 or eu-central-1); a paid Pro-family plan and some organization enablement are required. Further scoped facts are recorded in the atomic answers.
Scope
Surfaces: Kiro CLI, Kiro Crew, Kiro IDE, Kiro mobile preview, Kiro Web · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: local, managed-cloud, self-hosted · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Laptop-independent execution: first-party sources in this pass did not establish local, byo_remote, hybrid, provisioning, payer, resources, region, expiry, other_device_continuation. No client-disconnect, crash/restart, resource-pressure or invoice-reconciliation fixture was run. Documented persistence is distinct from measured recovery.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Byo remote [supported] Crew runs on remote hosts, EC2 or Fargate (opt-in preview). Sources: kiro:b09-multi, kiro:b09-crew.
Self hosted [supported] Crew runs on the user's machine, container or controlled remote host; the desktop app can connect through an SSH tunnel. Sources: kiro:nov07-crew.
Managed cloud [supported] Managed cloud sessions run in isolated Kiro sandboxes in the profile Region (us-east-1 or eu-central-1); a paid Pro-family plan and some organization enablement are required. Sources: kiro:nov07-cloud, kiro:b09-cloud.
Hybrid [supported] IDE and CLI create and attach to cloud sessions. Sources: kiro:b09-cloud.
Provisioning [unknown] Not established for provisioning in the named first-party source pass. Product access and scenario tests were not run.
Payer [supported] Cloud sessions are included in the plan with no separate compute charge. Sources: kiro:b09-cloud.
Resources [unknown] Not established for resources in the named first-party source pass. Product access and scenario tests were not run.
Region [supported] Cloud sessions run in the profile Region (us-east-1 or eu-central-1); individual content is stored in us-east-1. Sources: kiro:b09-cloud, kiro:b09-dataprot.
Expiry [unknown] Not established for expiry in the named first-party source pass. Product access and scenario tests were not run.
Client disconnect [supported] Disconnecting a client does not stop an in-flight cloud task according to the guide. Sources: kiro:nov07-cloud.
Other device continuation [supported] Resume a cloud session from Mobile, Web, IDE or CLI. Sources: kiro:b09-cloud, kiro:b09-mobile.
Each task uses its own kirocrew/task/ branch. Existing repositories get a separate Git worktree per task run. Crew documents a Docker container runtime with its own persistent volumes and optional inner sandbox. IDE 1.3+ and local V3 CLI 2.31+ have an optional OS command sandbox, off by default; built-in file tools and remote MCP remain outside it. Worktree-based task runs leave the original checkout untouched. Managed cloud sessions execute the same Kiro harness inside a cloud VM. This is a documented architecture claim, not a containment test.
Scope
Surfaces: Kiro Crew, Kiro CLI, Kiro IDE, Kiro Web, Kiro mobile preview · Version: Kiro Crew v0.12.2 (b6599234221cfc492c0dd95fdd53643e710c9f28) where named; managed Kiro cloud/mobile documentation checked 2026-11-13; no installed-product test. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Separate scopes: Crew branches/worktrees/container runtime, optional local IDE/CLI OS command sandbox, and managed cloud VM/network/secret settings. These do not establish identical containment or controls across clients. · OS: Not specified · Execution modes: local, self-hosted, managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
The scoped first-party source pass does not establish checkout, filesystem, process, network, secrets, security_boundary. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Checkout [unknown] Not established for checkout in the named first-party source pass. Product access and scenario tests were not run.
Branch [supported] Each task uses its own kirocrew/task/ branch. Sources: kiro:gap07-runner.
Worktree [supported] Existing repositories get a separate Git worktree per task run. Sources: kiro:gap07-runner.
Container [supported] Crew documents a Docker container runtime with its own persistent volumes and optional inner sandbox. Sources: kiro:gap07-crew-hosting.
Vm [supported] Managed cloud sessions execute the same Kiro harness inside a cloud VM. This is a documented architecture claim, not a containment test. Sources: kiro:facet38-cloud-vm.
Os sandbox [supported] IDE 1.3+ and local V3 CLI 2.31+ have an optional OS command sandbox, off by default; built-in file tools and remote MCP remain outside it. Sources: kiro:nov07-sandbox.
Filesystem [unknown] Not established for filesystem in the named first-party source pass. Product access and scenario tests were not run.
Process [unknown] Not established for process in the named first-party source pass. Product access and scenario tests were not run.
Network [supported] Kiro Web sandbox network levels and a custom domain allow-list; this does not establish the same network controls on every local or Crew client. Sources: kiro:b09-net.
Secrets [partial] Kiro Web exposes encrypted sandbox secrets as environment variables and warns about exfiltration. Separately, Crew masks credential paths; these are different boundaries. Sources: kiro:b09-envvars, kiro:b09-crew-sec.
Code separation [supported] Worktree-based task runs leave the original checkout untouched. Sources: kiro:gap07-runner.
Security boundary [unknown] Not established for security boundary in the named first-party source pass. Product access and scenario tests were not run.
Task Runner reconciles interrupted steps after a Gateway restart. Git-coordinated runs resume automatically from checkpoints after Gateway restart. Cloud conversation, bound repositories and sandbox file state persist independently of the client and replay on reattachment. Passed/skipped steps are retained; unfinished safe steps get a new attempt. Runs without Git/idempotency safeguards reopen paused with an unknown-side-effect notice. Humans inspect external state before resuming unsafe interrupted runs.
Scope
Surfaces: Kiro CLI, Kiro Crew, Kiro IDE, Kiro mobile preview, Kiro Web · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: local, managed-cloud, self-hosted · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Client disconnect [supported] Disconnecting a client doesn't stop the agent; in-flight tasks keep running. Sources: kiro:b09-cloud.
Worker crash [supported] Task Runner reconciles interrupted steps after a Gateway restart. Sources: kiro:gap07-runner.
Service restart [supported] Git-coordinated runs resume automatically from checkpoints after Gateway restart. Sources: kiro:gap07-runner.
Expiry [unknown] Not established for expiry in the named first-party source pass. Product access and scenario tests were not run.
Transcript reload [supported] Cloud conversation, bound repositories and sandbox file state persist independently of the client and replay on reattachment. Sources: kiro:nov07-cloud.
Process reconnect [unknown] Not established for process reconnect in the named first-party source pass. Product access and scenario tests were not run.
Task resume [supported] Resume cloud sessions from /sessions or --resume-id. Sources: kiro:b09-cl30, kiro:b09-cloud.
State reconstruction [supported] Passed/skipped steps are retained; unfinished safe steps get a new attempt. Sources: kiro:gap07-runner.
Context loss [unknown] Not established for context loss in the named first-party source pass. Product access and scenario tests were not run.
Duplicate actions [partial] Runs without Git/idempotency safeguards reopen paused with an unknown-side-effect notice. Sources: kiro:gap07-runner.
Manual repair [supported] Humans inspect external state before resuming unsafe interrupted runs. Sources: kiro:gap07-runner.
Multi day continuity [partial] Sandbox file state persists with the session until it is deleted. Sources: kiro:b09-sandbox.
Kiro Web sandboxes auto-configure from manifests and take environment variables and secrets.
Scope
Surfaces: Kiro Web · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Kiro Web cloud sandbox setup from repository manifests, with environment variables and encrypted secrets. These findings do not establish local IDE/CLI setup parity. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
10 atomic answers
Dependencies [supported] The Web sandbox auto-configures from project manifests. Sources: kiro:b09-envconf.
Caches [unknown] Not established for caches in the named first-party source pass. Product access and scenario tests were not run.
Snapshots [unknown] Not established for snapshots in the named first-party source pass. Product access and scenario tests were not run.
Services [unknown] Not established for services in the named first-party source pass. Product access and scenario tests were not run.
Ports [unknown] Not established for ports in the named first-party source pass. Product access and scenario tests were not run.
Secrets [supported] Sandbox environment variables and encrypted secrets. Sources: kiro:b09-envvars.
Duplicate installs [unknown] Not established for duplicate installs in the named first-party source pass. Product access and scenario tests were not run.
Collisions [unknown] Not established for collisions in the named first-party source pass. Product access and scenario tests were not run.
kirocrew run --timeout sets a run timeout. Each step allows three logic/test retries, two crash recoveries and two replans. The runner caps total tasks including replans at fifty and detects repeated-error loops.
Scope
Surfaces: Kiro IDE, Kiro CLI, Kiro Web, Kiro mobile preview, Kiro Crew · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Time limits [supported] kirocrew run --timeout sets a run timeout. Sources: kiro:gap07-runner.
Turn limits [unknown] Not established for turn limits in the named first-party source pass. Product access and scenario tests were not run.
Token limits [unknown] Not established for token limits in the named first-party source pass. Product access and scenario tests were not run.
Spend limits [supported] Credit pool limits per user, group and profile. Sources: kiro:b09-pooling.
Timeouts [unknown] Not established for timeouts in the named first-party source pass. Product access and scenario tests were not run.
Retries [supported] Each step allows three logic/test retries, two crash recoveries and two replans. Sources: kiro:gap07-runner.
Provider failures [unknown] Not established for provider failures in the named first-party source pass. Product access and scenario tests were not run.
Enforcement [supported] The runner caps total tasks including replans at fifty and detects repeated-error loops. Sources: kiro:gap07-runner.
Enterprise prompt logs and per-user activity exports; Web marks auto-approved and blocked tool calls.
Scope
Surfaces: Kiro IDE, Kiro CLI, Kiro Web · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Enterprise/admin prompt logs for IDE and CLI and per-user activity exports; separately, Web tool-call approval markers. A control documented on one client is not attributed to every client. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
13 atomic answers
Logs [partial] Enterprise prompt logs cover IDE and CLI. Sources: kiro:b09-promptlog.
Traces [unknown] Not established for traces in the named first-party source pass. Product access and scenario tests were not run.
Failure reasons [unknown] Not established for failure reasons in the named first-party source pass. Product access and scenario tests were not run.
Task stats [unknown] Not established for task stats in the named first-party source pass. Product access and scenario tests were not run.
Agent stats [unknown] Not established for agent stats in the named first-party source pass. Product access and scenario tests were not run.
Project stats [unknown] Not established for project stats in the named first-party source pass. Product access and scenario tests were not run.
Time stats [unknown] Not established for time stats in the named first-party source pass. Product access and scenario tests were not run.
Failure status [unknown] Not established for failure status in the named first-party source pass. Product access and scenario tests were not run.
Approval status [supported] With Approve for me, Web marks approved tool calls and shows reasons for blocked ones. Sources: kiro:b09-perms.
Reconnect consistency [unknown] Not established for reconnect consistency in the named first-party source pass. Product access and scenario tests were not run.
Performance method [unknown] Not established for performance method in the named first-party source pass. Product access and scenario tests were not run.
Responsiveness [unknown] Not established for responsiveness in the named first-party source pass. Product access and scenario tests were not run.
The account dashboard updates credit usage at least every five minutes; pooled admin usage has separate dashboards.
Scope
Surfaces: Kiro CLI, Kiro Crew, Kiro IDE, Kiro mobile preview, Kiro Web · Version: Kiro CLI 3.1.0+ (changelog retrieved 2026-11-12). Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Per-task API and compute cost: first-party sources in this pass did not establish task_cost, child_cost, epic_cost, harness_aggregation, billed_vs_estimated, tokens, subscription_allowance, provider_reconciliation, compute_cost, alerts, export, drilldown. No client-disconnect, crash/restart, resource-pressure or invoice-reconciliation fixture was run. Documented persistence is distinct from measured recovery.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
14 atomic answers
Task cost [unknown] Not established for task cost in the named first-party source pass. Product access and scenario tests were not run.
Session cost [supported] Since CLI 3.1.0 (Nov 5, 2026) /usage shows the credits the current session has used. Sources: kiro:nov12-changelog.
Child cost [unknown] Not established for child cost in the named first-party source pass. Product access and scenario tests were not run.
Epic cost [unknown] Not established for epic cost in the named first-party source pass. Product access and scenario tests were not run.
Harness aggregation [unknown] Not established for harness aggregation in the named first-party source pass. Product access and scenario tests were not run.
Billed vs estimated [unknown] Not established for billed vs estimated in the named first-party source pass. Product access and scenario tests were not run.
Tokens [unknown] Not established for tokens in the named first-party source pass. Product access and scenario tests were not run.
Subscription allowance [supported] Credits included per plan. Sources: kiro:b09-pricing.
Provider reconciliation [unknown] Not established for provider reconciliation in the named first-party source pass. Product access and scenario tests were not run.
Compute cost [supported] No separate cloud compute charge. Sources: kiro:b09-cloud.
Refresh delay [supported] The account dashboard updates credit usage at least every five minutes; pooled admin usage has separate dashboards. Sources: kiro:nov07-pricing.
Alerts [supported] Low-resource notification at 80% of monthly credits. Sources: kiro:b09-usage-notify.
Export [supported] User activity exports include credit use. Sources: kiro:b09-activity.
Drilldown [unknown] Not established for drilldown in the named first-party source pass. Product access and scenario tests were not run.
Crew allows three concurrent task runs and parallel batches of three independent steps. The shared scheduling queue is persisted in tasks.db. CLI or dashboard can cancel a specific task or all tasks. Interrupted steps are reconciled against the Gateway incarnation and retry safety.
Scope
Surfaces: Kiro IDE, Kiro CLI, Kiro Web, Kiro mobile preview, Kiro Crew · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Concurrency [supported] Crew allows three concurrent task runs and parallel batches of three independent steps. Sources: kiro:gap07-runner.
Queues [supported] The shared scheduling queue is persisted in tasks.db. Sources: kiro:gap07-runner.
Cpu ram [unknown] Not established for cpu ram in the named first-party source pass. Product access and scenario tests were not run.
Backpressure [unknown] Not established for backpressure in the named first-party source pass. Product access and scenario tests were not run.
Host awareness [unknown] Not established for host awareness in the named first-party source pass. Product access and scenario tests were not run.
Check reuse [unknown] Not established for check reuse in the named first-party source pass. Product access and scenario tests were not run.
Check deduplication [unknown] Not established for check deduplication in the named first-party source pass. Product access and scenario tests were not run.
Bounded tests [unknown] Not established for bounded tests in the named first-party source pass. Product access and scenario tests were not run.
Cancellation [supported] CLI or dashboard can cancel a specific task or all tasks. Sources: kiro:gap07-runner.
Fairness [unknown] Not established for fairness in the named first-party source pass. Product access and scenario tests were not run.
Recovery [supported] Interrupted steps are reconciled against the Gateway incarnation and retry safety. Sources: kiro:gap07-runner.
Shared limits [supported] Credit pools share credits across seats with per-user caps. Sources: kiro:b09-pooling.
Crew 0.12 ships opt-in Shared Crew collaboration: owners can admit distinct people over Tailscale, and the source records their prompts and presence in the same session. This does not establish multiplayer for the managed IDE/Web cloud session.
Scope
Surfaces: Kiro Crew · Version: Kiro Crew v0.12.2 (b6599234221cfc492c0dd95fdd53643e710c9f28) where named; managed Kiro cloud/mobile documentation checked 2026-11-13; no installed-product test · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-13 (9 days old)
Agent cross-check
Not separately cross-checked
The scoped first-party source pass does not establish visibility, discussion, comments, ordering, conflicts, plan_restrictions, owner_online. No hands-on scenario was run.
11 atomic answers
Visibility [unknown] Not established for visibility in the named first-party source pass. Product access and scenario tests were not run.
Discussion [unknown] Not established for discussion in the named first-party source pass. Product access and scenario tests were not run.
Comments [unknown] Not established for comments in the named first-party source pass. Product access and scenario tests were not run.
Presence [supported] Shared Crew tracks distinct principals viewing or typing in one session, folding tabs of one principal together. Sources: kiro:facet38-shared-crew.
Coprompting [supported] Distinct verified Shared Crew principals can submit prompts to the same session, with author attribution and send admission. Sources: kiro:facet38-shared-crew.
Ordering [unknown] Not established for ordering in the named first-party source pass. Product access and scenario tests were not run.
Conflicts [unknown] Not established for conflicts in the named first-party source pass. Product access and scenario tests were not run.
Attribution [supported] Prompts carry the verified actor, and sender labels distinguish multiple people in the same conversation. Sources: kiro:facet38-shared-crew.
Permissions [partial] The owner enables the released Shared Crew preview and admits people through Tailscale; admitted people initially have equal access. Sources: kiro:facet38-crew-release.
Plan restrictions [unknown] Not established for plan restrictions in the named first-party source pass. Product access and scenario tests were not run.
Owner online [unknown] Not established for owner online in the named first-party source pass. Product access and scenario tests were not run.
Organization sign-in supports IAM Identity Center or external IdP such as Okta and Microsoft Entra. Organization-managed access uses its admin-provided start URL/region or external identity-provider flow. Kiro organizations distinguish administrators managing assigned users, groups and credit limits from members consuming pooled credits.
Scope
Surfaces: Kiro IDE, Kiro CLI, Kiro Web, Kiro mobile preview, Kiro Crew · Version: Kiro Crew v0.12.2 (b6599234221cfc492c0dd95fdd53643e710c9f28) where named; managed Kiro cloud/mobile documentation checked 2026-11-13; no installed-product test · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
Not separately cross-checked
The scoped first-party source pass does not establish project_roles, task_roles, membership, provisioning, unauthorized_access, revocation. No hands-on scenario was run.
9 atomic answers
Organization roles [supported] Kiro organizations distinguish administrators managing assigned users, groups and credit limits from members consuming pooled credits. Sources: kiro:facet38-team-admin.
Project roles [unknown] Not established for project roles in the named first-party source pass. Product access and scenario tests were not run.
Task roles [unknown] Not established for task roles in the named first-party source pass. Product access and scenario tests were not run.
Membership [unknown] Not established for membership in the named first-party source pass. Product access and scenario tests were not run.
Sso [supported] Organization sign-in supports IAM Identity Center or external IdP such as Okta and Microsoft Entra. Sources: kiro:gap07-auth.
Provisioning [unknown] Not established for provisioning in the named first-party source pass. Product access and scenario tests were not run.
Unauthorized access [unknown] Not established for unauthorized access in the named first-party source pass. Product access and scenario tests were not run.
Revocation [unknown] Not established for revocation in the named first-party source pass. Product access and scenario tests were not run.
Plan scope [supported] Organization-managed access uses its admin-provided start URL/region or external identity-provider flow. Sources: kiro:gap07-auth.
Spec force_approval gates can protect deployment/publish steps. The task pauses and shows Approve/Deny controls before a forced-approval step. A forced approval gate can be denied in the dashboard. Supervised mode is a review workflow, not a sandbox or access boundary; protected paths and command permissions are separate. The sandbox is separate from command permissions and cloud sandboxing, with platform prerequisites and configurable network modes. Claude Code tools preapproved in Claude settings can bypass Crew approval, deny and audit observation. Codex refuses to start with Crew sandbox off.
Scope
Surfaces: Kiro Crew, Kiro CLI, Kiro IDE, Kiro Web · Version: Kiro IDE 1.4.154 / CLI 3.2.1 (changelog retrieved 2026-11-12). Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Crew approval gates and harness-specific exceptions, local IDE/CLI capability rules, Web sandbox controls and the separately documented Enterprise Management preview. The sources do not establish one identical enforcement interface across clients. · OS: Not specified · Execution modes: local, self-hosted, managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Command [supported] IDE and CLI shell capability rules match command prefixes; Web sandbox permissions are a separate client scope. Sources: kiro:b09-perms.
Tool [supported] IDE and CLI per-capability deny, ask or allow rules; Web uses the separately documented sandbox approval behavior. Sources: kiro:b09-perms.
Network [supported] Kiro Web sandbox network levels and allow-lists; local OS sandbox network modes retain their own documented scope. Sources: kiro:b09-net.
Secret [unknown] Not established for secret in the named first-party source pass. Product access and scenario tests were not run.
Approver identity [unknown] Not established for approver identity in the named first-party source pass. Product access and scenario tests were not run.
Lifetime [unknown] Not established for lifetime in the named first-party source pass. Product access and scenario tests were not run.
Allow [supported] The task pauses and shows Approve/Deny controls before a forced-approval step. Sources: kiro:gap07-runner.
Deny [supported] A forced approval gate can be denied in the dashboard. Sources: kiro:gap07-runner.
Revoke [unknown] Not established for revoke in the named first-party source pass. Product access and scenario tests were not run.
Tunnels [unknown] Not established for tunnels in the named first-party source pass. Product access and scenario tests were not run.
Defaults [supported] Supervised mode is a review workflow, not a sandbox or access boundary; protected paths and command permissions are separate. Sources: kiro:nov07-security.
Safer modes [supported] The sandbox is separate from command permissions and cloud sandboxing; IDE 1.4.154 adds a permission-mode menu (Supervised, Accept file changes, Approve for me) and Kiro Web has model-based Approve for me. Sources: kiro:nov07-sandbox, kiro:nov12-changelog.
Enforcement [partial] Claude Code tools preapproved in Claude settings can bypass Crew approval, deny and audit observation; Codex refuses to start with Crew sandbox off. Enterprise Management (preview, new US East profiles) sets one policy across IDE, CLI, Web and Crew LTS; enforcement was not tested. Sources: kiro:gap07-backends, kiro:nov12-changelog.
Cloud session history persists in the session store, IDE chats export, and Crew logs security decisions.
Scope
Surfaces: Kiro IDE, Kiro CLI, Kiro Web, Kiro mobile preview, Kiro Crew · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Separate findings: shared cloud-session storage for native clients, IDE-only chat export, and the documented Crew security decision log. This does not establish cross-user audit integrity, retention guarantees or per-client export parity. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
11 atomic answers
Actions [supported] Crew's security event log records every decision. Sources: kiro:b09-crew-sec.
Approvals [unknown] Not established for approvals in the named first-party source pass. Product access and scenario tests were not run.
Edits [unknown] Not established for edits in the named first-party source pass. Product access and scenario tests were not run.
Discussion [unknown] Not established for discussion in the named first-party source pass. Product access and scenario tests were not run.
Decisions [unknown] Not established for decisions in the named first-party source pass. Product access and scenario tests were not run.
Cross user persistence [unknown] Not established for cross user persistence in the named first-party source pass. Product access and scenario tests were not run.
Cross session persistence [supported] Cloud sessions live in a cloud session store. Sources: kiro:b09-cloud.
Export [supported] IDE chat export to zip. Sources: kiro:b09-export.
Mutability [unknown] Not established for mutability in the named first-party source pass. Product access and scenario tests were not run.
Retention [unknown] Not established for retention in the named first-party source pass. Product access and scenario tests were not run.
Integrity [unknown] Not established for integrity in the named first-party source pass. Product access and scenario tests were not run.
IDE supervised mode shows agent-generated file changes for review. Turn-completion review must be distinguished from a merge/deployment authorization gate.
Scope
Surfaces: Kiro IDE, Kiro CLI, Kiro Web, Kiro mobile preview, Kiro Crew · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Pending reviews [unknown] Not established for pending reviews in the named first-party source pass. Product access and scenario tests were not run.
Change understanding [supported] IDE supervised mode shows agent-generated file changes for review. Sources: kiro:gap07-review.
Evidence navigation [unknown] Not established for evidence navigation in the named first-party source pass. Product access and scenario tests were not run.
Comments [supported] The agent addresses PR review comments. Sources: kiro:b09-github.
Request changes [supported] PR feedback via /kiro commands or the task view updates the PR. Sources: kiro:b09-github.
Shipping guidance [partial] Turn-completion review must be distinguished from a merge/deployment authorization gate. Sources: kiro:gap07-review.
Effort [unknown] Not established for effort in the named first-party source pass. Product access and scenario tests were not run.
Missed evidence [unknown] Not established for missed evidence in the named first-party source pass. Product access and scenario tests were not run.
Keyboard [unknown] Not established for keyboard in the named first-party source pass. Product access and scenario tests were not run.
Narrow screen [unknown] Not established for narrow screen in the named first-party source pass. Product access and scenario tests were not run.
Context switching [unknown] Not established for context switching in the named first-party source pass. Product access and scenario tests were not run.
Roles [unknown] Not established for roles in the named first-party source pass. Product access and scenario tests were not run.
Retained context [unknown] Not established for retained context in the named first-party source pass. Product access and scenario tests were not run.
Sandbox file state persists with the session and PR diffs show under Reviews.
Scope
Surfaces: Kiro Web, Kiro IDE, Kiro CLI, Kiro mobile preview · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Cloud-session sandbox file state persists across native-client attachments; PR files and diffs under Reviews are documented for the Web GitHub workflow. No identical review UI across clients is established. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
13 atomic answers
Diffs [supported] PRs and MRs; PR files and diffs show under Reviews in the session. Sources: kiro:b09-github.
Documents [unknown] Not established for documents in the named first-party source pass. Product access and scenario tests were not run.
Screenshots [unknown] Not established for screenshots in the named first-party source pass. Product access and scenario tests were not run.
Recordings [unknown] Not established for recordings in the named first-party source pass. Product access and scenario tests were not run.
Previews [unknown] Not established for previews in the named first-party source pass. Product access and scenario tests were not run.
Test outputs [unknown] Not established for test outputs in the named first-party source pass. Product access and scenario tests were not run.
Reviewer outputs [unknown] Not established for reviewer outputs in the named first-party source pass. Product access and scenario tests were not run.
Gallery [unknown] Not established for gallery in the named first-party source pass. Product access and scenario tests were not run.
Task links [unknown] Not established for task links in the named first-party source pass. Product access and scenario tests were not run.
Revision links [unknown] Not established for revision links in the named first-party source pass. Product access and scenario tests were not run.
Task steps run tests before committing unless --no-test is selected. A separate reviewer session checks the actual Git diff. Analyze Requirements is listed for IDE/CLI; Correctness property-based testing is listed only for IDE. Review failures revert/retry, but reviewer exceptions are treated as passed and tests may be skipped. force_approval gates and --no-test configure distinct run behaviors. force_approval blocks execution even under YOLO, with explicit Approve/Deny buttons.
Scope
Surfaces: Kiro CLI, Kiro IDE, Kiro Web · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
Unknown after the targeted first-party documentation, release and repository pass: lint, types, ci, required_checks, requirement_conflicts. No configured product fixture was run; documentation does not establish successful hands-on behavior.
11 atomic answers
Tests [supported] Task steps run tests before committing unless --no-test is selected. Sources: kiro:gap07-runner.
Lint [unknown] Not established for lint in the named first-party source pass. Product access and scenario tests were not run.
Types [unknown] Not established for types in the named first-party source pass. Product access and scenario tests were not run.
Ci [unknown] Not established for ci in the named first-party source pass. Product access and scenario tests were not run.
Independent review [supported] A separate reviewer session checks the actual Git diff. Sources: kiro:gap07-runner.
Spec checks [supported] Analyze Requirements is listed for IDE/CLI; Correctness property-based testing is listed only for IDE. Sources: kiro:nov07-specs.
Required checks [unknown] Not established for required checks in the named first-party source pass. Product access and scenario tests were not run.
Failure blocking [partial] Review failures revert/retry, but reviewer exceptions are treated as passed and tests may be skipped. Sources: kiro:gap07-runner.
Requirement conflicts [unknown] Not established for requirement conflicts in the named first-party source pass. Product access and scenario tests were not run.
Configured policy [supported] force_approval gates and --no-test configure distinct run behaviors. Sources: kiro:gap07-runner.
Enforced policy [supported] force_approval blocks execution even under YOLO, with explicit Approve/Deny buttons. Sources: kiro:gap07-runner.
The Web spec flow implements tasks and opens a PR or merge request, with later feedback updates.
Scope
Surfaces: Kiro CLI, Kiro IDE, Kiro Web · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Git and pull request workflow: first-party sources in this pass did not establish branches, worktrees, commits, comments, ci_response, rebase, conflicts, product_state. No draft PR, failed-gate, stale-approval, rollback or six-task batch-review fixture was run. Described actions do not prove delivery authority.
Workflow-based answers depend on opt-in Workflows, which docs say are not yet available on every account (2026-11-22).
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
9 atomic answers
Branches [unknown] Not established for branches in the named first-party source pass. Product access and scenario tests were not run.
Worktrees [partial] A workflow prompt can ask for a fresh worktree; not a default. Sources: kiro:b09-workflows.
Commits [supported] Web agent commits on a feature branch; Crew Task Runner commits per step. Sources: kiro:b09-github, kiro:b09-runner.
Pull requests [supported] The Web spec flow implements tasks and opens a PR or merge request, with later feedback updates. Sources: kiro:nov07-specs.
Comments [supported] /kiro all and /kiro fix address PR review comments. Sources: kiro:b09-github.
Ci response [unknown] Not established for ci response in the named first-party source pass. Product access and scenario tests were not run.
Rebase [unknown] Not established for rebase in the named first-party source pass. Product access and scenario tests were not run.
Conflicts [unknown] Not established for conflicts in the named first-party source pass. Product access and scenario tests were not run.
Product state [unknown] Not established for product state in the named first-party source pass. Product access and scenario tests were not run.
Kiro Web explicitly says it never merges changes automatically; the user reviews before the default branch is changed.
Scope
Surfaces: Kiro Web · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
Merge and deployment authority: first-party sources in this pass did not establish approve, release, deploy, exact_revision, authority_enforcement. No draft PR, failed-gate, stale-approval, rollback or six-task batch-review fixture was run. Described actions do not prove delivery authority.
6 atomic answers
Approve [unknown] Not established for approve in the named first-party source pass. Product access and scenario tests were not run.
Merge [unsupported] Kiro Web explicitly says it never merges changes automatically; the user reviews before the default branch is changed. Sources: kiro:nov07-web.
Release [unknown] Not established for release in the named first-party source pass. Product access and scenario tests were not run.
Deploy [unknown] Not established for deploy in the named first-party source pass. Product access and scenario tests were not run.
Exact revision [unknown] Not established for exact revision in the named first-party source pass. Product access and scenario tests were not run.
Authority enforcement [unknown] Not established for authority enforcement in the named first-party source pass. Product access and scenario tests were not run.
Crew retains per-step commits and can revert a failed independent-review step before retry. IDE supervised rejection reverts files, while the Web GitHub workflow opens linked PRs. Other delivery evidence remains unestablished.
Scope
Surfaces: Kiro Crew, Kiro IDE, Kiro Web · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Crew per-step commit/review-retry evidence, IDE supervised-change reversion, and Web GitHub PR links are separate findings. No identical deployment or rollback interface across clients is established. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Commit links [unknown] Not established for commit links in the named first-party source pass. Product access and scenario tests were not run.
Pr links [supported] Opens PRs with detailed descriptions. Sources: kiro:b09-github.
Build links [unknown] Not established for build links in the named first-party source pass. Product access and scenario tests were not run.
Deployment links [unknown] Not established for deployment links in the named first-party source pass. Product access and scenario tests were not run.
Delivery status [unknown] Not established for delivery status in the named first-party source pass. Product access and scenario tests were not run.
Retained evidence [supported] Per-step commits and Git log/diff state feed later step prompts. Sources: kiro:gap07-runner.
Rollback [supported] A failed independent review reverts the step commit before retry. Sources: kiro:gap07-runner.
Revert [supported] Rejecting supervised changes reverts files to their pre-turn state according to the guide. Sources: kiro:nov07-security.
Stale approval invalidation [unknown] Not established for stale approval invalidation in the named first-party source pass. Product access and scenario tests were not run.
Kiro IDE and CLI use the AWS Content and AWS IP License terms. Kiro provides dependency-source attribution and relinking material; a complete open-source IDE/CLI was not established.
Scope
Surfaces: Kiro IDE, Kiro CLI, Kiro Web, Kiro mobile preview, Kiro Crew · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
Unknown after the targeted first-party documentation, release and repository pass: server_license, hosted_extensions, source_revision, hosted_parity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
6 atomic answers
Client license [supported] Kiro IDE and CLI use the AWS Content and AWS IP License terms. Sources: kiro:gap07-license.
Server license [unknown] Not established for server license in the named first-party source pass. Product access and scenario tests were not run.
Hosted extensions [unknown] Not established for hosted extensions in the named first-party source pass. Product access and scenario tests were not run.
Source visibility [partial] Kiro provides dependency-source attribution and relinking material; a complete open-source IDE/CLI was not established. Sources: kiro:gap07-license.
Source revision [unknown] Not established for source revision in the named first-party source pass. Product access and scenario tests were not run.
Hosted parity [unknown] Not established for hosted parity in the named first-party source pass. Product access and scenario tests were not run.
The Crew Gateway and dashboard run locally, in Docker or on a user-controlled remote host; Kiro/model-service credentials remain backend-specific. Crew runtime/state are user-hosted, while selected coding harness and provider authentication may depend on external services. IDE/CLI on one machine share local memory, distinct from cross-device transcript export.
Scope
Surfaces: Kiro IDE, Kiro CLI, Kiro Web, Kiro mobile preview, Kiro Crew · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Self hosting [supported] The Crew Gateway and dashboard run locally, in Docker or on a user-controlled remote host; Kiro/model-service credentials remain backend-specific. Sources: kiro:gap07-crew-hosting.
Vendor dependencies [partial] Crew runtime/state are user-hosted, while selected coding harness and provider authentication may depend on external services. Sources: kiro:gap07-crew-hosting.
Export [partial] IDE chats export as zip files; full account export was not found. Sources: kiro:b09-export.
Import [unknown] Not established for import in the named first-party source pass. Product access and scenario tests were not run.
Formats [unknown] Not established for formats in the named first-party source pass. Product access and scenario tests were not run.
Cancellation [supported] Cancel by switching to Kiro Free; the paid plan lasts to month end. Sources: kiro:b09-cancel.
Account independence [unknown] Not established for account independence in the named first-party source pass. Product access and scenario tests were not run.
History portability [partial] IDE/CLI on one machine share local memory, distinct from cross-device transcript export. Sources: kiro:gap07-memory.
Improvement content can include generated code, questions, other inputs and responses. Free-tier inputs may be retained up to sixty days for abuse detection; model-specific retention may also apply. Free and individual subscriber content can improve services or models unless opted out; enterprise content is excluded from service improvement. Usage telemetry includes interaction, errors and metrics, separate from shared improvement content. Individual/free usage analytics, errors/crashes and improvement content are collected by default. IDE unchecks Usage Analytics and Performance Metrics; CLI toggles Telemetry off. Content-sharing controls are separate. Enterprise reports are admin controlled. Model-specific abuse-retention requirements remain separate from Kiro improvement opt-out.
Scope
Surfaces: Kiro IDE, Kiro CLI, Kiro Web, Kiro mobile preview, Kiro Crew · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Code data [supported] Improvement content can include generated code, questions, other inputs and responses. Sources: kiro:gap07-data.
Prompts [unknown] Not established for prompts in the named first-party source pass. Product access and scenario tests were not run.
Credentials [unknown] Not established for credentials in the named first-party source pass. Product access and scenario tests were not run.
Logs [supported] Enterprise admins can log IDE and CLI prompts and responses to their own S3 bucket. Sources: kiro:b09-promptlog.
Artifacts [unknown] Not established for artifacts in the named first-party source pass. Product access and scenario tests were not run.
Retention [supported] Free-tier inputs may be retained up to sixty days for abuse detection; model-specific retention may also apply. Sources: kiro:gap07-data.
Deletion [supported] Account deletion has a 30-day restore window, then account and data are permanently deleted. Sources: kiro:b09-delete.
Training [supported] Free and individual subscriber content can improve services or models unless opted out; enterprise content is excluded from service improvement. Sources: kiro:gap07-data.
Residency [supported] Free and individual content is stored in us-east-1; enterprise content in the profile's Region. Sources: kiro:b09-dataprot.
Subprocessors [unknown] Not established for subprocessors in the named first-party source pass. Product access and scenario tests were not run.
Telemetry disclosure [supported] Usage telemetry includes interaction, errors and metrics, separate from shared improvement content. Sources: kiro:gap07-data.
Telemetry defaults [supported] Individual/free usage analytics, errors/crashes and improvement content are collected by default. Sources: kiro:gap07-data.
Telemetry controls [supported] IDE unchecks Usage Analytics and Performance Metrics; CLI toggles Telemetry off. Content-sharing controls are separate. Enterprise reports are admin controlled. Sources: kiro:gap07-data.
Consent prompt [unknown] Not established for consent prompt in the named first-party source pass. Product access and scenario tests were not run.
Provider separation [supported] Model-specific abuse-retention requirements remain separate from Kiro improvement opt-out. Sources: kiro:gap07-data.
Monthly individual prices are Pro $20, Pro+ $40, Pro Max $100 and Power $200, checked 7 November 2026. Team pooling costs $20/seat/month, adding 500 included credits per seat, with at least two seats. Further scoped facts are recorded in the atomic answers. Crew Strands accepts separately supplied model-provider keys stored in Settings Secrets. These external model costs are distinct from managed Kiro credit billing.
Scope
Surfaces: Kiro CLI, Kiro Crew, Kiro IDE, Kiro mobile preview, Kiro Web · Version: Kiro Crew v0.12.2 (b6599234221cfc492c0dd95fdd53643e710c9f28) where named; managed Kiro cloud/mobile documentation checked 2026-11-13; no installed-product test. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
The scoped first-party source pass does not establish currency, seat_minimum, workspace_fees, credits, trial. No hands-on scenario was run.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Interval [supported] Monthly individual prices are Pro $20, Pro+ $40, Pro Max $100 and Power $200, checked 7 November 2026. Sources: kiro:nov07-pricing.
Seats [supported] Team pooling costs $20/seat/month, adding 500 included credits per seat, with at least two seats. Sources: kiro:nov07-pricing.
Workspace fees [unknown] Not established for workspace fees in the named first-party source pass. Product access and scenario tests were not run.
Included usage [supported] Individual paid tiers include 1,000/2,000/5,000/10,000 credits respectively; model multipliers and task complexity affect consumption. Sources: kiro:nov07-pricing.
Credits [supported] Usage is metered in credits, to 0.01 credit. Sources: kiro:b09-pricing.
Trial [supported] First Pro upgrade: rest of the month free plus 500 trial credits valid 12 months. Sources: kiro:b09-pricing.
Overages [supported] Add-on credits cost $0.04 each; individual packs are prepaid and expire after twelve months. Sources: kiro:nov07-pricing.
Taxes [supported] The page excludes applicable taxes/duties unless stated; GovCloud pricing is approximately 20% higher and has no Free tier. Sources: kiro:nov07-pricing.
Model cost [supported] Crew Strands accepts separately supplied model-provider keys stored in Settings Secrets. These external model costs are distinct from managed Kiro credit billing. Sources: kiro:facet38-crew-release.
Compute cost [supported] Cloud sessions are included in the existing paid credit model with no separate cloud-compute charge, checked 7 November 2026. Sources: kiro:nov07-cloud.
Plan and pooled-seat prices give fixed monthly costs; per-task credits vary by model and task.
Scope
Surfaces: Kiro IDE, Kiro CLI, Kiro Web, Kiro mobile preview · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Kiro account/subscription and pooled-seat credit pricing for native Kiro use; published fixed fees exclude usage-dependent add-on credits. This does not price a fixed workload, third-party harness use or self-hosted Crew infrastructure. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
11 atomic answers
One person [partial] $0 (50 credits) to $200/month (10,000 credits) per plan, plus add-on credits. Sources: kiro:b09-pricing.
Two people [partial] Two pooled seats: $40/month with 1,000 shared credits. Sources: kiro:b09-pricing.
Five people [partial] Five pooled seats: $100/month with 2,500 shared credits, plus $0.04 add-on credits. Sources: kiro:b09-pricing.
Task assumptions [unknown] Not established for task assumptions in the named first-party source pass. Product access and scenario tests were not run.
Concurrency [unknown] Not established for concurrency in the named first-party source pass. Product access and scenario tests were not run.
Tokens [unknown] Not established for tokens in the named first-party source pass. Product access and scenario tests were not run.
Compute hours [unknown] Not established for compute hours in the named first-party source pass. Product access and scenario tests were not run.
Fixed cost [partial] Published subscription fees provide a fixed monthly component: pooled seats are $20 each, giving $40 for two or $100 for five, before usage-dependent add-ons. This is not a complete workload total. Sources: kiro:b09-pricing.
Variable cost [partial] Additional credits are usage-dependent; the pooled plan lists $0.04 per add-on credit. Credit consumption varies with model and task, so a fixed per-task total is unestablished. Sources: kiro:b09-pricing.
Included cost [partial] The cited plans include credit allowances: Free has 50 credits, two pooled seats share 1,000, and five share 2,500. These allowances do not establish how many tasks a workload completes. Sources: kiro:b09-pricing.
Unknown cost [supported] Credits per prompt vary with model and task, so per-task cost is not fixed. Sources: kiro:b09-pricing.
Mobile is TestFlight early access on iPhone and Google Play on Android, separate from IDE/CLI/Web availability. CLI 3.0.0 retired Classic and the desktop app; Enterprise support runs through AWS Support.
Scope
Surfaces: Kiro IDE, Kiro CLI, Kiro Web, Kiro mobile preview · Version: Kiro changelog retrieved 2026-11-12. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Client-specific mobile distribution and CLI release changes, plus service-level Enterprise support and the administrative Enterprise Management preview. Mobile release restrictions do not define all Kiro clients. · OS: Not specified · Execution modes: local, managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Availability and support: first-party sources in this pass did not establish support, response_commitments, status_history, deprecation, export_options. No full license/hosted parity audit, assurance-report access or fixed one/two/five-person workload costing was performed. Public pricing is dated; missing rates remain unknown.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
Release stage [partial] Enterprise Management APIs are documented as preview and not yet publicly released, with us-east-1 and eu-central-1 regional setup. Other client release stages retain their separately cited bounds. Sources: kiro:nov12-changelog, kiro:b09-em-api.
Access restrictions [supported] The cited mobile access finding describes iPhone TestFlight early access; it does not define IDE, CLI or Web availability. Android distribution is recorded separately in ACC-01. Sources: kiro:nov07-mobile.
Support [supported] Enterprise cases go through AWS Support or the Kiro Support power. Sources: kiro:b09-support.
Response commitments [unknown] Not established for response commitments in the named first-party source pass. Product access and scenario tests were not run.
Release activity [supported] Frequent releases: IDE 1.4.121 and CLI 3.1.0 (Nov 5), IDE 1.4.154 and CLI 3.2.0 (Nov 10), CLI 3.2.1 (Nov 11, 2026). Sources: kiro:nov12-changelog.
Status history [unknown] Not established for status history in the named first-party source pass. Product access and scenario tests were not run.
Deprecation [supported] CLI 3.0.0 (2026-11-03) retired the Classic interface, desktop app and inline autocomplete, listed as breaking changes. Sources: kiro:b09-cl30.
Export options [unknown] Not established for export options in the named first-party source pass. Product access and scenario tests were not run.
Kiro is in AWS's ISO/IEC 27001:2022 scope (EY CertifyPoint); reports via AWS Artifact; certificate not inspected.
Scope
Surfaces: Kiro IDE, Kiro CLI, Kiro Web, Kiro mobile preview · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Vendor statement about the Kiro service within AWS ISO/IEC 27001:2022 scope. The certificate and service listing have not been inspected; no independent certificate or identical certification boundary is asserted for each client or self-hosted Crew. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
9 atomic answers
Iso scope [supported] Kiro is in the scope of AWS's ISO/IEC 27001:2022 certification. Sources: kiro:b09-compliance.
Iso validity [unknown] Not established for iso validity in the named first-party source pass. Product access and scenario tests were not run.
Soc2 type [unknown] Not established for soc2 type in the named first-party source pass. Product access and scenario tests were not run.
Soc2 scope [unknown] Not established for soc2 scope in the named first-party source pass. Product access and scenario tests were not run.
Soc2 period [unknown] Not established for soc2 period in the named first-party source pass. Product access and scenario tests were not run.
Report access [supported] Reports via AWS Artifact, which needs Builder ID or IAM Identity Center sign-in. Sources: kiro:b09-compliance.
Verification date [unknown] Not established for verification date in the named first-party source pass. Product access and scenario tests were not run.
Evidence status [partial] Vendor statement of ISO 27001 scope; the certificate was not inspected. Sources: kiro:b09-compliance.
Kiro Free provides fifty credits monthly for limited listed models; cloud/Web access is not implied. First upgrade to Pro gets the rest of the month free plus 500 trial credits valid for twelve months; higher-plan differences may be charged. Further scoped facts are recorded in the atomic answers.
Scope
Surfaces: Kiro CLI, Kiro Crew, Kiro IDE, Kiro mobile preview, Kiro Web · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Useful free tier and evaluation access: first-party sources in this pass did not establish credits_trial, self_host_cost, early_access, free_scenarios, usage_caps, paid_evaluation. No full license/hosted parity audit, assurance-report access or fixed one/two/five-person workload costing was performed. Public pricing is dated; missing rates remain unknown.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
10 atomic answers
Ongoing free [supported] Kiro Free provides fifty credits monthly for limited listed models; cloud/Web access is not implied. Sources: kiro:nov07-pricing.
Trial [supported] First upgrade to Pro gets the rest of the month free plus 500 trial credits valid for twelve months; higher-plan differences may be charged. Sources: kiro:nov07-pricing.
Credits trial [unknown] Not established for credits trial in the named first-party source pass. Product access and scenario tests were not run.
Self host cost [partial] Crew is open source and self-hosted but runs on kiro-cli sign-in and Kiro credits. Sources: kiro:b09-crew, kiro:b09-pricing.
Paid only [supported] Web requires Pro, Pro+, Pro Max or Power; Free does not establish Web access. Sources: kiro:nov07-web.
Early access [unknown] Not established for early access in the named first-party source pass. Product access and scenario tests were not run.
Free scenarios [unknown] Not established for free scenarios in the named first-party source pass. Product access and scenario tests were not run.
Card required [supported] Upgrading to a paid plan requires a valid card. Sources: kiro:nov07-pricing.
Usage caps [supported] Kiro Free includes 50 credits a month. Sources: kiro:b09-pricing.
Paid evaluation [unknown] Not established for paid evaluation in the named first-party source pass. Product access and scenario tests were not run.
Credit pricing is public but model choice and work complexity prevent deriving a fixed per-task cost.
Scope
Surfaces: Kiro CLI, Kiro Crew, Kiro IDE, Kiro mobile preview, Kiro Web · Version: Public sources checked 2026-11-07; no installed release tested. Batch 09 recheck 2026-11-22: kiro.dev docs (Markdown twins), pricing and changelog (CLI 3.0.0, 2026-11-03; entries through 2026-11-20); Crew answers cite current Crew docs (0.10.0+), while retained Crew v0.12.2 source citations keep their pin. · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-22 (checked today)
Agent cross-check
2026-11-22
Pricing transparency: first-party sources in this pass did not establish included_limits, overages, compute_markup, model_markup, minimum_commitment, cancellation, sales_only_unknowns, transparency_classification. No full license/hosted parity audit, assurance-report access or fixed one/two/five-person workload costing was performed. Public pricing is dated; missing rates remain unknown.
Documentation and public-code recheck only (2026-11-22); no product fixture was run.
9 atomic answers
Units [supported] Credit pricing is public but model choice and work complexity prevent deriving a fixed per-task cost. Sources: kiro:nov07-pricing.
Included limits [supported] Each plan includes a fixed monthly credit amount. Sources: kiro:b09-pricing.
Overages [partial] Add-on credits at $0.04; credit pooling uses no overages, while existing Enterprise subscriptions can keep overages. Sources: kiro:b09-pricing.
Model markup [unknown] Not established for model markup in the named first-party source pass. Product access and scenario tests were not run.
Minimum commitment [supported] Monthly billing; credit pooling needs at least two seats. Sources: kiro:b09-pricing.
Cancellation [supported] Downgrade to Free anytime; the plan runs to month end. Sources: kiro:b09-cancel.
Sales only unknowns [unknown] Not established for sales only unknowns in the named first-party source pass. Product access and scenario tests were not run.
Transparency classification [unknown] Not established for transparency classification in the named first-party source pass. Product access and scenario tests were not run.
Clients attach to the same remote session; disconnection does not stop work, approvals wait, and paid plans include cloud compute with a ten-session cap.
Android is publicly available through Google Play for Android 10+. iPhone requires requested early access through TestFlight; the request page says only limited invitees receive access. Both use paid-plan cloud sessions.
The shipped gateway documents opening its HTTPS dashboard URL on a phone, including a named tunnel or Tailscale Serve token link. This is the user-hosted Crew browser client, distinct from the native Kiro Mobile app.
Kind
documented
Locator
Reach it from a laptop or phone; named HTTPS tunnel; lines 236-433
The IDE runs on macOS (Intel and Apple Silicon), Windows 10/11 (x64, ARM64) and listed Linux distributions; the CLI on macOS, Windows 11 and Linux; Web in any modern browser. Kiro ships as a desktop IDE, a VS Code extension (VS Code 1.145+, local workspaces only), a CLI, a web app, a mobile app and Crew. In the IDE you open a folder to start a session.
Kind
documented
Locator
Intro; System requirements; Open a project; Install Kiro for VS Code
Kiro IDE, CLI, Web and Mobile use ACP to reach the unified harness; ACP-compatible editors such as JetBrains IDEs and Zed connect through ACP with capabilities their client implements.
Developer Mode enables Preview selection of Claude Code, Codex, OpenCode, Pi and other harnesses. Existing sessions retain their backend. Pi lacks Crew MCP tools; Codex requires sandboxing; Claude preapproved calls may bypass Crew audit.
The public release removes Developer Mode, adds Strands and GitHub Copilot CLI, exposes provider keys in Settings Secrets, and ships Shared Crew as a preview owners can switch on to admit other people over Tailscale with equal access.
Kind
documented
Locator
November 5: More Coding Agents; Previews You Can Turn On
The released runtime has a closed known-backend set for Kiro, Claude Code, KAS, Strands, Codex, OpenCode, Pi, Goose, DeepSeek and Copilot. Registration rejects a backend outside that set. Edition plugin registration does not supply a generic arbitrary coding-harness adapter; configured MCP tool commands are a separate feature.
Free $0 with 50 credits/month; Pro $20 (1,000 credits), Pro+ $40 (2,000), Pro Max $100 (5,000), Power $200 (10,000) per user per month, USD; add-on credits $0.04 each. Credit pooling for teams of 2+: $20 per seat/month adding 500 credits per seat; admins set user, group and profile limits; credit pooling doesn't use overages, existing Enterprise subscriptions can keep overages. First upgrade to Pro: rest of month free plus 500 trial credits valid 12 months. A credit is a unit of work; credits per prompt vary by model and task. Subscriptions cover IDE, CLI, Web, Crew, ACP IDEs and CI automation; use through third-party automation harnesses that route requests outside Kiro's native interfaces is not permitted. Auto routing or a chosen OpenAI, Anthropic, xAI or open-weight model.
Crew sessions can run on Kiro CLI, Kiro Agent, Claude Code, Codex, OpenCode, Pi, goose or DeepSeek Harness backends; backends other than Kiro CLI are Experimental (Crew 0.10.0+).
Codex uses its own .codex/auth.json and native sign-in; Claude Code uses its own .claude/.credentials.json and native terminal sign-in. Both are own_credential_file entitlements, independent of Crew Kiro logout. This establishes reuse of each coding agent account through its native harness rather than an API-key-only wrapper.
Kind
source-inspected
Locator
AgentAuthDeclaration for Codex and Claude Code, lines 503-551
The kiro label or a /kiro comment assigns an issue to the agent, which listens to issue comments; users assign only to repositories where they have write permission and others cannot assign on their behalf. The agent clones into its sandbox, creates a feature branch, commits with co-authors, opens PRs with detailed descriptions; /kiro all and /kiro fix address PR review comments and check feedback. PR files and diffs show under Reviews. If multiple users assign the same issue, separate tasks are created.
Kind
documented
Locator
Installation; Assigning tasks from GitHub issues; How the agent works with GitHub; Addressing PR feedback; Review pull requests in your session; Multiple users
Cloud sessions are included in the plan with no separate charge for cloud compute; up to 10 concurrent cloud sessions. IDE, CLI, Web and Mobile create, resume and steer the same session; disconnecting a client doesn't stop the agent; history, repositories and sandbox file state persist and the transcript replays on reattach; approvals wait for the next client. Workflow progress and results return to the parent session. Sessions run in the profile's Region, us-east-1 or eu-central-1; Pro-family plan required.
Kind
documented
Locator
Info box; capability table; How cloud sessions work; Prerequisites
kiro-cli runs non-interactively in CI with a KIRO_API_KEY; API keys are available only to Pro, Pro+, Pro Max and Power subscribers and admins must enable them for managed subscriptions; governance rules apply to headless sessions.
16 operations create, edit, publish and assign Kiro policies via SigV4; Enterprise Management is in preview in us-east-1 and eu-central-1 and the APIs are not yet publicly released (custom AWS CLI model).
Capability rules (fs_read, fs_write, shell, web_fetch, mcp, subagent and others) with deny, ask, allow or evaluate effects and glob match patterns apply in IDE and CLI; Web approves every sandbox action by default. With Approve for me on Web, approved tool calls are marked Approved for you and blocked ones fail with a reason.
Kind
documented
Locator
Capability table; capabilities and effects; Approve for me in Kiro Web
Kiro IDE and CLI are AWS Content under AWS agreements and the AWS IP License. Chromium is the IDE engine; Bun powers the CLI frontend. Dependency licenses do not license the main application as open source.
Every surface is a front end speaking ACP to a standalone harness process that runs locally or in a cloud sandbox. Every tool call is checked against permission rules and kiroignore patterns that keep files out of agent access.
Kind
documented
Locator
One harness, many surfaces; tool checks; configuration table
Crew decomposes Markdown specs into persistent task runs and step sessions. Up to three runs/parallel steps, per-run IDs/branches/worktrees, test/review/retry checkpoints, restart reconciliation and explicit approval gates are documented.
Specs create requirements/design/tasks files and schedule independent tasks in dependency waves; correctness testing and mobile parity have explicit limits.
Workflows are opt-in graphs of agent steps, sequences, loops and parallel branches generated from a prompt (approved before running) or saved as recipes; Kiro ships investigate, feature-pipeline and publish-pr recipes. Steps may set custom agents, models and effort; each step session can be paused, resumed or steered and revisited with follow-ups; progress and results return to the parent chat. If Workflows is absent from settings it is not yet available for the account. Example prompts can ask for a fresh worktree.
Kind
documented
Locator
Intro; Start from the agent; recipes; Enable per client; structure (steps, loops, branches); Background delegation
Memory is stored locally per user account and shared by IDE/CLI on the machine. It defaults off in IDE and has read-only/learn controls. Current subagents can read parent memory but cannot modify it.
IDE/CLI requirements analysis identifies logical contradictions, ambiguities, conflicting constraints and missing cases. Chat answers update requirements.md. Web does not yet offer this analysis.
Kiro generates requirements.md with acceptance criteria, design.md with architecture and testing strategy, and tasks.md with dependencies and optional/required work. Humans review and refine each phase.
Scheduled tasks run a prompt against GitHub or GitLab repositories on a schedule in autonomous mode without starting a session (Pro plans and up); they can be disabled, re-enabled and edited.
Hooks trigger on file, task, prompt-submit, agent-stop, session-start and tool-use events; file and task triggers run in IDE and CLI V3, Web runs the prompt, stop, session and tool triggers.
Crew is an open-source personal agent that runs on the user's machine, a local container or a remote machine they control, with its gateway at localhost:5476; first launch installs kiro-cli and signs in.
Free and individual subscriber content is stored in us-east-1; enterprise content may be stored in the profile's Region; inference location can differ.
Crew Gateway can run as a service or in Docker on user hardware, including an always-on remote Linux host while the laptop sleeps. Sandbox availability is checked before container agent execution.
The engineering explanation says the same standalone harness runs on a laptop or inside a VM in the cloud; remote clients connect to its cloud sandbox. This establishes VM execution, not tested containment guarantees.
Crew blocks protected credential paths, masks credential locations from subprocesses with its OS sandbox, redacts credential patterns and records every decision in a security event log.
CLI 3.0.0 (2026-11-03) made V3 default and retired the Classic interface, desktop app and inline autocomplete as breaking changes with migration notes; cloud sessions resume from /sessions.
Kind
documented
Locator
V3 by Default, Classic and Desktop App Retired; Breaking changes
CLI 3.2.1 (Nov 11); Enterprise Management preview sets one policy for IDE, CLI, Kiro Web and Kiro Crew LTS, for new profiles in US East (N. Virginia) (Nov 10); Kiro Crew LTS (Nov 10); IDE 1.4.154 adds Approve for me and turns the Autopilot toggle into a permission-mode menu: Supervised, Accept file changes, Approve for me (Nov 10); CLI 3.2.0 (Nov 10); Kiro Web Approve for me, where a model approves, blocks or asks about agent actions (Nov 6); CLI 3.1.0 shows session credits used in /usage (Nov 5).
Shipped chat admission records the verified actor with each prompt. The presence model distinguishes principals in one session and attribution labels multiple human authors in the same session. preview.py permits the owner to enable this released opt-in preview; this is distinct people sharing one Crew, not just same-account device access.
Kind
source-inspected
Locator
Chat prompt payload and admit_chat_turn; collab.py presence; attribution.py sender_line
The complete pricing page distinguishes organization administrators who manage users, groups, pooled credit limits and access from assigned members. This establishes organization-level administrative roles, without claiming Crew fine-grained per-person roles from a proposal.
Kind
documented
Locator
Teams; shared credit pools and enterprise controls
Individual/free usage may supply content for improvement by default. IDE/CLI telemetry and content have separate opt-outs. Enterprise improvement collection is off; admin reports remain separately controlled. Free inputs may be held up to sixty days for abuse detection.
Kiro is in the scope of AWS's ISO/IEC 27001:2022 certification, verified by EY CertifyPoint; reports download through AWS Artifact, which requires Builder ID or IAM Identity Center sign-in.