# Install the Ditto Plugin > Add the official Ditto marketplace, install the plugin in your AI client, and connect memory for the start and end of a task. --- The Ditto plugin brings memory and skills into your AI client. Choose your client below, install Ditto, then sign in to your Ditto account when the client prompts you. The plugin connects to `https://api.heyditto.ai/mcp` through the client's own OAuth sign-in. You do not need API keys, npm helpers, or a separate Ditto CLI setup. **Adding the marketplace alone does not install the plugin.** A marketplace is a catalog. You still need to select and install Ditto from it, enable the plugin, and connect your account. The official repository is [ditto-assistant/ditto-plugins](https://github.com/ditto-assistant/ditto-plugins). Client availability and organization policies can vary. These instructions follow its current [installation guide](https://github.com/ditto-assistant/ditto-plugins#install). ## Claude Desktop, Chat, and Cowork 1. Install [Claude Desktop](https://claude.com/download), or open [claude.ai](https://claude.ai). Sign in to the Claude account and workspace where you want to use Ditto. The plugin follows your Claude account. 2. In Desktop, select **Chat** or **Cowork** first. In the sidebar, open **Customize → Plugins**. Some accounts show **Plugins** directly. 3. Select **Add → Add marketplace → Add from a repository**. Enter `https://github.com/ditto-assistant/ditto-plugins`, then sync or add the marketplace. 4. Find **Ditto** in that marketplace and select **Add**. Enable it if prompted. 5. Open the installed plugin and connect or sign in to Ditto. Under **Yours**, confirm Ditto is enabled, **Connectors** shows Ditto **Connected**, and **Skills** lists `ditto-memory`, `handoff`, `weekly-review`, and the other Ditto skills. 6. Start a new chat, type `/`, and look for the Ditto skills before sending your request. A Ditto plugin installed in Claude Code is a separate installation; it does not mean Ditto is installed in Chat. If the marketplace or plugin is unavailable, ask your Claude organization owner to check plugin policy. Other work connectors are optional. After connecting Ditto, you can attach the host's own connectors for the services you want to use; they are not required to install Ditto. ## Claude Code Run these inside Claude Code: ```text /plugin marketplace add ditto-assistant/ditto-plugins /plugin install ditto@ditto-claude-plugins ``` Open `/mcp` to inspect and authenticate the plugin-provided Ditto server. The marketplace keeps its historical name, `ditto-claude-plugins`, even though the GitHub repository is now `ditto-plugins`. To update an existing installation: ```text /plugin marketplace update ditto-claude-plugins /plugin update ditto@ditto-claude-plugins /reload-plugins ``` ## Cursor Sign in to Cursor before running this in your terminal. Use the full URL; the `owner/repo` shorthand is rejected: ```sh agent plugin marketplace add https://github.com/ditto-assistant/ditto-plugins ``` Then select and install **Ditto** from the added marketplace for your user or project. Teams can import the repository through **Dashboard → Plugins & MCPs → Add Marketplace → Import from Repo**. If Ditto is available in your Cursor Marketplace, you can also find it under **Customize** and install it there; directory availability is separate from repository installation. Sign in to Ditto under **Customize → MCP servers**. Skills load under **Agent Decides** and can be invoked by name, such as `/ditto-memory`. ## Codex Run in your terminal: ```sh codex plugin marketplace add ditto-assistant/ditto-plugins codex plugin add ditto@ditto-plugins ``` Alternatively, install Ditto from `/plugins`. Complete the sign-in prompt, then check the connection in `/mcp`. ## Grok Build Run in your terminal: ```sh grok plugin marketplace add ditto-assistant/ditto-plugins grok plugin install ditto --trust ``` Plugins need trust to attach their MCP server. Check Ditto in `/mcps` and sign in when prompted. Skills appear as `/ditto:`, for example `/ditto:ditto-memory`. ## GitHub Copilot CLI and VS Code Run in your terminal: ```sh copilot plugin marketplace add ditto-assistant/ditto-plugins copilot plugin install ditto@ditto-plugins ``` In Copilot CLI, use `/mcp` to connect. In VS Code, add the marketplace repository from the agent plugins view, install Ditto, then start and sign in to the Ditto server from the MCP servers view. ## Antigravity Run in your terminal: ```sh agy plugin install https://github.com/ditto-assistant/ditto-plugins ``` Sign in through the MCP servers panel when prompted. Gemini CLI is not supported by this plugin; use Antigravity instead. ## Kimi Code Run inside a Kimi Code session: ```text /plugins install https://github.com/ditto-assistant/ditto-plugins ``` Choose **Trust and install**, then run `/reload`. Check `/plugins list`: Ditto should have its skills and one MCP server. Open `/mcp`, then authenticate with: ```text /mcp-config login plugin-ditto:ditto ``` ## ChatGPT availability The repository currently describes ChatGPT directory installation as available **once listed**. This guide does not confirm a live directory listing. See the repository's [ChatGPT notes](https://github.com/ditto-assistant/ditto-plugins/tree/main/docs/openai) for current packaging and listing information; those maintainer steps are not a user installation flow. For the separate custom-connector route, use [Ditto MCP Server](/docs/mcp-server). A custom MCP connector and a marketplace plugin are different setup paths. ## Recall at the start, hand off at the end **There are no lifecycle hooks to configure in the current marketplace plugin.** It does not inject context on every prompt or automatically save transcripts. Memory moves through skills and the hosted MCP connection, within your permissions. - **At the start of work or an automation:** invoke `ditto-memory` and ask it to recall relevant context. For example: “Use ditto-memory to find the latest decisions and open work for this project. Fetch the memories you rely on before starting.” Use your host's skill menu or invoke the skill by name. - **As work progresses:** ask for a private save, or authorize ongoing private capture for the task. The skill records useful facts and decisions rather than every exchange. It does not enable automatic capture by itself. - **When finishing or archiving a task:** invoke `handoff` to save verified outcomes, constraints, open work, links, and the next step. Ask it to save the note and read it back. Archiving depends on host support; a saved memory does not prove the chat was archived. For recurring automations, include these recall and save instructions in the automation's task instructions. Installing the plugin alone does not schedule them or guarantee that every session will run them. See [Make Ditto Part of Your AI Workflow](/docs/ai-assistant-memory-workflow) for a reusable instruction and [Agent Integrations](/docs/agent-integrations) for other connection paths. ## Check your setup Start a new conversation and ask: “Use ditto-memory to search for relevant existing context. Report connection or permission errors; do not save a test memory.” Confirm the client actually uses Ditto and reports any errors. Seeing skills in a menu proves they loaded, not that memory access succeeded. If skills are missing, check that you installed and enabled Ditto after adding the marketplace, then reload plugins or open a new conversation. If the server needs authentication, reconnect through the client's MCP or connector controls using the intended Ditto account. For help, contact [support@heyditto.ai](mailto:support@heyditto.ai) with the client name and error message, without credentials.