Memory

Kodik can remember facts, conventions, and context that should carry over between separate tasks, and it can also keep temporary working notes for a single long-running task. It does this through the memory tool.

How the memory tool works

During a task the agent can call the memory tool with three parameters:

Parameter	Description
scope	Storage scope: workspace, global, or session
path	Memory file name (flat name only, no directory separators)
content	Markdown content to store

To delete an entry the agent passes delete: "true" instead of content.

The path is a bare filename — no subdirectories are allowed. A .md extension is added automatically if omitted. Absolute paths and .. traversal are rejected.

Note

Workspace and global writes create, update, or delete files in the chosen scope’s directory, and the change is loaded into the agent’s context on the next task. Session memory is different: it is saved inside the current chat session and becomes visible to the agent after conversation compaction.

Storage scopes

Workspace memory

Files are stored in .kodik/memories/ at the root of the current project. This memory is project-specific and can be committed to version control.

Example file: .kodik/memories/testing-conventions.md

Global memory

Files are stored in ~/.kodik/Memories/ (on Windows, C:\Users\<You>\.kodik\Memories\). Global memory is available across all projects and workspaces.

Session memory

Session memory is stored inside the current chat session instead of in a standalone file on disk. It is meant for temporary task state: plans, decisions, blockers, and handoff notes that should survive reloads and compaction but should disappear when the task is deleted.

Session memory is controlled from Settings → Agents → Session memory. Turning it off removes the session scope from the memory tool and keeps compacted summaries transcript-only.

Loading into the agent’s context

At the start of each task Kodik loads workspace and global memory files into the system prompt. Files from each durable scope are placed inside a <memory> tag near the top of the context. Each durable scope is limited to 200 lines and 50 files.

Session memory is not loaded into the system prompt. When a conversation has been compacted, Kodik appends the current session memory to the compacted assistant summary. That injected session-memory block is limited to the first 200 lines so long-running sessions cannot flood the next request. Individual memory entries must not exceed 16 KB.

Because memory files are plain .md files you can view and edit them directly. Kodik also automatically redacts values that look like secrets (tokens, API keys) before writing.

Practical tips

• Ask the agent to save team conventions, code-style preferences, or architecture details to workspace memory — they will automatically be present in future sessions.
• Use global memory for personal preferences that apply across all projects (for example, your preferred response language).
• Use session memory for temporary task state that should survive compaction but should not become a project convention.
• You can create or edit memory files by hand — Kodik will load them just like agent-created ones.
• To inspect what is stored, open .kodik/memories/ in the file explorer or ~/.kodik/Memories/ for global memory.