Skip to content

Kiro CLI Setup ​

Kiro CLI is Amazon's AI coding CLI with built-in ACP support — no adapter needed.

Install and Configure ​

  1. Install Kiro CLI by following the instructions at kiro.dev. Once installed, the binary is named kiro-cli.

  2. Find the installation path:

bash
which kiro-cli
# Example output: /usr/local/bin/kiro-cli
cmd
where.exe kiro-cli
# Example output: C:\Users\Username\.kiro\bin\kiro-cli.exe
  1. Open Settings → Agent Console. Switch to the Kiro CLI section.

  2. Configure:

    • Path: kiro-cli (works in many cases via login shell PATH; or set the full path from step 2, or click Auto-detect)
    • Arguments: acp (set by default)

Authentication ​

Run Kiro CLI in your terminal to trigger its sign-in flow:

bash
kiro-cli

Follow the browser-based login. That's all — the Kiro CLI section has no API key field; Agent Console reuses the cached credential from your local Kiro config.

TIP

Kiro CLI natively supports ACP, so no additional adapter is required. Just point Agent Console at the kiro-cli binary and you're set.

Choose the engine ​

Kiro CLI has two engines. Agent Console uses the newer one, V3, unless you pick otherwise. Some Kiro agent configs only load on V3.

  1. In the Kiro CLI section, Kiro CLI engine has three choices: Default (V3), V3 and V2 (legacy). Leave it on Default (V3) to follow Agent Console's default. V2 (legacy) is the older engine: pick it if a chat won't start on V3. The engine you pick here is the one that runs, even if Kiro CLI's own engine setting says otherwise. If you run Kiro through a custom agent instead (for example one per Kiro profile), the same setting appears on that custom agent whenever its path is kiro-cli, and it starts on Default (V3) too.
  2. Keep your arguments as they are, for example acp --agent my-agent. V3 doesn't accept --agent, --model or --effort on launch, so Agent Console passes them to each new chat instead. --trust-all-tools and --trust-tools are dropped; V3 uses its own permission rules. In a V3 chat, Always allow asks whether to remember the choice for this vault or this chat (see Permission Controls).
  3. A change applies to chats you start after it. Open chats keep the engine they started on. To see which engine a chat runs on, hover over the chat header.

Older versions of Kiro CLI don't have V3. You don't have to update to keep working: on Default (V3), Agent Console starts the chat on V2 instead, and a tip at the top of the chat lists what V3 adds once you run kiro-cli update. Select Got it to hide the tip; hovering the chat header still says why the chat runs on V2. If you picked V3 by name, the chat shows Kiro CLI needs an update instead of connecting. Run kiro-cli update, or set Kiro CLI engine to V2 (legacy) or Default (V3), then send your message again.

Each saved chat remembers the engine it ran on. A V2 chat opens fine on V3. V2 can't open a chat that ran on V3, so if you reopen one after switching to V2, Agent Console starts a new session, says why at the top of the chat, and continues from your saved messages. If your Kiro CLI is too old for V3, the note at the top of the chat says so, and running kiro-cli update brings back V3 for new chats. Before Agent Console 2.5.0, a chat set to V2 (legacy) could quietly run on V3 if Kiro CLI's own engine setting was V3. Reopening one of those on V2 works the same way: a new session that continues from your saved messages.

With V3, your agent's hooks (start, prompt and stop) run in Agent Console chats too. MCP servers that need sign-in prompt you as soon as Kiro reports them, and servers that fail to start are listed at the top of the chat (see MCP Tools).

On V2, starting a new chat in the same tab restarts Kiro, so it takes a few seconds longer. That keeps each tab to one copy of your MCP servers. Rename with AI isn't available on V2 for the same reason. V3 has neither limit.

Pick the model, the effort level and other Kiro options (such as Autopilot or Supervised) from the dropdowns below the message box. The effort dropdown only shows for models that support it. Agent Console remembers your model and effort picks for the next chat. If a model you saved is no longer offered, the chat switches to the first model on the list and tells you. When you reopen an earlier chat from history or after a restart, it keeps the model, effort and mode it was using.

Verify Setup ​

  1. Click the robot icon in the ribbon or use the command palette: "Open chat"
  2. Switch to Kiro CLI from the agent dropdown in the chat header
  3. Try sending a message to verify the connection

Having issues? See Troubleshooting.

Released under the Apache 2.0 License.