# chat-recall docs

> chat-recall indexes the session transcripts of AI coding tools (Claude Code, Codex, Cursor, OpenCode, Antigravity, Hermes, Pi), redacts secrets, and syncs them to a server that an assistant searches through an MCP server.

## Start here

- [chat-recall documentation](https://chatrecall.dev/docs/index.md): How to install chat-recall, connect your AI coding tools, run your own server, and use the MCP tools.

## Tutorial

- [Your first recall](https://chatrecall.dev/docs/first-recall.md): In this tutorial, we install chat-recall, send our existing AI sessions to the server, and ask an assistant about work it did not see.

## How-to guides

- [Install](https://chatrecall.dev/docs/install.md): That indexes the transcripts already on your disk, detects which AI tools you have, and registers the MCP server in each of their configs:
- [Connect your AI tools](https://chatrecall.dev/docs/connect.md): chat-recall init does this for you.
- [Connect claude.ai or ChatGPT](https://chatrecall.dev/docs/connectors.md): An assistant that cannot run the chat-recall CLI, such as claude.ai, ChatGPT or a browser IDE, connects to the remote MCP endpoint of your server.
- [Give a new session your context](https://chatrecall.dev/docs/wake-up.md): This guide gives a new AI session the decisions, preferences and facts of your earlier work, and the state of the work you want to continue.
- [Run sessions that work together](https://chatrecall.dev/docs/sessions.md): One AI session can start other sessions, give them work and get their results.
- [Sync skills, MCP servers, commands and agents across your tools](https://chatrecall.dev/docs/toolkit.md): Each AI tool keeps its own skills, MCP servers, commands and agents.
- [Keep decisions with the decision guard](https://chatrecall.dev/docs/guard.md): The decision guard runs before an agent's tool call.
- [Work with a team](https://chatrecall.dev/docs/teams.md): A team shares projects, a task board and a library of skills, commands, agents and MCP servers.
- [Control what syncs](https://chatrecall.dev/docs/sync-control.md): chat-recall sends the transcripts of your AI tools to your server, with secrets masked.
- [Handle a secret that reached a session](https://chatrecall.dev/docs/leaked-secret.md): An API key, a token or a password that you pasted into an AI session is in that tool's transcript on your disk.
- [Index a codebase](https://chatrecall.dev/docs/code-index.md): chat-recall can analyse a repository with codeindex and keep the results on your server: findings, hotspots and a ranked list of actions.
- [Back up your chats with the Vault](https://chatrecall.dev/docs/vault.md): The Vault keeps an encrypted copy of your AI sessions on the server, and puts them back on another machine.
- [Self-hosting chat-recall](https://chatrecall.dev/docs/self-hosting.md): Run the whole thing on your own machine.
- [Troubleshooting](https://chatrecall.dev/docs/troubleshooting.md): It checks the login, the server, the credentials, the hooks of each AI tool, the MCP server and codeindex, and names the command that fixes each problem.

## Reference

- [CLI commands](https://chatrecall.dev/docs/cli.md): Every command of the chat-recall CLI, with its options.
- [MCP tools](https://chatrecall.dev/docs/mcp-tools.md): The chat-recall MCP server has 68 tools.
- [Hooks](https://chatrecall.dev/docs/hooks.md): chat-recall init and chat-recall install-hooks install these hooks.
- [Environment variables](https://chatrecall.dev/docs/environment.md): Every knob is optional — chat-recall runs with sane defaults.
- [What is indexed, and where it lives](https://chatrecall.dev/docs/data.md): The CLI keeps almost nothing locally — just what it needs to reach the server:

## Explanation

- [How chat-recall works](https://chatrecall.dev/docs/how-it-works.md): chat-recall has two parts: a CLI on each machine, and a server.
- [Memory and wake-up](https://chatrecall.dev/docs/memory.md): A new AI session knows nothing about your past work.
- [How search works](https://chatrecall.dev/docs/how-search-works.md): Search runs on the server, in Postgres.
- [How sync works](https://chatrecall.dev/docs/how-sync-works.md): The CLI sends your sessions to the server and makes sure that none is lost on the way.
- [Secret detection](https://chatrecall.dev/docs/secret-detection.md): How chat-recall keeps credentials out of the index, and why it is built this way.

## For developers

- [Adding an AI coding tool](https://chatrecall.dev/docs/adding-a-tool.md): chat-recall reads seven tools today: Claude Code, Codex, OpenCode, Antigravity, Cursor, Hermes Agent and Pi.