Open History to see the last commit
1# Kiro
2
3T3 Code runs the [Kiro CLI](https://kiro.dev/docs/cli/) as an agent, using your own Kiro account,
4custom agents, steering, hooks, and MCP configuration.
5
6## Set Up Kiro
7
81. Install the Kiro CLI on the machine running the T3 Code server. On macOS or Linux, run
9 `curl -fsSL https://cli.kiro.dev/install | bash`. On Windows 11, run
10 `irm 'https://cli.kiro.dev/install.ps1' | iex` in PowerShell. Kiro's
11 [installation guide](https://kiro.dev/docs/getting-started/installation/) lists other options.
122. Run `kiro-cli login` once in a terminal. Kiro Pro and higher plans can instead set an API key as
13 `KIRO_API_KEY` in the Kiro provider's environment variables.
143. Open **Settings → Providers**, enable Kiro, and refresh it.
15
16If `kiro-cli` is not on the server's `PATH`, set its **Binary path**. On macOS and Linux, the
17installer usually puts it in `~/.local/bin`. T3 Code starts Kiro's CLI V3 engine, so a Kiro CLI
18that cannot run V3 will not start.
19
20## Models
21
22The model picker lists the models your Kiro account can use once Kiro is signed in. New threads
23start on your Kiro default model: `auto`, which lets Kiro choose, unless your account or
24organization sets another. A model your account cannot use stops the turn with an error instead of
25running on another model.
26
27Models with adjustable reasoning effort, such as recent Claude Opus and Sonnet models and GPT-5.6,
28show a **Reasoning** setting with only the levels Kiro offers for that model. Your default model and
29models without effort control run at Kiro's own setting.
30
31## Agents
32
33The **Agent** setting next to the model picks the
34[Kiro agent](https://kiro.dev/docs/custom-agents/) a thread runs as: Kiro's built-in agents such as
35Spec and Plan, and your own agents in `~/.kiro/agents`. Agents in a project's `.kiro/agents` are
36not listed yet. Refresh the Kiro provider after adding or removing an agent.
37
38The thread's model still applies when an agent sets its own `model`. An agent that was removed
39leaves the thread on Kiro's current agent.
40
41## Permission Modes
42
43Kiro asks before tool calls such as writes and commands, and T3 Code answers by the permission mode:
44
45- **Supervised** sends those requests to you. Kiro's Autopilot is off, so Kiro also asks you to
46 review the turn's file changes before it finishes.
47- **Full access** approves them without asking you. Autopilot stays on, so there is no review step.
48
49Kiro offers no **Auto** or **Auto-accept edits**. Approvals offer only the choices Kiro sends. Kiro's
50**Always allow** saves a rule for the whole workspace, so T3 Code shows it only when Kiro offers no
51one-time choice.
52
53## Steering, Forks and Compaction
54
55- A message you send while Kiro is working joins the running turn. Kiro reads it once its current
56 step or tool call finishes. A message with images stops the turn and starts a new one with it.
57- Forking a thread from a message gives the fork Kiro's own copy of the conversation up to that
58 message.
59- `/compact` uses Kiro's own compaction. Kiro also compacts on its own as the conversation fills its
60 context.