Last Updated: 8/3/2026

Jolli Memory in Claude Code

Jolli Memory ships as a Claude Code plugin. Install it once and Memory’s tools, commands, and skills are available inside Claude Code, and the git hooks that build your Memory are set up for you as you work.

If you already use the Jolli CLI you do not need the plugin. Both do the same job for a repository, and whichever surface is newest drives that repository’s hooks. The plugin is the shortest path when Claude Code is where you work.

Install

In Claude Code:

/plugin marketplace add jolliai/jolli-claude-plugin
/plugin install jolli@jolli-marketplace

The first line adds Jolli’s marketplace, the second installs the plugin from it.

In the desktop app, use + → Plugins → Add marketplace with the same source, then enable Jolli Memory under Manage plugins.

Requirement: node must be on your PATH. Claude Code fetches the plugin itself, so you do not need npm. This is the same Node requirement the CLI and the editor extensions have.

On Windows, the fallback path needs a bash shell. Most of what the plugin does runs through Memory’s MCP tools and is unaffected. But when a command or skill falls back to calling Jolli directly, it runs a helper script at ~/.jolli/jollimemory/run-cli, and that script is written for bash. It works in Git Bash and not in PowerShell or Command Prompt. If a /jolli:* step fails with a command-not-found or a path error while everything else works, this is why: run Claude Code from Git Bash, or install the CLI with npm i -g @jolli.ai/cli and use jolli directly.

Turn it on for a repository

There is no enable command to run. After install, the plugin sets itself up the next time it starts a session in a git repository:

1. Install the plugin (above).
2. Fully restart Claude Code. In the desktop app, quit it completely (Cmd+Q) rather than closing the window. Setup runs at session start, so it does not take effect in a session that was already open. This is the most common reason nothing appears to happen.
3. Open a session inside the git repository you want Memory for.
4. The plugin then installs Jolli’s git hooks into that repository, adds the /jolli menu, and selects a way to generate your memories. It repeats this check every session, so it stays set up and repairs itself if something is removed.
5. Run /jolli:status to confirm. You should see hooks installed and an AI provider set.
6. Make a commit. The Memory appears shortly after the commit returns.

You do not need to sign in or add an API key to generate memories. In Claude Code, Memory generates them through your local Claude Code CLI. Signing in is only for sharing to a Space, below.

Each git worktree is set up separately, so a new worktree gets the /jolli menu on its first session there.

Your past reasoning arrives automatically

Claude Code is the only assistant that gets a briefing without being asked. Once a repository has Memories, every new Claude Code session opens with a compact [Jolli Memory — <branch>] block: the branch name, its recent Memories, the key decisions behind them, and any pinned plans. It runs about 300 to 500 tokens, so it orients the session without eating your context budget.

Two things to expect:

• Feature branches only. The automatic briefing is skipped on the shared branches main, master, develop, development, staging, and production. The match is exact and case-sensitive, so a branch named Main or release/2.0 still gets one.
• After three quiet days on a branch, the briefing starts suggesting you run a full Recall instead.

Skipping the automatic briefing never disables recall. Run /jolli:recall any time for a deeper pull, or /jolli:recall <branch> for a branch you are not on. See Recall vs Search.

Nothing seems to have happened

These are the causes specific to the plugin. Work down them in order:

• Claude Code was not fully restarted. Setup runs at session start. Quit the app completely and reopen it. To check whether setup has run at all, look for the file ~/.jolli/jollimemory/run-cli. If it is missing, the plugin has not set itself up yet.
• The session is not inside a git repository. The plugin only acts inside a git repository, and does nothing at all outside one. Open a folder that is a repository, or run git init first.
• Memory was turned off for this repository earlier. Turning Jolli off for a repository is remembered, and the plugin honors it: it keeps Memory off and removes that repository’s hooks even after you install the plugin. The setting lives in .jolli/jollimemory/profile.json in the repository’s main worktree. In a repository with submodules, turning it off in one submodule covers the others. Turn Memory back on for the repository and the plugin sets it up on the next session. For how to turn it off and on from the CLI, see Troubleshooting and FAQ.

Run /jolli:status after each step to see whether it took effect.

If none of those is the cause, the problem is not plugin-specific. One thing worth ruling out: Claude Code capture can be switched off in your configuration. It is on unless someone changed it, so this only applies if you or a teammate set claudeEnabled to false. If you also have the CLI installed, turn it back on with jolli configure --set claudeEnabled=true. For everything else - missing credentials, a stuck background worker, a summary that never generated - see Troubleshooting and FAQ.

Commands and skills

Five commands:

Three skills:

Typing /jolli on its own opens a menu that lists these and runs the one you pick.

/jolli:init is a convenience, not a prerequisite. Memory generation is already set up by the time you could run it; what init adds is signing in and binding a Space in one pass.

The plugin also registers Memory’s MCP tools, so you can ask for recall or search in plain language instead of running a skill. For the tools and how they behave, see Use Your Memory from Any AI Assistant (MCP).

Using the CLI in another assistant? The plugin’s commands are namespaced with a colon (/jolli:recall). In Codex, Cursor, Gemini CLI, GitHub Copilot, and OpenCode the CLI installs the unnamespaced forms instead (/jolli-recall, /jolli-search). Same actions, different names per host.

Signing in and sharing to a Space

Signing in is what lets you bind the repository to a Jolli Space and share memories with your team. After binding, a git push publishes that branch’s memories to the Space.

/jolli:login

This opens your browser and can take up to a minute. Two things to know:

• It is not needed to generate memories. Generation keeps running locally whether you sign in or not.
• Sharing needs a Jolli credential specifically. A Jolli sign-in or a Jolli API key can bind a Space; an Anthropic API key cannot. If you use your own Anthropic key for generation, you still need to sign in to share.

Run /jolli:logout to sign out. Your Anthropic key, if you set one, is preserved.

What the plugin does not cover

The plugin covers Jolli Memory only. The jolli space, jolli site, and jolli workflow command families come from separate CLI plugins you install with npm, and the Claude Code plugin does not load them - it carries a fixed command surface. If you need those, install the CLI alongside the plugin you want, for example npm i -g @jolli.ai/cli @jolli.ai/space-cli. Memory Bank cloud sync and the knowledge wiki are also CLI-only.

You can run the plugin, the CLI, and an editor extension together - whichever surface is newest drives a repository’s hooks, so they do not fight. For which surface suits you, see Jolli Memory.

Related

• Jolli Memory - install, sign in, and your first Memory
• Use Your Memory from Any AI Assistant (MCP) - the MCP tools
• Recall vs Search - when to use which
• Reference - every CLI command and configuration key
• Supported AI Assistants and Capture - how each assistant is captured
• Troubleshooting and FAQ - when something is not working