# Jolli Support

## Jolli Memory

- [Getting Started with Jolli Memory](/jolli-memory/getting-started-with-jolli-memory): When you work with an AI coding agent, the reasoning behind every decision lives in the conversation: why you picked this approach, what alternatives you rejected, what dead ends you hit. The commit…
- [Jolli Memory in CI and Automation](/jolli-memory/jolli-memory-in-ci-and-automation): Jolli Memory runs headless. Everything you do interactively - install, sign in, enable, commit, view - also works from a script or a CI job with no editor and no browser. This page covers the pieces…
- [Memory Bank and Sync](/jolli-memory/memory-bank-and-sync): Jolli Memory keeps a copy of every memory on your own disk, and it can mirror those memories across your devices. This page explains the Memory Bank (the local copy), how to find and move it, and how…
- [Recall vs Search](/jolli-memory/recall-vs-search): Recall resumes one branch. Search finds a decision across all branches.
- [Reference](/jolli-memory/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.
- [Supported AI Assistants and Capture](/jolli-memory/supported-ai-assistants-and-capture): Jolli Memory captures the reasoning behind your work automatically. On every commit, a background worker finds the AI coding session that produced the work, reads its transcript and your git diff,…
- [Troubleshooting and FAQ](/jolli-memory/troubleshooting-and-faq): This is the place to look when Jolli Memory is not behaving, and the place to check the common questions before you adopt it.
- [Use Your Memory from Any AI Assistant (MCP)](/jolli-memory/use-your-memory-from-any-ai-assistant-mcp): Jolli Memory captures the reasoning behind your commits. This page connects that memory to your AI assistant through the Model Context Protocol (MCP), so the assistant can read your history from…

## Jolli Sites

- [Jolli Sites](/jolli-sites): A Site is a published documentation website built from a Space. One Space can power more than one Site (a public one and an internal-only one drawing from the same Articles, for example).

## Jolli Spaces

- [Editing](/jolli-spaces/editing): The manual writing surface: the Article editor and the tools for finding and organizing content within a Space. For the AI side - drafting with the Agent, Changesets, and Gap Analysis - see The Jolli…
- [Getting Started with Jolli Spaces](/jolli-spaces/getting-started-with-jolli-spaces): A Space is where documentation lives in Jolli. You bring your existing docs in (or generate them from code); the Jolli Agent and Gap Analysis keep them in sync as the code changes; every edit passes…
- [Managing a Space](/jolli-spaces/managing-a-space): Every Space has its own settings, separate from your organization's Settings. Space Settings is where you control who can work in a single Space, how automation behaves for it, where its content is…
- [The Jolli Agent](/jolli-spaces/the-jolli-agent): The Jolli Agent is Jolli's AI assistant: you give it a documentation task and it drafts the work for you. This article covers the Agent itself, the Changesets its edits pass through for review, and…
- [Workflows](/jolli-spaces/workflows): Availability: Workflows is available only if it has been enabled for your organization. It's turned on by Jolli for your organization - you can't enable it yourself. If you don't see a Workflows…

## Settings

- [Settings](/settings): Organization and account settings live under the Settings menu. This page covers the areas that matter day-to-day: your profile and preferences, the people in the organization, the roles that govern…

## Welcome To Jolli

- [Welcome to Jolli](/welcome-to-jolli)

## Whats New In Jolli

- [What's New in Jolli](/whats-new-in-jolli): Highlights: four new AI assistants captured, /llms.txt on every published Site, and workflow run-completion notifications.