Kiro CLI 2.29.0 adds configurable memory across local V3 chats

Kiro’s changelog entry dated October 9, 2026, introduces Memory in CLI 2.29.0 for local V3 sessions. The company says the feature lets its coding assistant carry project knowledge—such as repository commands and conventions—from one chat into another.

The controls separate using memories from changing them. Typing /memories and selecting config offers three access modes: read & write, read only and off. Read-only access uses saved memories without changing them or making automatic updates; switching memory off stops both use and modification. Access changes take effect in the next session, not the current one.

Automatic updates have a different timetable. With read-and-write access enabled, the Automatic memory updates option lets Kiro create and refine memories, including after a session ends. Changes to that option apply immediately. In an untrusted workspace, Kiro can still read memories but cannot add, alter or delete them.

There are two ways to see what is being recalled or stored. When Kiro uses a memory, the chat displays a Memory entry showing command=get and the memory’s title while the assistant works. The list option lets users search, preview and open saved memories, but it is not an editor: fixing or deleting an entry requires asking Kiro in the chat.

Kiro illustrates the intended benefit with a debugging example: after learning that integration tests require a seeded local database, the assistant could seed it first in a later session rather than rediscover the dependency. That is the company’s example of the workflow, not a reported test result.