# claude-mem for Claude Code: what it does and how to install it

> claude-mem is a Claude Code plugin that captures what your agent does during a session, compresses it, and injects the relevant part back at the start of the next one. It ships 19 skills and one command, so context you built on Monday is still there on Tuesday.

Canonical: https://www.flowy.sh/plugins/thedotmack-claude-mem/guide
Published: 2026-08-06
Updated: 2026-10-29
Author: Maximo Correa

## When does claude-mem pay off?

You spend a session working out why a build fails. You find it. The session ends.

Tomorrow you open Claude Code and the agent knows none of it. Not the dead ends
you ruled out, not the file that turned out to matter, not the fix. You explain it
again, and the explaining is the expensive part.

claude-mem is built for that gap. It watches what happens during a session,
compresses it, and puts the relevant part back in front of the agent next time.

## What does claude-mem include?

Nineteen skills and one command. The full set, not a sample:

`babysit` · `cloud-sync` · `design-is` · `do` · `how-it-works` ·
`knowledge-agent` · `learn-codebase` · `make-plan` · `mem-search` ·
`mode-creator` · `oh-my-issues` · `pathfinder` · `smart-explore` · `standup` ·
`timeline-report` · `version-bump` · `weekly-digests` · `what-the` · `wowerpoint`

The command is `anti-pattern-czar`.

Read the names and the shape of the thing shows up. Some are about getting
context in (`learn-codebase`, `smart-explore`). Some are about getting it back out
(`mem-search`, `timeline-report`, `weekly-digests`, `standup`). Others are working
habits the author wanted to keep across sessions rather than retype
(`make-plan`, `babysit`, `do`).

That is a description of the names, not a claim about the code. For what each one
does, read it at the source: every skill on the listing links to its own file.

## How do I install claude-mem in Claude Code?

The install commands are on [the install card on the listing page](https://www.flowy.sh/listings/thedotmack-claude-mem#install), derived from the plugin's own synced
manifest rather than typed here. Two lines: one adds the marketplace, one
installs the plugin.

Copying them into this page would mean a second copy of a command that changes
whenever the author renames their marketplace, and this page has no way to know
when that happens. The listing does.

## How does invocation fire in claude-mem?

Every other plugin directory stops at the command above. This is the part that
decides whether any of it matters, and the answer is different for each kind of
component.

**A skill can fire itself.** The model reads the skill's own description and
invokes it when your prompt matches, without you naming it. You can also call one
by name, and each is available as a slash command. Nineteen of the twenty
components here are skills, so most of this plugin is the kind that can act on
intent rather than on instruction.

**A command never fires itself.** `anti-pattern-czar` runs when you type it. That
is the whole contract, and it is a feature: some things should only happen because
you asked.

**Hooks run on events, not on intent.** They fire when something happens in the
session rather than when your prompt suggests they should. claude-mem ships hooks,
which is consistent with a plugin whose job is to notice things while you work.

The distinction is worth holding on to, because "I installed it and nothing
happened" almost always means the component was a command and nobody typed it, or
a skill whose description did not match how the prompt was phrased.

## Who should use claude-mem?

People working on the same thing across many sessions. A long refactor, a system
you return to weekly, a codebase you are still learning. The value comes from
accumulation, so a plugin like this is worth least on day one and most in month
three.

If your work is a series of unrelated one-off sessions, memory across them buys
you less.

## What does claude-mem not do?

It does not make your other skills fire. Context loss and skill invocation are
different problems that get confused because both feel like the agent forgetting.
claude-mem addresses the first. Whether an installed skill actually gets invoked
at the right moment is the second, and it is answered by the routing layer on an
auto-invoked listing.

Worth being clear about, because a memory plugin is the closest thing in the
catalog to the compaction problem, and it would be easy to oversell it into
solving the other one.

## What should I read before I install claude-mem?

The listing carries the full component list, every skill linked to its source, and
the repository behind it. Nothing here is a substitute for reading the file you
are about to hand your agent.

Sources: [thedotmack/claude-mem on GitHub](https://github.com/thedotmack/claude-mem), [thedotmack/claude-mem README](https://github.com/thedotmack/claude-mem#readme)

## Common questions

### Will claude-mem make my other skills fire?

No. Context loss and skill invocation are different problems that feel the same, because both look like the agent forgetting. claude-mem addresses the first. Whether an installed skill gets invoked at the right moment is answered by a routing layer, on an auto-invoked listing.

### I installed it and nothing happened. Why?

Almost always one of two things. The component was a command, and a command never fires itself, so it runs when you type it. Or it was a skill whose description did not match how you phrased the prompt. Nineteen of the twenty components here are skills, so most of it can act on intent.

### Is it worth installing if my sessions are unrelated?

Less so. The value comes from accumulation, so a memory plugin is worth least on day one and most in month three. It pays off on a long refactor or a codebase you return to weekly, and buys you little across a series of one off sessions.

## Related

- [The listing page](https://www.flowy.sh/listings/thedotmack-claude-mem): Install command, components and repository
- [Alternatives to this plugin](https://www.flowy.sh/alternatives/thedotmack-claude-mem): Peers in its category, ranked by stars
- [The Claude Code plugin marketplace](https://www.flowy.sh/marketplace/plugins): How plugins install, and every plugin in the index
- [MemPalace for Claude Code: what it does and how to install it](https://www.flowy.sh/plugins/mempalace-mempalace/guide): another plugin guide
- [GBrain for Claude Code: what it does and how to install it](https://www.flowy.sh/plugins/garrytan-gbrain/guide): another plugin guide
