Agents

An agent is a configuration that tells Kiro Crew how to behave: which model to use, what system prompt to follow, which tools it can call, and which MCP servers to spawn. Every session runs under an agent.

Open Customize → Agents. You can:

• View all configured agents
• Edit any agent's model, prompt, and tool list
• Create new agents
• Switch the active agent for a session
• Reset a managed agent to its defaults

Kiro Crew ships with a kirocrew agent that includes:

• Model — auto (uses the model configured in kiro-cli)
• System prompt — general-purpose assistant behavior
• MCP servers — kirocrew-core (spawn, learn, task, wait, messaging) and kirocrew-cron (scheduling tools)
• Tools — full tool access (file read/write, shell, web, MCP)

This is what runs when you don't specify an agent. It covers most use cases.

From the Agents panel, click Create. Set:

• Name — identifier used to reference the agent
• Model — which LLM to use (or auto for the default)
• Prompt — the system prompt that shapes behavior
• Tools — which tools the agent can call

For file-based configuration, create a JSON file:

{
  "name": "reviewer",
  "description": "Independent code reviewer",
  "model": "auto",
  "prompt": "You are a code reviewer. Focus on correctness, security, and clarity.",
  "tools": ["fs_read", "grep"]
}

Place it under ~/.kiro/agents/ or reference it from the dashboard.

Control how the agent gets tool permission. Set globally from Settings → Security or per-session with the Autopilot toggle.

Denied commands and sensitive-path blocks always apply, even in Autopilot.

• Narrower tool access — a "reviewer" agent that can only read files, not write them
• Different prompt — an agent tuned for a specific domain (data analysis, writing, ops)
• Different model — use a specific model for certain types of work
• Restricted scope — limit what the agent can do for safety-sensitive workflows

An agent can follow a parent template. For each capability the template defines, the agent chooses Inherited, Override, or Removed. When the template changes, the agent sees the incoming changes and can review them before applying.

If you customize an agent based on a shared template, Kiro Crew lets you fork a private copy so your changes stay independent of future template updates.

Enable Settings → Developer → Feature Previews → Crewmates, then open Crewmates in the sidebar to reach the Crewmates page and its crewmate threads. Each crewmate has a display name, private memory, workspace, agent template, default model, and optional triggers. Its stable id continues to drive schedules and CLI commands when its display name changes.

In Customize → Agents, select Edit avatar on a crewmate. Choose a Ghost face, upload a Picture, or pick from the Library. The Reactions pane sets motion and optional sound for Working, Finished, and Failed states.

Opening a crewmate's thread can show one card, read from the crewmate's own work ledger, without adding a chat turn or calling the model.

• While a goal is in flight, a resume card shows the goal, what is finished, running, or waiting on you, and one next step.
• When no goal is in flight and the thread is new or has been idle for six hours or more, a welcome card recaps the goals the crewmate left open and its recent sessions.

A card you saw moments ago is not shown again on the next open, and no card appears while the crewmate is mid-turn.

The pill at the top of a crewmate's thread says what it is doing now. Select it to open the Profile card, which has four tabs:

• Profile summarizes the crewmate and leads to its Memory, Workspace, and Notes. It also holds the crewmate's own Permissions, Model, and Reasoning effort settings, which apply to every chat with that crewmate.
• Schedules lists what wakes the crewmate on its own. New schedule here creates a schedule that runs as that crewmate, bound to its private memory.
• Sessions lists the sessions the crewmate is driving.
• Goals is a placeholder. Goals are not available yet.

The pencil on the card opens Edit crewmate.

By default the roster lists crewmates you have chatted with or starred. The crewmate you have open stays listed while the search box is empty. Typing a search reaches every crewmate, including hidden ones, and the search alone decides what shows.

With a thread open, the roster folds into a switcher of faces in the thread header. Choose Show the full roster to bring the roster column back. The roster's status view shows presence, patrol state, next wake, and why a loop stopped.

A crewmate's side panel has a Dashboard tab and the Workspace file browser. The Dashboard tab shows the page or live view the crewmate publishes. With the Dynamic Dashboard preview on, it shows the crewmate's dynamic dashboard instead. Read the crewmate's notes from the Profile card.

The page-header Cloud control manages one crew-wide deployment, not one crewmate. Its actions lead to Settings → Remote Crew. On desktop, enable Crew Companion from Apps → Library to show one crewmate avatar across your displays.

Choose + → New team in the roster header to create one. Opening a team shows crewmate status, questions waiting for you, and recent activity. Use Edit team to rename it, change membership, or delete it. Deleting a team keeps its crewmates and their chats.

To create a crewmate from a template, see Agent templates.

Turn on Settings → Developer → Feature Previews → Dynamic Dashboard to fill a crewmate's Dashboard tab with a page built from its own record. The tab shows a project report by default. Twelve pages ship with Kiro Crew, including a standup, a roadmap, and a kanban of the crewmate's work.

To change the page, ask the crewmate in chat. It previews the page you asked for and applies it. It can choose only from the shipped pages and cannot write a page of its own.

Every figure on a page comes from one of two places: a fold of the crewmate's crew log, or a value the crewmate wrote itself, which carries the tag crewmate wrote this. A cost nobody measured shows a dash rather than 0.

The same preview adds a status row above the composer and an All Dashboards page. Its Automatic cards for all sessions switch keeps a summary of each session's recent work and next steps.

With the preview off, the Dashboard tab keeps showing the page or live view the crewmate publishes.