KodaCode
Coming soon
Docs/Features

Memory

The agent stores solutions, problems, decisions and patterns as it works, linked by how they relate, and finds them again in later sessions.

Memory is on by default (Preferences → Memory → Use memory). Before each turn, KodaCode recalls the memories that match your message and gives them to the agent. The first message of a session also gets a briefing of the project's recent activity, open problems and patterns. The agent sees the recalled memories and the briefing. The transcript does not show them.

The agent decides what to store. It stores new memories as it works, or when you ask it to remember something. KodaCode does not store memories by itself.

What a memory is

A memory has a type, a title, content, tags and an importance from 0 to 1. Its type is one of task, code pattern, problem, solution, project, technology, error, fix, command, file context, workflow, general, conversation or preference. Links connect memories by how they relate. For example, a fix SOLVES a problem, a cause CAUSES an error, and an approach BUILDS_ON another or is DEPRECATED_BY another. To follow the links of a memory, the agent asks for its related memories.

A memory records the session that stored it or last changed it. The agent sees this as From session when it reads, searches or recalls memories. With that session ID, the agent can open the earlier session with search_sessions and read the work behind the memory.

In the right panel

The Memory section of the right panel shows how many memories the project has:

  • This session lists the memories that this session Saved, Updated, Read or Forgot. A memory counts as read when the agent gets it or lists its related memories. A recall or a search does not count.
  • Recent in project lists the memories that changed last.
  • Manage opens the Memory screen. Click a memory to open it there.

The memory screen

Open it with /memory or ⇧⌘M:

  • List, Graph and Timeline views, Search memories, and a filter for each type.
  • Open a memory to see its content and its Linked memories.
  • Edit a memory's title, content, Tags, comma separated, and Importance, 0 to 1. The right panel updates after you save.
  • History shows each version of the memory.
  • + link connects this memory to another one.
  • Delete a memory, then press again to delete it and its history.

Where it's kept

Each project keeps its memories in .koda/memory/, which git ignores. If you choose it in project setup, the project keeps them in .koda/memory.json instead. That file is committed with the repository, so your team shares it.

The memory tool

The agent's memory tool stores, gets, updates and deletes memories. It also searches and recalls memories, lists related memories, links memories and shows recent activity.