# Kiro

Podium publishes this catalog and sells an agent development environment. Podium chooses the products, criteria, sources and wording, so treat these pages as vendor-authored research. Check important claims against the linked primary sources. The same evidence rules apply to Podium and its competitors, but they do not remove this conflict of interest.

Page: https://adecomparison.com/ade/kiro/
Website: https://kiro.dev/
Research: covered

Method: https://adecomparison.com/method/

Rank by must-haves met, then preferences, then name. Read each finding's checked date. Findings stay published after their scheduled recheck. Checks over six months old may be outdated.

## kiro:ACC-01

Finding: 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.

Verification: sourced
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: 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

The scoped first-party source pass does not establish editor_extensions, notifications. No hands-on scenario was run.

Source: https://kiro.dev/docs/getting-started/installation.md
Locator: System requirements; client installation
Finding: Kiro documents distinct IDE, CLI, Web, iOS early access and Crew installations, with OS-specific requirements.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/mobile.md
Locator: Early access; cloud-session links
Finding: Kiro iOS is early access through TestFlight; detailed mobile documentation is still pending.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/cloud-sessions.md
Locator: How sessions work; prerequisites; client matrix
Finding: 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.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/mobile.md
Locator: Availability; Android and iPhone table
Finding: 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.
Retrieved: 2026-11-13

Source: https://github.com/kirodotdev/KiroCrew/blob/b6599234221cfc492c0dd95fdd53643e710c9f28/docs/guides/remote-and-mobile.md
Locator: Reach it from a laptop or phone; named HTTPS tunnel; lines 236-433
Finding: 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.
Retrieved: 2026-11-13

## kiro:ACC-02

Finding: 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.

Verification: sourced
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: 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

The scoped first-party source pass does not establish model_providers. No hands-on scenario was run.

Source: https://kiro.dev/docs/crew/features/agent-backends.md
Locator: Preview selector; Available backends; Constraints
Finding: 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.
Retrieved: 2026-11-07

Source: https://kiro.dev/changelog/crew/
Locator: November 5: More Coding Agents; Previews You Can Turn On
Finding: 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.
Retrieved: 2026-11-13

Source: https://github.com/kirodotdev/KiroCrew/blob/b6599234221cfc492c0dd95fdd53643e710c9f28/src/kiro_crew/agent_sdk/backends.py
Locator: ACP_BACKENDS_KNOWN lines 430-445; register_selectable_backend lines 731-763
Finding: 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.
Retrieved: 2026-11-13

## kiro:ACC-03

Finding: 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. The managed Kiro Agent backend uses the Kiro sign-in and Kiro credit entitlement; external backends have separate account routes.

Verification: sourced
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Kiro Crew
Version: Kiro Crew v0.12.2 (b6599234221cfc492c0dd95fdd53643e710c9f28) where named; managed Kiro cloud/mobile documentation checked 2026-11-13; no installed-product test

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.

Source: https://github.com/kirodotdev/KiroCrew/blob/b6599234221cfc492c0dd95fdd53643e710c9f28/src/kiro_crew/agent_sdk/host_auth.py
Locator: AgentAuthDeclaration for Codex and Claude Code, lines 503-551
Finding: 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.
Retrieved: 2026-11-13

Source: https://kiro.dev/changelog/crew/
Locator: November 5: More Coding Agents; Previews You Can Turn On
Finding: 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.
Retrieved: 2026-11-13

## kiro:ACC-04

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Kiro CLI; Kiro Crew; Kiro IDE; Kiro mobile preview; Kiro Web
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://kiro.dev/docs/getting-started/installation.md
Locator: System requirements; client installation
Finding: Kiro documents distinct IDE, CLI, Web, iOS early access and Crew installations, with OS-specific requirements.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/cloud-sessions.md
Locator: How sessions work; prerequisites; client matrix
Finding: 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.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/crew.md
Locator: Installation; recurring work; persistence
Finding: Crew is a distinct local or user-hosted Gateway agent with persistent sessions, schedules, memory and a task runner.
Retrieved: 2026-11-07

## kiro:ACC-07

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Kiro IDE; Kiro CLI; Kiro Web; Kiro mobile preview; Kiro Crew
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: mobile_implementation, hybrids. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://kiro.dev/license/
Locator: Application license; Open-source attribution
Finding: 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.
Retrieved: 2026-11-07

## kiro:PLAN-01

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Kiro IDE; Kiro CLI; Kiro Web; Kiro mobile preview; Kiro Crew
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: prompt_intake, external_import, chat_git_triggers, sync, supported_edits, external_roundtrips. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://kiro.dev/docs/crew/features/task-runner.md
Locator: Loop; Task IDs; Recovery; Approval gates; Dependencies
Finding: 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.
Retrieved: 2026-11-07

## kiro:PLAN-02

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Kiro CLI; Kiro IDE; Kiro Web
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://kiro.dev/docs/specs.md
Locator: Capability matrix; core structure; task execution
Finding: Specs create requirements/design/tasks files and schedule independent tasks in dependency waves; correctness testing and mobile parity have explicit limits.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/crew/features/task-runner.md
Locator: Loop; Task IDs; Recovery; Approval gates; Dependencies
Finding: 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.
Retrieved: 2026-11-07

## kiro:PLAN-03

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Kiro CLI; Kiro IDE; Kiro Web
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: epics, hierarchy, state_propagation, task_to_epic, identity_retention, workflow_constraints. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://kiro.dev/docs/specs.md
Locator: Capability matrix; core structure; task execution
Finding: Specs create requirements/design/tasks files and schedule independent tasks in dependency waves; correctness testing and mobile parity have explicit limits.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/crew/features/task-runner.md
Locator: Loop; Task IDs; Recovery; Approval gates; Dependencies
Finding: 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.
Retrieved: 2026-11-07

## kiro:PLAN-04

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Kiro CLI; Kiro Crew; Kiro IDE; Kiro mobile preview; Kiro Web
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: skills, project_docs, provenance, takeover_continuity. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://kiro.dev/docs/steering.md
Locator: Capability matrix; file scopes
Finding: Workspace and global steering have separate scopes; cloud use of local personal configuration requires opt-in upload.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/crew.md
Locator: Installation; recurring work; persistence
Finding: Crew is a distinct local or user-hosted Gateway agent with persistent sessions, schedules, memory and a task runner.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/memory.md
Locator: Storage; Access controls; Subagent scope
Finding: 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.
Retrieved: 2026-11-07

## kiro:PLAN-05

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Kiro CLI; Kiro IDE; Kiro mobile preview; Kiro Web
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: code_search, indexing, multimodal_inputs, freshness, access_scope, api_retrieval, citations. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://kiro.dev/docs/steering.md
Locator: Capability matrix; file scopes
Finding: Workspace and global steering have separate scopes; cloud use of local personal configuration requires opt-in upload.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/specs/analyze-requirements.md
Locator: What it catches; Invocation; Corrections
Finding: 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.
Retrieved: 2026-11-07

## kiro:PLAN-06

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Kiro Crew
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://kiro.dev/docs/crew.md
Locator: Installation; recurring work; persistence
Finding: Crew is a distinct local or user-hosted Gateway agent with persistent sessions, schedules, memory and a task runner.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/crew/features/task-runner.md
Locator: Loop; Task IDs; Recovery; Approval gates; Dependencies
Finding: 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.
Retrieved: 2026-11-07

## kiro:PLAN-07

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Kiro IDE; Kiro CLI; Kiro Web; Kiro mobile preview; Kiro Crew
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://kiro.dev/docs/crew/features/task-runner.md
Locator: Loop; Task IDs; Recovery; Approval gates; Dependencies
Finding: 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.
Retrieved: 2026-11-07

## kiro:PLAN-08

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Kiro CLI; Kiro IDE; Kiro Web
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://kiro.dev/docs/specs.md
Locator: Capability matrix; core structure; task execution
Finding: Specs create requirements/design/tasks files and schedule independent tasks in dependency waves; correctness testing and mobile parity have explicit limits.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/specs/feature-specs/requirements-first.md
Locator: Requirements; Design; Tasks
Finding: 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.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/specs/analyze-requirements.md
Locator: What it catches; Invocation; Corrections
Finding: 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.
Retrieved: 2026-11-07

## kiro:COORD-01

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Kiro CLI; Kiro IDE; Kiro mobile preview; Kiro Web
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://kiro.dev/docs/specs.md
Locator: Capability matrix; core structure; task execution
Finding: Specs create requirements/design/tasks files and schedule independent tasks in dependency waves; correctness testing and mobile parity have explicit limits.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/cloud-sessions.md
Locator: How sessions work; prerequisites; client matrix
Finding: 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.
Retrieved: 2026-11-07

## kiro:COORD-03

Finding: Crew can spawn isolated subagents and synthesize their results; this does not establish IDE-native delegation parity.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Kiro Crew
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://kiro.dev/docs/crew.md
Locator: Installation; recurring work; persistence
Finding: Crew is a distinct local or user-hosted Gateway agent with persistent sessions, schedules, memory and a task runner.
Retrieved: 2026-11-07

## kiro:COORD-04

Finding: Crew Schedule creates recurring jobs in separate sessions; continued execution depends on its Gateway host.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Kiro Crew; Kiro Web
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://kiro.dev/docs/web.md
Locator: Prerequisites; modes; features
Finding: Web is a paid-plan cloud client with interactive, Spec and autonomous modes, cron schedules and a documented no-auto-merge boundary.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/crew.md
Locator: Installation; recurring work; persistence
Finding: Crew is a distinct local or user-hosted Gateway agent with persistent sessions, schedules, memory and a task runner.
Retrieved: 2026-11-07

## kiro:COORD-05

Finding: Approvals requested with no client attached wait for the next attaching client.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Kiro CLI; Kiro IDE; Kiro mobile preview; Kiro Web
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://kiro.dev/docs/cloud-sessions.md
Locator: How sessions work; prerequisites; client matrix
Finding: 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.
Retrieved: 2026-11-07

## kiro:RUN-01

Finding: Crew runs on the user's machine, container or controlled remote host; the desktop app can connect through an SSH tunnel. Sessions run in isolated Kiro cloud sandboxes in us-east-1; a paid Pro-family plan and some organization enablement are required. Further scoped facts are recorded in the atomic answers.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Kiro CLI; Kiro Crew; Kiro IDE; Kiro mobile preview; Kiro Web
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://kiro.dev/docs/cloud-sessions.md
Locator: How sessions work; prerequisites; client matrix
Finding: 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.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/crew.md
Locator: Installation; recurring work; persistence
Finding: Crew is a distinct local or user-hosted Gateway agent with persistent sessions, schedules, memory and a task runner.
Retrieved: 2026-11-07

## kiro:RUN-02

Finding: 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.

Verification: sourced
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Kiro CLI; Kiro IDE
Version: Kiro Crew v0.12.2 (b6599234221cfc492c0dd95fdd53643e710c9f28) where named; managed Kiro cloud/mobile documentation checked 2026-11-13; no installed-product test

The scoped first-party source pass does not establish checkout, filesystem, process, network, secrets, security_boundary. No hands-on scenario was run.

Source: https://kiro.dev/docs/sandbox.md
Locator: Coverage; platform requirements
Finding: Kiro's optional local sandbox covers shell commands/children and optionally stdio MCP, excluding the agent and built-in file tools.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/crew/features/task-runner.md
Locator: Loop; Task IDs; Recovery; Approval gates; Dependencies
Finding: 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.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/crew/running-24-7.md
Locator: Docker; Remote host; Persistent state
Finding: 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.
Retrieved: 2026-11-07

Source: https://kiro.dev/blog/one-agent/
Locator: Kiro agent harness architecture
Finding: 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.
Retrieved: 2026-11-13

## kiro:RUN-03

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Kiro CLI; Kiro Crew; Kiro IDE; Kiro mobile preview; Kiro Web
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: client_disconnect, expiry, process_reconnect, task_resume, context_loss, multi_day_continuity. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://kiro.dev/docs/cloud-sessions.md
Locator: How sessions work; prerequisites; client matrix
Finding: 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.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/crew.md
Locator: Installation; recurring work; persistence
Finding: Crew is a distinct local or user-hosted Gateway agent with persistent sessions, schedules, memory and a task runner.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/crew/features/task-runner.md
Locator: Loop; Task IDs; Recovery; Approval gates; Dependencies
Finding: 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.
Retrieved: 2026-11-07

## kiro:RUN-05

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Kiro IDE; Kiro CLI; Kiro Web; Kiro mobile preview; Kiro Crew
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: turn_limits, token_limits, spend_limits, timeouts, provider_failures. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://kiro.dev/docs/crew/features/task-runner.md
Locator: Loop; Task IDs; Recovery; Approval gates; Dependencies
Finding: 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.
Retrieved: 2026-11-07

## kiro:RUN-07

Finding: The account dashboard updates credit usage at least every five minutes; pooled admin usage has separate dashboards.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Kiro CLI; Kiro Crew; Kiro IDE; Kiro mobile preview; Kiro Web
Version: Public sources checked 2026-11-07; no installed release tested

Per-task API and compute cost: first-party sources in this pass did not establish task_cost, session_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.

Source: https://kiro.dev/pricing/
Locator: Plan cards; pooling; trial FAQ checked 7 November 2026
Finding: Free has fifty credits; paid individual tiers and pooled team seats differ in included credits. Add-ons cost $0.04/credit and taxes are excluded.
Retrieved: 2026-11-07

## kiro:RUN-08

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Kiro IDE; Kiro CLI; Kiro Web; Kiro mobile preview; Kiro Crew
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: cpu_ram, backpressure, host_awareness, check_reuse, check_deduplication, bounded_tests, fairness, shared_limits. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://kiro.dev/docs/crew/features/task-runner.md
Locator: Loop; Task IDs; Recovery; Approval gates; Dependencies
Finding: 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.
Retrieved: 2026-11-07

## kiro:TEAM-01

Finding: 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.

Verification: sourced
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Kiro Crew
Version: Kiro Crew v0.12.2 (b6599234221cfc492c0dd95fdd53643e710c9f28) where named; managed Kiro cloud/mobile documentation checked 2026-11-13; no installed-product test

The scoped first-party source pass does not establish visibility, discussion, comments, ordering, conflicts, plan_restrictions, owner_online. No hands-on scenario was run.

Source: https://github.com/kirodotdev/KiroCrew/blob/b6599234221cfc492c0dd95fdd53643e710c9f28/src/kiro_crew/shared_crew/admission_entry.py
Locator: Chat prompt payload and admit_chat_turn; collab.py presence; attribution.py sender_line
Finding: 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.
Retrieved: 2026-11-13

Source: https://kiro.dev/changelog/crew/
Locator: November 5: More Coding Agents; Previews You Can Turn On
Finding: 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.
Retrieved: 2026-11-13

## kiro:TEAM-02

Finding: 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.

Verification: sourced
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: 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

The scoped first-party source pass does not establish project_roles, task_roles, membership, provisioning, unauthorized_access, revocation. No hands-on scenario was run.

Source: https://kiro.dev/docs/getting-started/authentication.md
Locator: Provider table; Organization login
Finding: IDE, CLI, Web and Mobile support IAM Identity Center or organization identity providers such as Okta/Entra. CLI also has a CI/headless API-key path.
Retrieved: 2026-11-07

Source: https://kiro.dev/pricing/
Locator: Teams; shared credit pools and enterprise controls
Finding: 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.
Retrieved: 2026-11-13

## kiro:TEAM-03

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Kiro CLI; Kiro IDE
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: command, tool, network, secret, approver_identity, lifetime, revoke, tunnels. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://kiro.dev/docs/sandbox.md
Locator: Coverage; platform requirements
Finding: Kiro's optional local sandbox covers shell commands/children and optionally stdio MCP, excluding the agent and built-in file tools.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/privacy-and-security.md
Locator: Autopilot versus Supervised
Finding: Supervised mode reviews file changes after writes and can revert them; it is explicitly not a security boundary.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/crew/features/agent-backends.md
Locator: Preview selector; Available backends; Constraints
Finding: 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.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/crew/features/task-runner.md
Locator: Loop; Task IDs; Recovery; Approval gates; Dependencies
Finding: 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.
Retrieved: 2026-11-07

## kiro:TEAM-05

Finding: IDE supervised mode shows agent-generated file changes for review. Turn-completion review must be distinguished from a merge/deployment authorization gate.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Kiro IDE; Kiro CLI; Kiro Web; Kiro mobile preview; Kiro Crew
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: pending_reviews, evidence_navigation, comments, request_changes, effort, missed_evidence, keyboard, narrow_screen, context_switching, roles, retained_context. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://kiro.dev/docs/privacy-and-security.md
Locator: Supervised mode; File changes
Finding: IDE supervised mode presents agent file changes for human review and approval, but is explicitly not a sandbox or access-control boundary.
Retrieved: 2026-11-07

## kiro:SHIP-02

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Kiro CLI; Kiro IDE; Kiro Web
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://kiro.dev/docs/specs.md
Locator: Capability matrix; core structure; task execution
Finding: Specs create requirements/design/tasks files and schedule independent tasks in dependency waves; correctness testing and mobile parity have explicit limits.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/crew/features/task-runner.md
Locator: Loop; Task IDs; Recovery; Approval gates; Dependencies
Finding: 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.
Retrieved: 2026-11-07

## kiro:SHIP-03

Finding: The Web spec flow implements tasks and opens a PR or merge request, with later feedback updates.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Kiro CLI; Kiro IDE; Kiro Web
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://kiro.dev/docs/specs.md
Locator: Capability matrix; core structure; task execution
Finding: Specs create requirements/design/tasks files and schedule independent tasks in dependency waves; correctness testing and mobile parity have explicit limits.
Retrieved: 2026-11-07

## kiro:SHIP-04

Finding: Kiro Web explicitly says it never merges changes automatically; the user reviews before the default branch is changed.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Kiro Web
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://kiro.dev/docs/web.md
Locator: Prerequisites; modes; features
Finding: Web is a paid-plan cloud client with interactive, Spec and autonomous modes, cron schedules and a documented no-auto-merge boundary.
Retrieved: 2026-11-07

## kiro:SHIP-05

Finding: Per-step commits and Git log/diff state feed later step prompts. A failed independent review reverts the step commit before retry. Rejecting supervised changes reverts files to their pre-turn state according to the guide.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Kiro IDE
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: commit_links, pr_links, build_links, deployment_links, delivery_status, stale_approval_invalidation. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://kiro.dev/docs/privacy-and-security.md
Locator: Autopilot versus Supervised
Finding: Supervised mode reviews file changes after writes and can revert them; it is explicitly not a security boundary.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/crew/features/task-runner.md
Locator: Loop; Task IDs; Recovery; Approval gates; Dependencies
Finding: 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.
Retrieved: 2026-11-07

## kiro:OWN-01

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Kiro IDE; Kiro CLI; Kiro Web; Kiro mobile preview; Kiro Crew
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://kiro.dev/license/
Locator: Application license; Open-source attribution
Finding: 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.
Retrieved: 2026-11-07

## kiro:OWN-02

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Kiro IDE; Kiro CLI; Kiro Web; Kiro mobile preview; Kiro Crew
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: export, import, formats, cancellation, account_independence. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://kiro.dev/docs/memory.md
Locator: Storage; Access controls; Subagent scope
Finding: 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.
Retrieved: 2026-11-07

Source: https://kiro.dev/docs/crew/running-24-7.md
Locator: Docker; Remote host; Persistent state
Finding: 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.
Retrieved: 2026-11-07

## kiro:OWN-03

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Kiro IDE; Kiro CLI; Kiro Web; Kiro mobile preview; Kiro Crew
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: prompts, credentials, logs, artifacts, deletion, residency, subprocessors, consent_prompt. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://kiro.dev/docs/privacy-and-security/data-protection.md
Locator: Data collection; Retention; Opt out
Finding: 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.
Retrieved: 2026-11-07

## kiro:OWN-04

Finding: 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.

Verification: sourced
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: 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

The scoped first-party source pass does not establish currency, seat_minimum, workspace_fees, credits, trial. No hands-on scenario was run.

Source: https://kiro.dev/docs/cloud-sessions.md
Locator: How sessions work; prerequisites; client matrix
Finding: 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.
Retrieved: 2026-11-07

Source: https://kiro.dev/pricing/
Locator: Plan cards; pooling; trial FAQ checked 7 November 2026
Finding: Free has fifty credits; paid individual tiers and pooled team seats differ in included credits. Add-ons cost $0.04/credit and taxes are excluded.
Retrieved: 2026-11-07

Source: https://kiro.dev/changelog/crew/
Locator: November 5: More Coding Agents; Previews You Can Turn On
Finding: 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.
Retrieved: 2026-11-13

## kiro:OWN-06

Finding: Mobile is TestFlight early access, separate from IDE/CLI/Web availability.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Kiro mobile preview
Version: Public sources checked 2026-11-07; no installed release tested

Availability and support: first-party sources in this pass did not establish release_stage, support, response_commitments, release_activity, 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.

Source: https://kiro.dev/docs/mobile.md
Locator: Early access; cloud-session links
Finding: Kiro iOS is early access through TestFlight; detailed mobile documentation is still pending.
Retrieved: 2026-11-07

## kiro:OWN-08

Finding: 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.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Kiro CLI; Kiro Crew; Kiro IDE; Kiro mobile preview; Kiro Web
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://kiro.dev/docs/web.md
Locator: Prerequisites; modes; features
Finding: Web is a paid-plan cloud client with interactive, Spec and autonomous modes, cron schedules and a documented no-auto-merge boundary.
Retrieved: 2026-11-07

Source: https://kiro.dev/pricing/
Locator: Plan cards; pooling; trial FAQ checked 7 November 2026
Finding: Free has fifty credits; paid individual tiers and pooled team seats differ in included credits. Add-ons cost $0.04/credit and taxes are excluded.
Retrieved: 2026-11-07

## kiro:OWN-09

Finding: Credit pricing is public but model choice and work complexity prevent deriving a fixed per-task cost.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Kiro CLI; Kiro Crew; Kiro IDE; Kiro mobile preview; Kiro Web
Version: Public sources checked 2026-11-07; no installed release tested

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.

Source: https://kiro.dev/pricing/
Locator: Plan cards; pooling; trial FAQ checked 7 November 2026
Finding: Free has fifty credits; paid individual tiers and pooled team seats differ in included credits. Add-ons cost $0.04/credit and taxes are excluded.
Retrieved: 2026-11-07