Kiro CLI: Memory Across Chat Sessions

Kiro CLI 2.29.0 introduces Memory for local V3 sessions, so Kiro can carry useful context from your work, such as a repository's commands and conventions, into later chat sessions instead of asking you to restate it.

[Carry context across chat sessions with Memory] Kiro can now learn useful context from your work and recall it when a later session needs it. For example, if Kiro learns while debugging that a repository's integration tests fail until the local database is seeded, a later session can seed it first instead of rediscovering the cause. When Kiro uses a memory, the chat shows a Memory entry with `command=get` and the memory's title while Kiro is still working.

[Carry context across chat sessions with Memory] In a local V3 session, type `/memories` and select `config` to choose `read & write`, `read only`, or `off`. The `read only` option says "Use existing memories. No changes or automatic updates." `off` stops Kiro from using or changing memories. Access changes apply in your next session. With `read & write`, Automatic memory updates lets Kiro create and refine memories, including after a session ends; changes to that setting apply immediately. In a workspace you have not trusted, Kiro can read memories but cannot add, change, or delete them.

[Improvements] Device flow control by profile: Administrators can turn off device flow sign-in for each Kiro profile. The CLI hides those profiles during device flow login and profile switching, while browser sign-in remains available

[Improvements] Directory agent upgrades: `kiro-cli agent upgrade <dir>` upgrades top-level agent JSON files to the format both V2 and V3 load. Use `--dry-run` to preview changes without writing, or `--no-backup` to skip the default backups

[Improvements] V2 TUI Hook groups: Hook matchers such as `read` now cover every tool in that group, so a blocking `preToolUse` Hook can stop any tool in the group

[Improvements] V3 ACP sign-in: `kiro-cli acp` now uses your Kiro CLI login by default. Pass `--auth-method=client` when the connecting client should handle sign-in

[Improvements] V3 MCP server startup: Custom agents now start only `mcp.json` servers allowed by their tool settings

[Carry context across chat sessions with Memory] Select `list` to search, preview, and open stored memories. The list is read-only; to fix or delete a memory, ask Kiro in the chat.

[Improvements] V2 TUI Hook input: Tool Hooks now receive `tool_tags`, so scripts can check a tool's group

[Improvements] V3 MCP server environments: `stdio` MCP servers now inherit the full agent environment

[Fixes] Classic `fs_write` no longer auto-approves a write when a symlink redirects it outside `allowedPaths`

[Fixes] Classic and V2 model fallback changes take effect in the current session without a restart

[Fixes] V2 and V3 now show the MCP OAuth authorization URL, so you can open it from SSH or tmux sessions

[Fixes] V3 non-interactive runs respect `telemetry.enabled` and `KIRO_DISABLE_TELEMETRY`

[Fixes] V3 `/upgrade-agent` rewrites legacy Hook matchers such as `fs_read` so they fire, and warns when a rewrite widens the match

[Fixes] Knowledge search in Classic and V2 returns one combined result set across all bases, with shared pagination and the requested limit and file type applied across the full search

[Fixes] Fixed an issue that could close V3 sessions under heavy load

[Fixes] V3 custom agents dispatched as subagents now load their own `mcpServers`

[Fixes] V3 resizes images to fit the selected model instead of failing the request

[Fixes] V3 `KIRO_API_KEY` keys minted outside `us-east-1` now authenticate in their home region

[Fixes] V3 resumed sessions keep `UserPromptSubmit` Hook output in the conversation

[Fixes] V3 Stop cancels a prompt sent while MCP servers are still starting

[Fixes] V3 keeps the turn that was ending in the model's history when a new prompt arrives at that moment

[Patches] MCP OAuth sign-in in Classic and V2 now works with servers that require an issuer

[Fixes] V3 offers the effort selector at session start when the default model supports effort

[Fixes] V3 shows a readable retry message when the backend returns a non-JSON error page

[Fixes] V3 manual Steering files load when their slash command appears in the middle of a prompt

[Carry context across chat sessions with Memory] Learn more ->

[Patches] 2.29.1 | Oct 10, 2026