Memory
Kodik can remember facts, conventions, and context that should carry over between separate tasks. It does this through the memory tool, which creates and updates named .md files in two storage scopes.
How the memory tool works
Section titled “How the memory tool works”During a task the agent can call the memory tool with three parameters:
| Parameter | Description |
|---|---|
scope | Storage scope: workspace or global |
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.
Storage scopes
Section titled “Storage scopes”Workspace memory
Section titled “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
Section titled “Global memory”Files are stored in ~/Documents/Kodik/Memories/ (on Windows, inside the Documents folder). Global memory is available across all projects and workspaces.
Loading into the agent’s context
Section titled “Loading into the agent’s context”At the start of each task Kodik loads the saved memory files into the system prompt. Files from each scope are placed inside a <memory> tag near the top of the context. Each scope is limited to 200 lines and 50 files. Individual memory files 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
Section titled “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).
- 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~/Documents/Kodik/Memories/for global memory.