Code maps, memory, and context

Code maps

Create a code map for a focused area of the repository. A map helps explain relationships and provides references back to files and lines. Use it to orient a session, inspect the cited code, or share the relevant structure with another task.

Good to know · A generated map is a snapshot. Revisit the source or regenerate the map after substantial code changes.

Project memory

Koyd stores persistent project memory on the server and uses a bundled local embedding model for semantic lookup. Agents can save reusable decisions and retrieve relevant knowledge in later work.

Keep memory specific: a build command, an architectural constraint, a decision and its reason, or a recurring failure. Review outdated entries when the project changes. Local embeddings do not mean model calls are offline; retrieved context can be sent to your configured provider.

Files and attachments

Use file references and attachments to give an agent the context it needs. Search project paths on the server, inspect file contents, and upload client files when appropriate. File references point to the selected server’s filesystem.

Search before widening the task

Search the project for names, paths, symbols, or relevant text. Read the result before assuming a component or behavior is current. Smaller, relevant context makes a task easier to review and reduces unnecessary model input.