Kiro vs HagiCode: Features and Comparison

HagiCode is a proposal-driven AI coding workbench that turns a request into a reviewable proposal, runs it through agent CLIs such as Claude Code, Codex and GitHub Copilot, and keeps the outcome as team knowledge.

Kiro is the terminal agent in the Kiro family, running on Kiro credits; HagiCode is a workbench that can run it as an executor. This page compares features, pricing and when Kiro alone is enough.

Install HagiCode Desktop

English2026-10-16

Short answer

Kiro is Kiro's terminal agent: you run kiro-cli in a project, and it reads your .kiro/ steering files and MCP config, then edits code and runs commands using your Kiro plan. HagiCode is a desktop and web workbench that launches kiro-cli as one of its Agent CLIs, adding parallel sessions, proposals and commits. It does not replace Kiro and it does not sell Kiro credits.

If you already work in Kiro and want its agents, steering and hooks in a terminal, stay with Kiro alone. Add HagiCode when you run several tasks at once or want a proposal workflow independent of Kiro's own.

Kiro vs HagiCode at a glance

DimensionKiroHagiCode
What it is

Terminal agent from Kiro; shares core capabilities with other Kiro surfaces

Desktop and web AI programming workbench that drives Agent CLIs you install

Interface and platforms

Terminal chat started with kiro-cli; macOS, Linux, Windows 11 (PowerShell)

Desktop app for Windows, macOS, Linux; Docker Compose container; Microsoft Store edition

Pricing and licensing

Part of Kiro plans: Free (50 credits/month), Pro $20, Pro+ $40, Power $200 per month, as of October 2026

Desktop and Container free; Store edition free with optional one-time TurboEngine purchase

Model and provider access

Built on Claude models; an Auto agent picks, and /model lets you choose per chat

Hosts no models; uses whatever kiro-cli is signed in with, so cost stays in Kiro credits

Parallel work

One chat per terminal; custom agents; cloud sessions keep running after you disconnect

Several concurrent sessions across repos, managed from an Agents view

Spec and planning workflow

Plan agent explores code without modifying it; steering files carry team rules

OpenSpec proposals: propose, validate, apply, archive; 3 concurrent on free editions, 32 with TurboEngine

Git and commit handling

Runs shell and Git commands; headless mode can open pull requests in pipelines

AI-composed commits, Git management, GitHub integration, embedded Code Server editor

Setup effort

curl -fsSL https://cli.kiro.dev/install | bash, then browser sign-in

Install HagiCode Desktop, with a working, signed-in kiro-cli already on the machine

Best for

Developers on Kiro plans who want agents, steering and hooks in the terminal or CI

Developers running several tasks or repos who want a GUI and a spec discipline

What Kiro does well

Custom agents with scoped permissions

You can define agents with pre-set prompts and tool permissions, then start one with kiro-cli --agent <name>. That is a practical way to give a reviewer agent read-only tools and a builder agent more room, all from files.

Steering and shared project config

The CLI reads steering files and MCP configuration from the project's .kiro/ folder, the same place other Kiro surfaces use, so team rules carry across the IDE and terminal. Agent skills, a knowledge base and code intelligence build on that.

Hooks, plan agent and cloud sessions

Hooks automate steps before and after commands, a plan agent explores code without editing it, and cloud sessions keep running after you disconnect. Together they suit longer tasks you want to leave running.

Headless mode and ACP

Headless mode runs prompts non-interactively in CI/CD with API keys, for example to troubleshoot a failing build or open a pull request. ACP support lets compatible IDEs drive the CLI. Sign-in works with Google, GitHub, AWS Builder ID or an organisation identity.

When to choose Kiro, and when to choose HagiCode

Stay with Kiro when

  • You already use Kiro and want its agents, steering files and hooks in the terminal.
  • You want custom agents with tightly scoped tool permissions defined in files.
  • You need headless runs in CI/CD with API keys.
  • You want long tasks to keep running in cloud sessions after you disconnect.
  • You work on one task at a time and want no extra application.

Reach for HagiCode when

  • You run several Kiro tasks across repositories and want the sessions side by side.
  • You want an OpenSpec proposal, validation and archive step, and the proposal lifecycle is not tied to one vendor.
  • You prefer to review tool calls and diffs in a GUI, with AI-composed commits and Code Server.
  • You want Vault notes and Monospecs for shared context across Kiro sessions and repositories.
  • You mix Agent CLIs (Kiro, Claude Code, Codex and others) and want one workspace.

Using Kiro together with HagiCode

HagiCode starts the kiro-cli you already installed, in its ACP mode (kiro-cli acp), and shows the session in its own interface. Your install, sign-in and Kiro credits stay as they were.

Nothing is locked in: your repositories stay ordinary Git repositories and you can run kiro-cli in a terminal at any time.

  • 1. Install Kiro (curl -fsSL https://cli.kiro.dev/install | bash; for Windows see the installation page on kiro.dev) and sign in; kiro-cli login re-authenticates.
  • 2. Install HagiCode Desktop (free) for Windows, macOS or Linux.
  • 3. In HagiCode, choose Kiro as the Agent CLI for a session.
  • 4. Open a repository and start a session or an OpenSpec proposal.
  • 5. Expect Kiro models and credit usage as before; HagiCode adds workflow around them.
  • 6. To go back to plain Kiro, open a terminal in the same repository and run kiro-cli.

What HagiCode adds on top of any agent

Parallel sessions and Agents management

Kiro gives you one chat per terminal. HagiCode can keep several Kiro sessions running across repositories and list them in one Agents view.

OpenSpec proposals

Kiro has steering files for standing rules. An OpenSpec proposal covers a single change: written, validated, applied and archived, so you keep the reasoning behind it.

AI commits and Code Server

HagiCode composes the commit message from what Kiro changed, and the embedded Code Server lets you check the edits without leaving the workbench.

Monospecs and Vault

Monospecs lets a Kiro session span several repositories; Vault stores notes that outlast one session.

One tool-call view and optional TokenMonitor

Kiro's tool calls show in the same layout as other agents' calls, and an optional TokenMonitor can show usage in the status bar. Kiro credits and billing are unchanged.

The bottom line

  • Kiro is a capable terminal agent with custom agents, steering, hooks and headless mode; for one terminal and one task it is enough alone.
  • HagiCode is a workbench layer that runs kiro-cli underneath, adding sessions, proposals and commits rather than credits or models.
  • Use Kiro directly for CI; use HagiCode for parallel, reviewed work.

Frequently asked questions

Is Kiro free?

Kiro has a free plan with 50 credits per month, plus Pro ($20), Pro+ ($40) and Power ($200) plans per month, as of October 2026. The CLI has no separate pricing and uses your Kiro plan; see kiro.dev/pricing.

How do I install Kiro?

On macOS and Linux run `curl -fsSL https://cli.kiro.dev/install | bash`, then start `kiro-cli` and sign in through the browser. Windows 11 (PowerShell) is supported; see the installation page on kiro.dev for the command.

Can I use Kiro with HagiCode?

Yes. Install `kiro-cli` and sign in, then choose Kiro as the Agent CLI in HagiCode. HagiCode accepts only `kiro-cli` binaries, not the generic `kiro` launcher.

Does HagiCode replace Kiro?

No. HagiCode runs Kiro as its executor and adds sessions, proposals, commits and a GUI around it.

Kiro vs HagiCode: which should I pick?

Use Kiro alone for single-terminal work, custom agents and CI. Add HagiCode for parallel sessions, OpenSpec proposals and a visual workspace.

Desktop

Localized AI code assistant, privacy protection, enhanced efficiency