Skip to Content
Jolli MemoryInstall Jolli Memory

Last Updated: 8/20/2026

Install Jolli Memory

Jolli Memory runs in more than one place. They all write to the same Memories on your machine, so the choice is about where you work, not about what you get.

If you just want the fastest path and you work in a terminal, install the CLI and skip the rest of this page. Everything else here is for picking deliberately.

Every way in

Where you workInstallBest for
A terminal, Vim, Emacs, or anywhereCLIThe complete surface. Every command, and the only one that runs in CI.
VS CodeVS Code extensionA sidebar and in-editor actions, with the CLI bundled in.
Cursor, Windsurf, or another VS Code forkthe same extension, from Open VSXThe sidebar on a fork.
A JetBrains IDEJetBrains pluginThe tool window. Needs Node on your PATH.
Claude CodeClaude Code pluginSetup handled for you, no npm and no credential.
Cursor, as your agentCursor pluginThe same, opt-in per repository.
CodexCodex pluginThe same, after you trust its hook.
Any other MCP-aware agentMCP host configReading your Memories from the chat, with nothing installed.
A hosted agent that cannot run local processesthe hosted endpointReaching your organization’s memory over the web.
A CI runnerCLI, headlessUnattended runs with an API key.

Node 22.13 or later is required for everything above except the hosted endpoint. The plugins and the editor extensions bundle Jolli’s own code, but none of them bundles Node.

You can run more than one. Whichever surface is newest drives a repository’s hooks, so they do not fight.

CLI

The primary surface. It works in any terminal, any editor, and in CI.

It installs the CLI, installs Node if you do not have it or your version is too old, then hands off to the guided setup so you finish with Memory already enabled in your repo.

macOS, Linux and WSL

curl -fsSL https://jolli.ai/install.sh | sh

Windows PowerShell

irm https://jolli.ai/install.ps1 | iex

Windows Command Prompt

curl -fsSL https://jolli.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To manage Node yourself, set JOLLI_INSTALL_NODE=0 before running and the script prints the commands to install Node by hand. On macOS and Linux you can point it at a different Jolli server with -s -- --url <server-url>, or force the Node install with -s -- --install-node.

If the script finishes and jolli still does not exist, check your Node version first. The script checks the major version only, so it accepts anything on Node 22 and reports success. The package itself requires 22.13, so npm is what refuses, and the script does not show you npm’s output on a run it considers successful. Node 22.5 through 22.12 fails this way silently. See Troubleshooting and FAQ.

Or with npm

npm install -g @jolli.ai/cli
jolli --version

Install it globally, because the git hooks call jolli directly. The package refuses to install below Node 22.13, so upgrade first if you need to, for example nvm install 22.13.

Or have your agent install it

If you already work in a terminal agent, paste this in:

Install the Jolli Memory CLI: run npm install -g @jolli.ai/cli, then jolli auth login to sign me in, then jolli enable in this repository and show me jolli status.

Then continue at Getting Started with Jolli Memory.

VS Code, Cursor and Windsurf

One extension covers all of them. It bundles the CLI, so there is no separate install.

  • VS Code (1.101 or later) - Extensions view, search Jolli Memory, Install. Or code --install-extension jolli.jollimemory-vscode.
  • Cursor, Windsurf and other forks - the same extension from Open VSX, for example cursor --install-extension jolli.jollimemory-vscode.

Enable it by clicking the Jolli Memory icon in the Activity Bar. Hooks install automatically, then reload the window so they take effect.

JetBrains

Settings → Plugins → Marketplace, search Jolli Memory, Install, then restart the IDE. Requires 2025.1 or later.

JetBrains needs Node 22.13 or later on your PATH, and there is no degraded mode below it: the plugin bundles Jolli’s code but not Node, so the MCP server and both skills are skipped and the tool window reports it. Memory generation keeps working.

Agent plugins

Jolli ships a plugin for Claude Code, Cursor and Codex. Each fetches itself from that agent’s marketplace, so there is no npm step and no credential needed to generate Memories.

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

Cursor has no command form: add jolliai/jolli-cursor-plugin as a marketplace, then install Jolli Memory from Customize in the sidebar.

The three differ in ways that matter on your first day, including one that surprises everyone: Cursor does not set up a repository until you opt it in. For the install details, the differences, and what to check when nothing appears to happen, see Jolli Memory in Your AI Agent.

Any other MCP host

Eleven hosts are configured for you when you run jolli enable. For anything else, jollimemory is a standard stdio MCP server, so any MCP-capable host can use it.

With nothing installed, point the host at:

npx -y @jolli.ai/cli mcp

That gives the agent read access to Memories you already have. Recording new ones still needs jolli enabled in the repo, because capture runs off git hooks.

With the CLI installed, register a stdio server with command jolli and args ["mcp"], under whatever key that host uses.

Hosts differ in where they keep MCP configuration and in which parts of the protocol they support. Check your host’s own documentation for the file it reads. For the eleven that are wired up automatically, and for connecting an agent that cannot start a local process, see Use Your Memory from Any AI Agent (MCP).

Which one should I use?

Most people should take the CLI, or the plugin for the agent they already live in. The cases below are the ones where the answer is genuinely not obvious.

You work in Cursor. Three different things carry the name, and they do different jobs:

  • The Cursor plugin is the one you want if Cursor is your coding agent. It sets up repositories you opt in, gives you /jolli- skills, and briefs each new session.
  • The VS Code extension from Open VSX gives you the visual sidebar. Install it as well if you want the panel; it is not an alternative to the plugin.
  • Cursor as an MCP host happens on its own when you run jolli enable with the CLI. You do not choose this one.

You work in VS Code or Windsurf. Take the extension. There is no agent plugin for either.

You already have the CLI and you want a plugin too. Fine, and common. Whichever surface is newest drives the repository’s hooks.

You only want to read Memories, not record them. Use the npx MCP server above. Nothing is installed and nothing is written to your repositories.

You are setting up a CI runner. Use the CLI with an API key, not the install script. See Jolli Memory in CI and Automation.

What differs by surface

Everything above records the same Memories. These are the differences worth knowing before you pick.

I want to…Best surface
Run Memory anywhere, including CICLI
Get a briefing at the start of every AI session, without askingClaude Code, Cursor or Codex plugin
Browse Memories in a sidebar while I codeVS Code extension, or the JetBrains plugin
Set it up without installing npm or adding a credentialAn agent plugin
Keep my repositories untouched until I say soCursor plugin
Ask about my history in plain languageAny MCP host
Reach my team’s memory from a hosted agentThe hosted endpoint
See stats, standup and the knowledge graphCLI, via the local dashboard
Publish Memories to my teamAny surface, once you sign in

The jolli space, jolli site and jolli workflow command families are separate npm packages and are not carried by any plugin or extension. Install them alongside the CLI, for example npm i -g @jolli.ai/cli @jolli.ai/space-cli.

Next steps

Troubleshooting and FAQGetting Started with Jolli Spaces