Kiro CLI 2.29.0 adds cross-session Memory to local V3 sessions

Kiro's command-line coding assistant can now remember project context from one chat to the next. According to the company's changelog entry dated October 9, 2026, Kiro CLI 2.29.0 introduces Memory for local V3 sessions, so Kiro can carry useful context from a user's work, such as a repository's commands and conventions, into later chats instead of asking users to restate it.

Kiro gives one example. If it learns while debugging that a repository's integration tests fail until the local database is seeded, a later session can seed the database first instead of rediscovering the cause. That is the company's illustration, not a measured result, and the changelog gives no data on how often recall is correct.

Users stay in control through a setting. In a local V3 session, typing /memories and choosing config offers read & write, read only, or off. Read only uses existing memories with no changes or automatic updates, and off stops Kiro from using or changing memories. Changes to this access setting apply from the next session.

With read & write, an Automatic memory updates option lets Kiro create and refine memories, including after a session ends. Changes to that option take effect immediately. When Kiro draws on a memory, the chat shows a Memory entry with command=get and the memory's title while it works, which gives users a visible cue.

Two guardrails are described. In a workspace the user has not trusted, Kiro can read memories but cannot add, change or delete them. The list view, opened by choosing list, lets users search, preview and open stored memories, but it is read-only; fixing or deleting a memory is done by asking Kiro in the chat.

Why it matters: coding agents lose time and user patience when each session starts cold, and persistent memory is a common answer. It also raises questions about what gets stored and how stale entries are corrected. The changelog addresses the second with the chat-based fix and delete route and the read-only mode, but it does not say where memories are stored or how they are retained, so those points remain unconfirmed.

This account rests on a single credible source, Kiro's own changelog. A search found no independent reporting or testing of the 2.29.0 feature; a third-party release tracker only summarizes the same changelog.

Revised 16 October 2026: Guth re-read the original sources and rewrote this article. The earlier version remains available as revision 1.