An AI dev workspace that outlives your terminal session

What it does Kiro Crew is a locally hosted gateway for AI development agents that maintains state, memory, and skills across conversations. It wraps a desktop app, web dashboard, CLI, and messaging integrations around a single runtime so you can start a task in one place and continue it in another. The system runs scheduled jobs, delegates work to subagents, and applies lessons learned from past failures to future sessions.

The interesting bit The architecture treats persistence as a first-class feature rather than a bolt-on: corrections you make in chat become durable workspace-scoped lessons, repeated workflows crystallize into reusable skills, and the gateway coordinates approvals, sandboxing, and audit policies across every surface. It is essentially an operating environment for agents that tries to stop them from being amnesic toddlers.

Key highlights

• Runs entirely on your own hardware (Mac, Linux, Windows via source, or container) with no mandatory cloud dependency
• Self-learning memory that turns corrections and task failures into durable, workspace-scoped lessons
• Unattended autonomy: scheduled recurring jobs, reactive webhooks, and long-running checkpointed tasks that validate and retry without a human at the terminal
• Delegation via isolated subagents for parallel research or execution that report back to parent sessions
• Defense-in-depth governance with tool approvals, OS sandboxing, sensitive-path checks, credential redaction, and audit events

Caveats

• Windows has no native desktop build yet; you run the Gateway from source and use the browser dashboard
• The entire runtime currently lives on a single host, so scaling beyond one machine is not yet supported
• Model inference routes through kiro-cli, meaning you work within Kiro’s account and model configuration rather than dropping in arbitrary API keys

Verdict Developers who want a locally hosted, long-running agent with memory and scheduling should look here; those looking for a simple, stateless chat wrapper or who need immediate multi-host distribution should wait.