Code maps, memory, and context

Code maps

A code map explains how a feature works, with every element linked to its files and lines. With a project selected, open Codemaps (Ctrl+M, or Cmd+M on a Mac), describe what to map, such as the authentication flow, and Koyd generates the map with an AI model. Maps are saved per project. You can generate a new version with another model and still switch back to earlier versions.

• Sections group what the feature does. Select an element to read its responsibility and connections in Overview, open its code in Source, or ask about it in AI notes.
• Arrows show recorded behavior such as calls, reads, and writes. Show all connections reveals the rest, and Fit selection and connections brings the selection and its connections into view.
• A Walkthrough follows a reading order step by step and selects the code for each step.
• Filter sections & nodes searches names, descriptions, paths, and connection notes.
• To give a map to a session, type @codemap: in the composer and pick the map. Koyd adds the map's context to your message as a file reference.

Good to know · A map is AI-assisted analysis, not a runtime trace or a complete call graph. Check the cited code before you rely on a claim.

Outdated code links

Code keeps changing after a map is made. When a map opens, Koyd checks each element's code link against the current files, and it checks again shortly after project files change. Outdated elements get a badge: Moved, Changed, Not found, or File missing. The inspector explains the problem, and Source opens where moved code is now.

A bar above the map shows how many code links are outdated and offers two fixes. Each saves a new version, and the previous version stays selectable.

• Fix locations points moved and changed elements to their new lines, and finds a missing symbol when exactly one file of the same type defines it. It uses no AI and leaves unclear cases unresolved.
• Refresh with AI re-analyzes only the sections with outdated elements, with the model you pick. The rest of the map and its AI notes are kept. It is not offered for change maps.

Good to know · The check only reads files and is advisory. If it cannot run, the map simply shows no freshness information.

Changes in a map

The Change map step in a workflow maps what a run changed. In the explorer, changed elements are colored by status (Added, Modified, Deleted, or Renamed) and show how many lines were added and removed. The header shows the change totals and the commit range, which ends in working tree when the map includes uncommitted changes. Select a changed element and open Diff to read its changes, Unified or Side by side.

For a run on its own branch, Source shows the project's current files until you merge the branch, while the line ranges and Diff describe the run's version. Workflows explains the Change map step.

Project memory

Memory keeps short facts between sessions, such as a build command, a decision and its reason, or a recurring failure. Turn it on for a project or a session group with Enable Memory in its menu. Lab → Memory has the main switch and the settings: Results per Query, Fact Extraction, and Retention with Unused Age and Max Chunks.

With Fact Extraction on, Koyd keeps explicit statements from your messages, such as preferences, project facts, and decisions; otherwise it saves a short excerpt of the conversation. Agents can search, read, save, correct, delete, and pin memories with their memory tools, and read-only modes can only search and read. Under a reply, a line such as 2 memories recalled shows what was used. Retention removes old, unused memories and keeps pinned and previously recalled ones.

Memory search uses a bundled multilingual embedding model that covers more than 200 languages and code, so a question can find a memory written in another language. Recall across languages works, but less well than within one language. If the model is unavailable, memory falls back to text search.

Good to know · Storage, indexing, and fact extraction run on the server without extra model requests. Recalled memories become part of the prompt, so your chat provider receives them. Memory does not detect secrets; treat it like chat history. For reference documents such as API docs or runbooks, use Knowledge bases.

Files and attachments

Type @ in the message box to reference a project file or folder; the suggestions search paths on the server. To give the agent a file from your device, attach it (see Attach files in Working with agents).