Crewmate Teams, Agent Templates, and Quieter Watches

Kiro Crew 0.8.0 spends less of your attention. Monitoring loops can screen quiet checks and wake for reviewer requests, while new cards explain blocked credentials and links. The desktop app bundles Kiro CLI, and folders carry steering into every chat.

Three changes may affect existing setups:

• Crew logs are now on by default. Each chat records a redacted event log that supports session ledgers, conductor work, and Issue Radar. Set KIROCREW_CREW_LOG=0 before starting the Gateway to turn recording off.
• Owner-written MCP auto-approve lists now take effect. Tools listed under autoApprove in mcp.json or an agent file skip both the approval card and Kiro Crew's tool gate. Set mcp.honour_auto_approve to false and restart the Gateway to keep those tools behind the gate. An app's own list is never honored.
• Command cron validation is stricter. Stored commands using brace expansion now fail until edited, imports skip those jobs, and quoted regex intervals such as grep -E '[0-9]{1,3}' are refused. Use a script cron for shell features outside the command-cron subset.

A monitoring loop can screen each check before waking the session. When a loop supplies no rules of its own, turn on Quiet check-ins: wake or skip under Settings → Developer → Feature Previews → Decisions (Jev) to use the shipped default. A quiet check costs no model turn. Pull request watches also wake when a review or comment asks a question or requests a change, and monitoring.max_runtime_secs can raise the default seven-day ceiling to thirty days.

Learn more ->

A removed credential becomes a lock tag that opens a card naming what matched, where it came from, and the safe way to reach it. A blocked link opens a similar card with its destination and rule, plus controls to inspect the full URL, open it once, or allow eligible checks for that host in the current workspace. A separate file-view setting can show files as written while chat and messaging channels remain redacted.

Learn more ->

A folder can name additional steering directories. Chats in that folder and its subfolders inherit those rules on every agent backend, alongside their normal project and agent steering.

Learn more ->

Fresh macOS, Linux, and Windows desktop installs carry a tested Kiro CLI copy. Sign in from the setup screen and start a chat without installing another copy on PATH. An absolute KIROCREW_KIRO_BIN value remains the operator override.

Learn more ->

The Agent templates tab groups installed templates by origin. You can create, duplicate, edit, or delete your own, start a one-off chat, or enroll one as a crewmate; built-in and package templates remain read-only. With the Crew Members preview enabled, choose + → New team to group the roster and see crewmate status, questions waiting for you, and recent activity.

Learn more about agent templates ->

Learn more about crewmate teams ->

An optional Subnet ID pins a built-in EC2 crew launch to one subnet and its VPC after Kiro Crew confirms an egress route. A crew reached through another SSH-connected crew appears as its own top-level tab, indented under the parent whose tunnel carries it. Chains support two hops.

Learn more ->

DeepSeek Harness joins the selectable agent backends when dsh is installed on the Gateway host. The Hooks editor can store Kiro Agent task, file, and manual event names. None fires on its own yet; Test runs them on demand, and each is saved disabled.

Learn more about agent backends ->

Learn more about Hooks ->