Last Updated: 8/20/2026

Reference

Overview

The lookup surface for Jolli Memory. Configuration first, then every CLI command, then the agent support matrix. To fix a problem, see Troubleshooting and FAQ.

Prerequisites

• The jolli CLI installed, on Node 22.13 or later.
• The jolli space, jolli site, and jolli workflow command families each need their own plugin package, noted at the section that documents them.

Configuration

All configuration lives in ~/.jolli/jollimemory/config.json. The CLI, VS Code (including forks such as Cursor and Windsurf), and IntelliJ read from the same file. Secrets (apiKey, jolliApiKey, authToken) are masked when displayed.

Keys

A few advanced keys are edited by hand in config.json and are not accepted by jolli configure: logLevelOverrides, compileExcludeFolders, dcoSignoff, storageMode, and syncConflictPolicy. storageMode selects where memories are written - dual-write (default: orphan branch + on-disk folder), folder (folder only), or orphan (orphan branch only, no browsable Markdown on disk). syncConflictPolicy sets the fallback when a sync conflict cannot be auto-merged - prompt (default), mine (always keep the local side), or theirs (always accept the other device).

Editing config from the CLI

jolli configure                       # show current config (secrets masked)
jolli configure --list-keys           # list every key with its type
jolli configure --set model=sonnet --set maxTokens=16000
jolli configure --set excludePatterns=docs/**,*.log
jolli configure --remove apiKey

Unknown keys and malformed values are rejected with exit code 1.

Environment variables

CLI commands

Binary jolli, package @jolli.ai/cli. Most commands accept --cwd <dir> to run against a specific repo root.

Core

jolli enable --repo-hooks-only installs only the repo hooks, the Claude agent hooks, and the project /jolli menu - it skips host detection and MCP registration, and backs the Claude Code plugin bootstrap. It is mutually exclusive with --integrations-only, which repairs the MCP server, skills, and dispatch scripts without changing repo hooks.

jolli view --commit <ref> accepts a numeric index (1 is the latest) or a commit SHA prefix. HEAD, branch names, and tags are not recognized (they resolve to nothing).

jolli status --refresh re-checks which Jolli Space this repo is bound to by asking the server, instead of trusting the locally cached answer. Reach for it when the binding shown looks out of date.

jolli dashboard serves a dashboard from your own machine and holds the terminal until you press Ctrl+C. Everything is served locally; nothing is uploaded. For the pages it serves, what each one shows, and how the repository picker works, see The Local Dashboard.

jolli recall flags

--full (full markdown instead of the short summary), --output <path> (implies --full), --depth <n>, --budget <tokens> (default 20,000), --include-transcripts, --no-plans, --catalog (list recorded branches), --format <md|json>. Pass a branch name or keyword as an argument, or omit it for the current branch.

Auth & cloud

jolli push-control --disable stops this repo from sending memories to a Space. Memories are still recorded locally, so nothing is lost; only the outbound push is off. --enable turns it back on and kicks off a catch-up so the memories held while it was off are sent. --enable and --disable cannot be combined.

The choice is stored once per repository, machine-wide, keyed by the repo’s remote URL rather than inside the working tree. Two consequences: every worktree of the same repo shares one setting, and a repo with no remote cannot be listed alongside the others because there is no identity to key it by (you can still control it from inside the repo with --cwd).

If that stored setting cannot be read, Jolli reports pushing as OFF rather than guessing, and says why. Repair the file if you can. --enable will rebuild it, but a rebuild starts from an empty set, so every other repo’s opt-out on that machine is turned back on.

Pushing can be stopped by more than this one setting: a repo turned off with jolli disable does not push either, and syncOnPush: false separately stops the automatic push on git push. All of them retain the pending memories rather than dropping them.

Memory Bank cloud sync is on-demand. Run it from the CLI with jolli sync-memory-bank, or from the VS Code Settings page. IntelliJ can also sync automatically on a schedule, controlled by its Settings toggle. The only precondition is a valid jolliApiKey. In a terminal, jolli sync-memory-bank prompts you to resolve each conflict (mine / theirs / view diff / skip); only in a non-interactive shell (a hook or CI) does it skip conflicting files and print their paths for you to resolve in your editor.

To publish memories to a team Jolli Space, run jolli bind once, then jolli push. The VS Code and IntelliJ editors offer the same publish per memory through the Share in Jolli action.

Knowledge & maintenance

jolli compile requires an API key, the same one used for summary generation - which is why it stays manual unless you opt in: with wikiRebuild set to auto it also runs after each commit and after a merge or pull, and each of those runs is billed. jolli graph needs no key - it only exports the existing knowledge graph (.jolli/graph/graph.json, produced by a prior jolli compile) to HTML, and errors telling you to run jolli compile first if that graph is missing.

jolli cutover switches one repository’s memory storage from the git orphan branch to a local SQLite database, which then becomes the source of truth. It is one way. The cutover freezes the repository’s orphan branch, and jolli enable will not unfreeze it, so run jolli cutover --status first to see where the repository stands before committing to it. After a cutover, jolli cutover --probe checks the frozen branch for drift - it should not be moving, and a probe that reports it is means something is still writing to it. Restart any IDE or long-running process afterwards so cached storage handles are rebuilt. Memory Bank and Sync covers what this changes day to day.

Two backfill flags are for scripting rather than day-to-day use. --stream emits one NDJSON progress event per commit and then a final report line, so a script can follow a long run. --list-candidates reports which commits could be back-filled as JSON and exits without attributing anything or calling the LLM; --since-days <n> and --limit <n> narrow that listing and apply only alongside it.

MCP

jolli mcp starts a Model Context Protocol server over stdio so AI agents can query your memories directly. jolli enable registers it into every detected host (the IntelliJ plugin too, when a compatible Node runtime is available), and each host picks it up on its next start with no manual setup. For the per-host config-file locations, see the Use Your Memory from Any AI Agent (MCP).

jolli mcp             # start the server (normally launched by your agent)
jolli mcp --reindex   # rebuild the local search index and exit

The server exposes ten built-in tools:

These ten are always present. When you are signed in, the server may also register additional Jolli-hosted tools alongside them (controlled by mcpPlatformToolsEnabled, on by default); set that key to false for a git-memory-only server.

Two more commands, jolli pr-description and jolli queue-status, exist mainly for skills and agents. They mirror the matching MCP tools.

Jolli Workflows

jolli workflow inspects the Workflows of a git-backed Space you have cloned on this machine. It ships as a separate plugin, so install it alongside the CLI:

npm i -g @jolli.ai/cli @jolli.ai/workflow-cli @jolli.ai/space-cli

space-cli is only needed for jolli workflow local-run, which calls jolli space clones behind the scenes - installing all three up front avoids a failure on the first command.

The workflow command is listed in jolli --help even before the plugin is installed; running a subcommand without it prints an install hint. It needs a Jolli sign-in, and it only sees Spaces that are git-backed with the destination already cloned locally.

Two things to know:

• Every subcommand prints JSON, not formatted text. These are built to be called by scripts and AI agent recipes rather than read in a terminal.
• None of them starts a run. local-run reports what is eligible to run locally; starting a run is done from the web app with Run now, or by an AI agent connected to your Jolli workspace.
• An empty run history from jolli workflow runs does not always mean there are no runs. If the call cannot reach the server, is not authorized, or names a Workflow that does not exist, it prints {"type":"runs","runs":[]} and exits successfully, exactly as it would for a Workflow that has genuinely never run. If you expected runs and got none, check your sign-in with jolli auth status and confirm the Workflow id before concluding the history is empty.

For creating and scheduling Workflows, see Workflows.

Two skills are installed alongside these commands for running workflows from an AI agent: jolli-local-run runs a workflow on your own machine, so your agent executes the recipe and no Jolli LLM budget is used, and jolli-remote-run triggers a run on Jolli’s backend and monitors it to completion. In Claude Code they appear under the /jolli menu.

Jolli Spaces

jolli space manages a Jolli Space from the command line: syncing its articles as markdown, mapping the source repositories it watches, running documentation impact analysis, and driving an agent over it. It ships as a separate plugin, so install it alongside the CLI:

npm i -g @jolli.ai/cli @jolli.ai/space-cli

The space command is listed in jolli --help even before the plugin is installed; running a subcommand without it prints the same install hint.

Set up and inspect

Sync articles

Sources and impact analysis

Agent

One more sits outside those groups: jolli space verify-publish-branch <expected> [actual] checks that a locally run Workflow published to the branch the server expected, printing the comparison as JSON and exiting non-zero when they disagree. It is meant for scripts and agent recipes rather than day-to-day use.

The older flat commands still work, for now. jolli init, jolli source, jolli impact, jolli sync, jolli agent, and jolli docs are kept as hidden aliases of their jolli space equivalents. Each prints a deprecation notice and they are removed in the next major release, so prefer the jolli space form. There is no jolli space docs: the old docs pull and docs publish map to jolli space sync down and jolli space sync up.

Jolli Sites

The site commands build a documentation site on your own machine: scaffold one, run it with hot reload, produce a static build with a search index, and manage themes. They ship as a separate plugin, so install it alongside the CLI:

npm i -g @jolli.ai/cli @jolli.ai/site-cli

jolli site theme list ends with the line Built-in: default, forge, atlas. Those three need no download. Note that default is available to a local build but is not offered when you pick a theme pack for a hosted Site in the web app, which starts from Forge and Atlas.

The older flat commands still work, for now. jolli new, jolli convert, jolli build, jolli dev, jolli start, jolli reverse, and jolli theme are kept as hidden aliases of their jolli site equivalents, so existing scripts keep running. Each one writes jolli <command> is deprecated; use jolli site <command> to standard error and then does its job, which leaves anything reading standard output unaffected. Prefer the jolli site form.

Before the plugin is installed, these commands appear in jolli --help under Jolli Site under their older flat names, since the site grouping arrives with the plugin itself. Running one then prints npm install -g @jolli.ai/site-cli and stops.

This is for building a site locally. Publishing a Space as a hosted Site, custom domains, and access control are all done in the web app, and are covered in Jolli Sites.

Telemetry

Usage telemetry is content-free and on by default. For exactly which fields it sends, what it never sends, and every opt-out path, see Troubleshooting and FAQ.

You can also opt out by setting DO_NOT_TRACK=1. See https://jolli.ai/telemetry  for the full event list.

IDE commands

The editor extensions expose the same actions in a sidebar. In VS Code (and forks such as Cursor and Windsurf) open the Command Palette (Cmd/Ctrl+Shift+P) and filter on Jolli Memory; in IntelliJ use Find Action (Cmd/Ctrl+Shift+A). The main commands and their CLI equivalents:

Create PR lives in the branch footer of the sidebar, not the palette. The IntelliJ settings page at Settings > Tools > Jolli Memory exposes the Anthropic API key, model, and Jolli API key; other keys are managed via the CLI or by editing config.json directly.

Agent plugins

Claude Code, Cursor, and Codex each have their own install path that needs no CLI setup. Installing the plugin gives you that agent’s jolli skills, a bare jolli menu, and Memory’s MCP tools already connected. See Jolli Memory in Your AI Agent for the full surface, how the three differ, and what to check when nothing appears to happen.

Agent support matrix

Jolli Memory captures thirteen sources across ten agents. Each has a config toggle in the keys table above (claudeEnabled, codexEnabled, geminiEnabled, openCodeEnabled, cursorEnabled, copilotEnabled, clineEnabled, devinEnabled, antigravityEnabled, and kimiEnabled - three of those each cover two sources: cursorEnabled (the Composer IDE + the cursor-agent CLI), copilotEnabled (both GitHub Copilot sources), and clineEnabled (the Cline VS Code extension + CLI)). Claude Code and Gemini CLI capture through an agent hook, so restart them after jolli enable; the other eleven are discovered at commit time and need no hook or restart. For each source’s capture mechanism, session location, and Node 22.13+ requirement, see the Supported AI Agents and Capture.

Troubleshooting

If something is not working, run this first:

jolli doctor        # checklist of hook, credential, and queue state
jolli doctor --fix  # release stale locks and reinstall missing hooks

For specific problems, such as summaries not generating, sign-in failures, or sync and Share in Jolli errors, see Troubleshooting and FAQ. If you still need help, email support@jolli.ai with your jolli doctor output.

Related

• Getting Started with Jolli Memory - install, sign in, and your first Memory.
• Troubleshooting and FAQ - fixes for the common problems, and what data goes where.
• Supported AI Agents and Capture - how each agent’s sessions are captured.
• Jolli Memory in CI and Automation - headless auth, waiting for summaries, env vars, and backfill.