Skip to main content
Agents save what they learn with arakun mem: a decision, a trap in the build, the fix for a bug, how you want things done. Every new session starts with an index of it in the system prompt, so the next agent knows it without being told again.

What it remembers

  • About the project. One store per repository. Git worktrees share the store of their main checkout, so every environment of a project sees the same memory.
  • About you. A global store for preferences you state to an agent, such as how you want commit messages written. It applies in every project.
  • What each session did. Arakun records this itself: what was asked, how each turn ended, the commits and the files changed. Agents don’t have to write summaries. It keeps the last 30 sessions of each project.
Agents give each memory a kind: decision, bugfix, gotcha, convention, preference, discovery, pattern, config or note. Arakun’s own records of sessions have the kind session.

The Memory tab

Turn the tab on first: under Arakun › Extensions, or in Settings › General › Sidebar. The Memory tab shows what agents remember about the project in view, and under About you, in every project what applies everywhere. Search it, open a memory’s file in your editor, or delete one (click the bin twice). The tab updates as agents write. Memory is also in the palette (Ctrl+K), in the same search as everything else.

From a terminal

These work with the app closed, so headless agents use memory too. For an agent that Arakun does not start, arakun mem prompt prints the how-to and the index to put in its prompt.

Scripts worth keeping

Agents often write the same helper script again in session after session: one that runs the checks, or one that reads a pull request’s reviews. arakun mem scripts finds them in the project’s saved sessions:
It groups scripts by the words they use, since agents rarely write one the same way twice, and shows the five seen most often. It only reports and changes nothing. Keep the ones you like as a script of the project, or save them as a pattern memory.

Where it is kept

Plain JSON files: global.json, and one file per repository in projects/. They are in ~/.local/share/arakun/memory, or %LOCALAPPDATA%\arakun\memory on Windows. ARAKUN_MEMORY_DIR puts them somewhere else. If Arakun can’t read a store, say one written by a newer version or edited by hand, it renames it to <name>.corrupt-<time> and starts that store fresh, with a notice that says so. To restore it, quit Arakun, keep a second copy of the file, rename it back, and start a version that can read it.

Turn it off

Start Arakun with ARAKUN_MEMORY=off. New sessions then start without the index, and Arakun stops recording sessions. What is already saved stays on disk.