Kiro's unified harness explains how one agent engine can serve IDE, CLI, web, and mobile. Kiro Crew moves one level up: work that persists over time, wakes on schedules, carries memory and skills, coordinates multiple agents, and connects to applications.
Long-running work changes the failure model. A single interactive session can rely on immediate user correction; a scheduled crew needs explicit state, checkpoints, retry limits, ownership, and approval gates before external actions. Memory must distinguish durable facts from temporary execution state, and every agent needs a defined role and permission set.
The useful product series is therefore engine, surface, and operation. The harness standardizes execution; Crew organizes jobs and collaboration; owner-facing clients supervise progress and approve irreversible steps. Persistence is valuable only when the system can explain what is running, why it woke, what it changed, and how to stop it.