---
title: "Agent plugins"
description: "A plugin sends your coding agent's sessions to past.dev and recalls memory into your prompts. You write no code."
canonical: https://past.dev/docs/plugins/overview
last-updated: 2026-10-12
---
# Agent plugins

> A plugin sends your coding agent's sessions to past.dev and recalls memory into your prompts. You write no code.

Product: past.dev Plugins. Source: https://past.dev/docs/plugins/overview

A past.dev plugin runs beside your agent on your own machine. When a session is over, it sends what you and the agent said to a past.dev project. Before the model reads a prompt, it recalls what the project remembers about that prompt and adds it to the context.

Each plugin is open source under the MIT license and calls only the public Memory API: `POST /api/v1/ingest/batch`, `POST /api/v1/recall` and `GET /api/v1/audiences/{slug}`. Anything a plugin does, your own code can do with the same project key.

### Which plugin to install

| Agent | Plugin |
| --- | --- |
| Claude Code (terminal, desktop app, IDE extensions) | [Claude Code plugin](/docs/plugins/claude-code). Recall on every prompt. |
| Codex (CLI and the ChatGPT desktop app) | [Codex plugin](/docs/plugins/codex). Recall on every prompt, after you trust its hooks. |
| Cursor | [Cursor plugin](/docs/plugins/cursor). Recall on every prompt, and the `past_recall` tool. |
| Junie in a JetBrains IDE | [JetBrains plugin](/docs/plugins/jetbrains). Junie calls the `past_recall` tool when it needs memory. |
| Hermes Agent | [Hermes provider](/docs/plugins/hermes). Recall before each message, and the `past_recall` tool. |

For an agent that runs no plugin, such as Claude on the web, the Codex IDE extension or Codex cloud tasks, connect the [MCP server](/docs/mcp/overview) instead. A plugin adds recall to every prompt. Through MCP, recall happens only when the model decides to call a tool.

### What a plugin sends

- The prompts you typed and the agent's replies.
- The name of the project folder and the git branch the agent works in.
- Nothing else. Tool calls and their results, file contents, diffs, command output and subagent threads stay on your machine.
- Strings that look like keys, tokens or private keys are replaced with `[redacted]` before anything is sent, in the sessions and in the recall queries.

A session is sent in sittings. A new sitting starts where the session was quiet for 30 minutes. Each sitting is one data point, dated at its first turn, so a memory takes the date it was said. A sitting that past.dev has already received is not sent again.

### What a plugin reads

A plugin recalls from the project its key belongs to, as the identity you connected with. It reads only what that identity's audiences allow. See [Access control](/docs/memory-api/access-control).

### Credits

A plugin spends credits like any other client of the Memory API. Each sitting it sends is one ingested data point, and each recall is one recall call. [Pricing](/pricing) gives the rates for each plan. The history command of each plugin shows the number of sessions and the credits they cost before it sends anything.

**Get API key.** Sign up and start with 150,000 credits, 400,000 with a work email. No card required, and nobody approves the account. Then create a project key in the console and install a plugin. Get API key: https://sso.past.dev/sign-up