Keep work moving

Kiro Crew is the persistent, open source development workspace that remembers your context, learns how you work, and coordinates across your unique tools and workflows, so you come back to progress instead of another workflow to restart.

Loading image...Kiro Crew session view: a sessions list on the left, an agent thread weighing title options in the middle, and a merged pull request on the right with 15 changed files and all checks passed

Persistent and self-improving

Memory, lessons, and skills carry across sessions, so your crew evolves to fit your work. Inspect, edit, or remove what your crew carries forward.

Works while you’re away

Cron schedules, webhook triggers, and heartbeat monitors keep your agent crews productive online or off. Long-running tasks move through checkpoints, validation, and retries automatically. Fold in your unique workflows and tools with Apps.

7 layers of defense

OS sandboxing, denied command patterns, bash blocking, input/output validation, sensitive path protection, credential redaction, and signed audit logs. Verify every layer: it’s open source.

Learns how you work

Kiro Crew remembers context across sessions, turns corrections into lasting lessons, and evolves from your work patterns so it just keeps getting better.

Loading image...Kiro Crew memory settings on the Audit tab, listing create, update, conflict skip, and conflict retire events with the memory key, details, and timestamp for each
Loading image...
list of installable skills

Control what your crew learns

Corrections become durable lessons, and repeated workflows get synthesized into named skills. Lessons and skills are Markdown files you can inspect, edit, scope to a workspace, or delete — and they use the same steering file format as the IDE and CLI.

Loading image...
knowledge graph showing relationships between nouns

Knowledge graph with search

Architectural decisions, coding preferences, and project context land in a knowledge graph backed by vector embeddings and full-text search, so the agent retrieves what's relevant instead of re-reading everything.

Loading image...
chat with memories referenced

Memory that survives restarts

Active projects and working context persist across sessions and restarts. Long-running work checkpoints and resumes, so you're not re-prompting your way back to where you left off.

Keeps working while you’re away

Agents work in parallel with scheduled jobs, webhooks, and heartbeats, so your crew runs tasks end to end and discovers work worth doing even when you step away.

Loading image...Kiro Crew Schedule page listing two cron jobs with their timezone-aware schedules, status, last and next run times, and run, continue, pause, and delete actions

Issues

Scans your backlog for work that's actionable now (reproducible bugs, stale issues, missing tests) and picks up what it can finish without waiting to be asked.

Codebase

Watches for drift: dependencies falling behind, dead branches, failing test suites, docs that no longer match the code.

CI/CD

Reacts to pipeline and deployment events. A failed build or a broken deploy becomes a session with the logs already in context.

Schedules

Timezone-aware cron jobs for recurring work. Per-job timeouts, jitter to avoid thundering herds, and skip dates for maintenance windows. Every run is logged and checkpointed.

Webhooks

Point external events at your agent over authenticated endpoints and it starts working on arrival.

Heartbeat

Watches state changes in your PRs, deployments, and pipelines, triggering work when conditions are met, so the agent stays in the loop without polling.

Apps and extensibility

Purpose-built interfaces for work that doesn't belong in chat. Wrap agents, skills, schedules, and integrations in a custom UI to automate your day without chatting every instruction.

Loading image...The Issue Radar app showing filters and a list of open pull requests with readiness labels, next to the selected pull request's AI summary, passing checks, labels, and branch details
typescriptdeploy-monitor/index.tsx
import { defineApp, useAgent } from '@kirocrew/app-sdk' export default defineApp({ name: 'deploy-monitor', skills: ['./skills/deployment-check.md'], schedule: '*/15 * * * *', ui: () => <DeploymentDashboard />, })

Build Apps in TypeScript or Python with the SDK

The App SDK gives you typed bindings for the agent runtime, skill system, and event bus. Define your App’s UI in React (rendered in the dashboard) or expose it headlessly via the CLI. Apps can register their own MCP tools, subscribe to agent events, and persist state between sessions.

Trust and transparency

A workspace with access to your code and tools needs to be inspectable and adaptable. Because Kiro Crew is open source, you can verify every layer rather than take it on faith.

Loading image...Diagram of an agent action entering a stack of eight defense layers at the top and passing through each one before it exits at the bottom
Process sandbox
Tool approval
Sensitive path blocking
Write-protected paths
Denied commands
Suspicious bash patterns
MCP input validation
Output redaction
Credential patterns
URL exfiltration detection
SEL audit logging
Dashboard token auth

We spend less time chasing tickets and more time making engineering decisions.

Akim Akimov

Runs anywhere

Mac. Linux. Windows. Run locally or deploy remotely.

Loading image...

Web dashboard

Multi-session chat, memory explorer, cron manager, app store, and 14 color themes. Responsive on mobile.

Full CLI

kirocrew chat, run, cron, spawn — everything from your terminal. Pipe-friendly and scriptable for CI/CD integration.

Desktop app

Electron wrapper: no Python or npm installation required. Download and run.

Loading image...

Slack integration

Each Slack thread becomes an isolated AI session with full tool access. Your team can interact with Kiro Crew directly in existing channels.

Loading image...
Loading image...

Telegram and Discord

Additional messaging surfaces for teams that live in Discord or Telegram. Same agent crews, same memory, different interface.

Remote instances

Manage Kiro Crew instances running on remote machines over SSH tunnels. Centralize or distribute — your choice.

Built in the open, shaped by the community

Kiro Crew started as an internal side project and grew to 39,000+ builders in less than 6 months with nearly 500 contributors shipping 567 updates at an average pace of 143 weekly commits. We’re governed by a steering committee with public discussions and decision making.

Fully open source

Read the code, audit the security layers, fork it, extend it. No proprietary black boxes. Your agent crew, your rules.

Additive, not a replacement

Compatible with anything built for other open-standards platforms without modification, so you can bring what you have rather than start over. Interoperates with your existing skills, MCP servers, IDE plugins, and CI pipelines.

Built on Kiro

Runs on the Kiro CLI. Shares the same agent protocol (ACP), model support, and .kiro configuration. Invest once, use everywhere.

Kiro Crew does the assembling and the checking so I can do the deciding.

Patrick Stark

Common questions