> ## Documentation Index
> Fetch the complete documentation index at: https://docs.versuno.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# versuno memory install-hook

> Make Claude Code recall your local memory automatically.

```
versuno memory install-hook [--uninstall]
```

Wires the auto-recall hook into Claude Code so your local memory store is searched on every prompt and the matches show up as context. No manual `recall` calls, no API.

It adds a `UserPromptSubmit` hook to `~/.claude/settings.json` that runs [`versuno memory recall --hook`](/cli/memory-recall#hook-mode). Your existing hooks and settings stay as they are, and the file is backed up to `settings.json.bak` before any change.

## Prerequisites

* The Versuno CLI installed globally so `versuno` is on your `PATH` (`bun add -g versuno-cli`). The hook runs `versuno memory recall --hook`.
* A populated local store. Run [`versuno memory capture --local`](/cli/memory-capture) first.

## Options

| Flag          | Description                                                                |
| ------------- | -------------------------------------------------------------------------- |
| `--uninstall` | Remove the auto-recall hook. Your other hooks and settings stay untouched. |

## What it changes

The command adds this entry to the `UserPromptSubmit` array in `~/.claude/settings.json`:

```json theme={null}
{
  "hooks": {
    "UserPromptSubmit": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "versuno memory recall --hook",
            "timeout": 10
          }
        ]
      }
    ]
  }
}
```

It's idempotent, so running it twice won't add a duplicate. Restart Claude Code (or start a new session) for the hook to take effect.

## Examples

```bash theme={null}
# Install, so Claude Code recalls automatically
versuno memory install-hook

# Remove the hook
versuno memory install-hook --uninstall
```

## Privacy note

Recall is global. A memory captured in one project can show up in a session in another project whenever the prompt matches. That's intentional, your memory follows you across projects and agents, but it's worth knowing before you turn on automatic injection.

## See also

* [versuno memory capture](/cli/memory-capture) fills the local store
* [versuno memory recall](/cli/memory-recall) searches it by hand