# Where Kiro CLI stores your chat sessions

> Kiro CLI, formerly Amazon Q Developer CLI, keeps sessions in a local SQLite database and session files. What is documented, and how to resume, save and delete sessions.

Source: https://groundedby.com/agents/kiro (updated 2026-10-29)

Kiro CLI is the terminal agent from AWS, renamed from Amazon Q Developer CLI. Its storage is only partly documented.

## Where sessions are

Kiro's documentation says sessions are kept in a **SQLite database in `~/.kiro/`**. User-filed issues give more detail, which we have not confirmed in Kiro's own docs:

| System | Reported path |
| --- | --- |
| Linux | `~/.local/share/kiro-cli/data.sqlite3` |
| Windows | `%LOCALAPPDATA%\Kiro-Cli\data.sqlite3` |
| Session files | `~/.kiro/sessions/cli/<uuid>.json` and `.jsonl` |

Data from the old Amazon Q CLI lives under `amazon-q/data.sqlite3` in your local data directory.

## Resume, save and delete

```bash
kiro-cli chat --resume
kiro-cli chat --resume-picker
kiro-cli chat --resume-id <id>
kiro-cli chat --list-sessions
kiro-cli chat --delete-session <id>
```

Inside a chat, `/chat save <file>` and `/chat load <file>` save and restore a conversation, and `/sessions clean` tidies old ones.

## Privacy notes

Local sessions do not sync. Sessions started with `--cloud` are stored in your AWS account.

The groundedby [evaluator](/evaluate) does not read Kiro sessions yet.

## Questions

**Is Kiro CLI the same as Amazon Q Developer CLI?**

Yes. Amazon Q Developer CLI was renamed Kiro CLI. Older Q CLI data sits in an amazon-q folder in your local data directory.

**Where exactly does Kiro CLI keep sessions?**

Kiro's docs say only that sessions are kept in a SQLite database in ~/.kiro/. User reports put the database at ~/.local/share/kiro-cli/data.sqlite3 on Linux and %LOCALAPPDATA%\Kiro-Cli\data.sqlite3 on Windows, with session files under ~/.kiro/sessions/cli/.

## Sources

- [Kiro docs, CLI session management](https://kiro.dev/docs/cli/chat/session-management/)
- [Kiro docs, migrating from Amazon Q Developer CLI](https://kiro.dev/docs/upgrade-guides/migrating-from-q/)