Last Updated: 7/13/2026

Reference

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

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, syncConflictPolicy, and dcoSignoff.

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 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 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. (The IntelliJ Recall skill requests a 30,000 budget instead of the 20,000 default.)

Auth & cloud

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 and jolli graph require an API key, the same one used for summary generation.

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 Connect Memory to Your AI Assistant (MCP) doc.

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

The server exposes nine tools:

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

Telemetry

Usage telemetry is content-free and on by default. It carries no account identifier, though signed-in events upload under your Jolli key, so they can be attributed to your account on our end.

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 support matrix

Jolli Memory captures seven sources across six assistants. Each has a config toggle in the keys table above (claudeEnabled, codexEnabled, geminiEnabled, openCodeEnabled, cursorEnabled, and copilotEnabled - the last covers both GitHub Copilot sources). Claude Code and Gemini CLI capture through an agent hook, so restart them after jolli enable; the other five are discovered at commit time and need no hook or restart. For each source’s capture mechanism, session location, and Node 22.5+ requirement, see the Supported AI Assistants and Capture doc.

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 the Troubleshooting and FAQ doc. 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 Assistants and Capture - how each assistant’s sessions are captured.
• Jolli Memory in CI and Automation - headless auth, waiting for summaries, env vars, and backfill.