Skip to main content

Kiro CLI

Install, authenticate, and resume Amazon's Kiro CLI inside Daintree, including the chat --resume path and why a moved project needs the resume picker.

Reviewed

Kiro CLI

Kiro is Amazon's spec-driven coding agent. It runs as a process in its own Daintree terminal panel with full PTY emulation, like every other built-in agent.

Commandkiro-cli
Shortcut— (assignable in Keyboard settings)
RenderingAlt-screen — Kiro draws its own full-screen TUI
Resumekiro-cli chat --resume (scoped to the folder, no session ID)
Quit command/quit
Permission bypass--trust-all-tools
PlatformsmacOS and Linux

Install & Authenticate

curl -fsSL https://cli.kiro.dev/install | bash

Run kiro-cli once from your terminal to authenticate. Kiro supports AWS SSO, AWS Builder ID, and GitHub or Google social login. For headless or SSH use, kiro-cli login --use-device-flow completes the SSO flow without a local browser.

Note
Daintree detects Kiro's auth by looking for the AWS SSO token at ~/.aws/sso/cache/kiro-auth-token.json. Sign in with AWS Builder ID or a social provider instead and Kiro keeps that token in the OS keychain, so Daintree shows a "Needs login" badge even though you're already signed in. The agent still launches and runs fine.

Resuming Sessions

Kiro resumes by folder rather than by session ID, so Daintree relaunches it as kiro-cli chat --resume and Kiro reopens the most recent conversation for that working directory. Nothing needs to be captured on shutdown, which is why the resume works even after a crash.

The catch is where those conversations live. Kiro keeps them in a home-directory SQLite store keyed by the absolute workspace path, not in the project folder. Move or rename a project and chat --resume at the new path starts fresh — the history is still on disk, and kiro-cli chat --resume-picker reaches it. Daintree flags this in the relocation preview rather than silently losing the thread. See Session Management for what else survives a move.

Launch flags, custom presets and display titles are covered in Agent Presets. What the working, waiting and exited badges on a running agent mean is covered in Agent States.

Tip
If kiro-cli isn't detected after install, confirm it's on your PATH (which kiro-cli), then restart Daintree.