Claude Code

Keep useful work from one Claude Code session for the next. MemIndex records prompts and tool activity. It turns that work into searchable notes and session summaries.

Set up

Install Claude Code first. Then run:

npx memindex install --ide claude-code

In a terminal, the installer asks how MemIndex should write its notes. See Install for the shared setup steps.

The installer enables the MemIndex plugin in Claude Code. Start a new Claude Code session after setup.

Let an agent or script do it

If Claude Code, another agent or a script runs the install, use the command that never asks a question:

npx memindex install --ide claude-code --yes

It uses your Anthropic plan to write notes, keeps memory on this computer, starts the background service and waits until it answers. If the service cannot start, the command exits with an error and tells you which command to run.

What it changes

• Copies the MemIndex plugin into ~/.claude/plugins and lists it in known_marketplaces.json and installed_plugins.json there.
• Turns the plugin on in ~/.claude/settings.json, leaving your other settings alone. Native Claude Code memory stays on unless you pass --disable-auto-memory.
• Creates ~/.memindex for your notes, settings and the viewer sign-in key.
• Starts the background service.

Take it out

npx memindex uninstall

This stops the service and removes everything above except ~/.memindex, so your notes are kept.

Use it

Work in your project as usual. MemIndex records tool results, including failed tool calls. It adds relevant past work when a new session starts.

Ask Claude Code to search memory when you need an earlier decision or fix. For example:

Search MemIndex for what we learned about the login flow.

When Claude Code shortens a long conversation, MemIndex can give it a saved record to read and continue from. This feature is called Endless Mode. It is on by default for local Claude Code sessions.

See that memory is being saved

The installer offers a status line at the bottom of Claude Code. When memory is working it reads memory: saved 5 min ago. When saving stops, it turns red and reads MEMORY NOT SAVING, followed by the reason and what to run. A new session also opens with a warning line in that case.

MemIndex never replaces a status line you already have. To turn it on later, run npx memindex install --status-line. To skip it, add --no-status-line.

If the reason says your memory database is newer than the plugin, update with:

npx memindex@latest update

Check it

npx memindex status
npx memindex doctor

Complete some work with a tool call. Start a fresh session in the same project. Ask it to find that work in MemIndex. New notes can take time to appear while MemIndex processes them.

A resumed conversation usually keeps its existing context. It does not receive the same startup history as a fresh session.

If no notes appear, use Troubleshooting. Read Privacy before recording sensitive work.