Skip to content
Thrum

Make your agents remember what they learn

Pro

Each coding tool loads a memory file at the start of every session. Some tools, such as Claude Code, read only the first part of a long one, so rules past that point are missed. With Pro, your agent keeps one short line per rule in the memory file and stores the full rule as a Thrum memory, a saved, titled note that later sessions and other agents in the project can search and read. So more rules fit in the same space.

Before you start

Section titled “Before you start”

What it looks like

Section titled “What it looks like”

This is an example. Before, a full rule sits in the memory file and uses several lines:

- Run the race-detector tests before merging anything that touches the
  scheduler. Last time we skipped them, a data race shipped and took two
  days to find. The command is the scheduler test target with the race
  flag on. If it is slow, run it on the package you changed first, then
  the whole suite before the merge.

After, the memory file keeps one line. It says when the rule applies and points at the full text. The line has a red circle symbol, the trigger, an arrow, and the memory’s ID. <ID> stands for the real ID.

- 🔴 Before merging scheduler changes → thrum-mem-<ID>

The full rule is now a Thrum memory. The agent reads it when the trigger matches, so the full text takes up no room in the file the rest of the time.

How it works

Section titled “How it works”

The Thrum plugin ships a skill for this, called memory-to-thrum-pointer.

  • The full text moves into a Thrum memory. The memory file keeps a trigger and an ID. The line is under about 140 characters.
  • The line says when the rule applies. It is a trigger, so the agent knows whether to open the full rule.
  • Nothing is deleted. The full text is kept in the Thrum memory. If the entry came from a longer note file (a topic file), that file stays and gains a link to the memory.

You don’t have to ask. Your agents use the skill on their own when their memory file is nearly full, or when they save a new memory. In Claude Code, Codex, Muse, GitHub Copilot, Cursor and opencode, the agent also gets a reminder when it writes to its memory file. Antigravity doesn’t get the reminder, so ask the agent when you want its file tidied.

Thrum memories belong to your project, not to one tool. A rule a Claude Code agent saves can be found by a Codex agent working in the same project, with no extra setup.

On Pro, two machines you have paired can also share memory storage. See Work across multiple machines.

Which file each tool uses

Section titled “Which file each tool uses”

Each tool loads a different file at the start of a session. This table shows which one.

Tool Memory file
Claude Code, Muse MEMORY.md
Codex, opencode, GitHub Copilot AGENTS.md
Antigravity GEMINI.md
Cursor .cursor/rules/*.mdc

The skill comes with these plugins:

  • Claude Code, Codex, Cursor, Muse and opencode: each has it in its own Thrum plugin.
  • GitHub Copilot: it uses the same Thrum Pro plugin as Claude Code, installed into Copilot. See Use GitHub Copilot CLI agents.
  • Antigravity: it comes when you install the Claude Code plugin.

What you can say

Section titled “What you can say”

You can also ask for it directly. Thrum’s web UI is the page you open in your browser to see your agents and their messages. Ask your coordinator (in its terminal, or in My Inbox, your inbox in Thrum’s web UI):

  • Move your long memory entries into Thrum memories.
  • Your memory file is near its limit. Tidy it with Thrum memory pointers.
  • Find the rule we saved about scheduler merges.

Each ask works on the memory file of the agent you ask. To tidy another agent’s file, ask your coordinator: Ask impl_api to tidy its memory file with Thrum memory pointers. Or message that agent yourself, in its terminal or from My Inbox.

Check it worked

Section titled “Check it worked”
  • Ask the agent to show you the line it saved in its memory file. It should be a short trigger followed by a memory ID containing -mem-.
  • Or open the agent in the Thrum web UI and look at its Memory tab, which lists its Thrum memories.
  • To read a rule in full, ask the agent: Open thrum-mem-<ID> and show me the full rule. Replace <ID> with the ID from the line.

On Free

Section titled “On Free”

On Free, agents can view and delete Thrum memories but cannot create or edit them. If an agent tries the skill on Free, it stops with needs Thrum Pro (free for eligible public repositories). Nothing changes, and the entry stays in the memory file as it was, so nothing is lost.

A public repository gets Pro at no charge once you register it. See Get Pro free for a public repository.

Next steps

Section titled “Next steps”