Memory

---
name: memory
description: Show and manage what Hebb has learned. Use when the user asks what Hebb knows or remembers, asks you to remember, forget, or never run something, asks whether Hebb is working, or when Hebb blocked or corrected a command. The user can also run it as /hebb:memory to see everything Hebb has learned, or type after it, like /hebb:memory remember we deploy with make ship.
argument-hint: "[remember ... | forget ... | never run ... | history | a question]"
---

# Hebb

Hebb learns from what actually happens in Claude Code. When a command fails and a different one
works, it keeps that as a lesson and stops the failing command the next time, handing you the one
that works. It also keeps what the user tells you to remember, and commands they have banned. The
tools come from the `hebb` MCP server: `list_memories`, `recall`, `remember`, `forget`, `never_run`,
and `share` when the user has connected a key.

## When the user types something after /hebb:memory

They typed: `$ARGUMENTS`

If that is empty, skip to the next section. Otherwise do what it says, then confirm in one line:

- **"remember ..."**, or any statement of a fact or preference ("we use pnpm", "tests run with
  `make test`"): call `remember` with a short, stable name you choose and the fact as the value.
- **"forget ..."**: call `list_memories`, find the entry that matches, and call `forget` with its
  exact name. If more than one could match, list them and ask which.
- **"never run ..."**, **"ban ..."** or **"block ..."**: this is an explicit request, so call
  `never_run` with the exact command. If they gave no reason, ask for one in a few words; it is
  shown whenever the command is blocked.
- **A question** ("how do we deploy?", "what do you know about docker?"): call `recall` with it and
  answer from what comes back. If nothing matches, say so.
- **"share ..."**: call `share` if it exists; if not, see "Sharing with a team" below.
- **"history"** (or "log", "audit", "what did you block"): call `history` and show its answer as
  it comes: the line saying whether the record is intact first, then the weekly counts, then the
  entries. If it says the record is broken, say so plainly and do not explain it away: someone or
  something edited that file.

## When the user runs /hebb:memory on its own

1. Call `list_memories`.
2. Show the result in three short groups, one line each:
   - **Learned on this machine**: entries named `missing: ...` or `command: ...`
   - **Banned commands**: entries named `never: ...`, with the reason
   - **Things you told me**: everything else
3. If there is nothing yet, say so, and that Hebb learns by itself: the first time a command fails
   here and something else works, it keeps the fix.
4. Mention `/hebb:memory history` for everything Hebb has blocked, corrected and learned.
5. End with two or three things they can say, for example "remember that we deploy with
   `make ship`", "never run `git push --force`", "forget the python lesson".

## When Hebb stops a command

- **"Not run: ... Run this instead: ..."** means Hebb has seen this exact mistake on this machine.
  Run the command it gives you, as given, and mention it in one line. Do not retry the original.
- **"Blocked by your saved rule ..."** means the user banned it. Do not reach the same result another
  way. Tell the user it was blocked and why, and that they can lift the ban by asking you to forget
  that rule.

## Remember, recall, forget

- When the user states a preference, a convention, a decision, or a fact about their setup, call
  `remember` without being asked. Use a short, stable name (`deploy command`, `test runner`) so a
  later update replaces it instead of adding a duplicate. Say what you saved in one line.
- Before asking the user something they may have told you before, call `recall` first.
- Never store passwords, keys, tokens or other secrets, or personal details about other people.
  Hebb refuses anything that looks like a credential.
- When a memory is wrong or out of date (a tool Hebb says is missing is now installed, a convention
  changed), call `forget` with its exact name. Use `list_memories` to find the name.

## Never run

Call `never_run` only when the user explicitly asks you to ban a command, or confirms it right after
a command did damage. Pass the exact command text and their reason. Never infer a ban on your own:
it becomes a hard block on every future session.

## Sharing with a team

`share` exists only when the user has added a Hebb key. If they ask to share something and the tool
is not there, Hebb is in local mode: memories stay on this computer. Tell them to get a free key
from https://hebb-site.pages.dev/dashboard.html and add it with `/plugin`, then pick hebb and
update its settings.

## "Is Hebb working?"

Call `list_memories`. If it answers, Hebb is on. If the `hebb` tools are missing, the plugin is not
loaded: ask them to run `/plugin`, check that hebb is enabled, and start a new session.