Meet Kiro CLI · Kiro CLI Guide

What Kiro CLI is, how it differs from a regular AI chat, and what it can do for you right in the Terminal.

Kiro CLI is an AI development agent that runs in your Terminal. It doesn’t just throw a few sentences back at you — it can actually read files, edit them, run commands, run tests, and take a development task from start to finish.

How it differs from a regular AI chat

A regular AI chat just hands you text; the copying, pasting, and actual doing is all on you. Kiro CLI is different. It has tools at its disposal, so it can do things directly in your environment.

Regular AI chat	Kiro CLI
Gives you code, you paste it yourself	Writes it straight into your files
Teaches you the command, you run it yourself	Actually runs it, with your approval
One question, one answer	Multi-step tasks: plan → execute → verify
No project context	Can read your code, settings, and environment

TIP

The core idea in one line: you say what you want, Kiro plans and acts on its own, and it checks with you first whenever it needs to touch the system. How much you let it through (trust) is up to you — we’ll get into that in detail in the “Tools & Trust” chapter later.

How it differs from Kiro (the GUI)

You may have also heard of Kiro itself — that’s an AI IDE with a graphical interface (a desktop app). Kiro CLI is its Terminal counterpart. The underlying AI capabilities are shared (agent, tools, trust, MCP); the difference is in how you use it.

	Kiro (graphical IDE)	Kiro CLI
Interface	Graphical windows, built-in editor	Plain-text Terminal
Best for	Editing while reading code, visual diffs	Remote SSH, servers, scripts and CI, keyboard-only flow
How it fits your work	Edit and preview inside the IDE	Hooks into your shell, existing toolchains, automation pipelines
Resources	Heavier (GUI)	Lightweight, runs fine on remote machines too

In short: developing locally and want things visual? Open the Kiro IDE. On a server, want to slot it into a script or CI, or you just like living in the Terminal? The CLI is the smoother fit.

TIP

It’s not an either/or. Same account, same agent concepts — you can use both. Using the IDE locally and the CLI when you SSH in is a very common combo.

What it can do for you

Make sense of a project you’ve never seen and explain the architecture to you
Write features, fix bugs, add tests — and actually run them once through
Refactor code, rename a bunch of things at once, apply a consistent style
Operate AWS, look up official docs, debug with a browser (via MCP tools)
Split work into several subtasks running in parallel (subagents), and even juggle several projects at once

Give it a quick spin

If you’ve already got it installed, hop into any project folder and type:

kiro-cli chat

Then describe the task in natural language, like this:

❯ Take a look at what this project does, and list the main entry points

It’ll start reading files, organizing things, and report back to you. It’s that simple.

Check your version

This tutorial matches Kiro CLI 2.6.1. First, take a look at which version you’ve got installed:

kiro-cli --version

When you want to know the latest way to use a command, --help always has the answer:

kiro-cli --help          # see all commands
kiro-cli chat --help     # see all options for a single command
kiro-cli --help-all      # see every subcommand at once

TIP

Make it a habit: when you’re not sure about a flag, run --help first. The examples in this tutorial all line up with 2.6.1, but the official tooling keeps getting updated — --help is the most up-to-the-minute answer you’ve got on hand.

In the next chapter, let’s get installation and updates sorted out.