Marketplace plugins that connect coding agents to an ai-memory server you run. Everything in this directory, and the catalogs at the repository root (.claude-plugin/marketplace.json, .agents/plugins/marketplace.json), is generated by ai-memory render-plugins. A test fails when the committed files differ from the generator, so edit the templates under crates/ai-memory-cli/templates/plugin/ and re-render instead.

Directory	Harness	Install
`claude-code/`	Claude Code (CLI and the desktop Code tab)	`claude plugin marketplace add akitaonrails/ai-memory`, then `claude plugin install ai-memory@ai-memory`
`codex/`	Codex (CLI and desktop)	`codex plugin marketplace add akitaonrails/ai-memory`, then `codex plugin add ai-memory@ai-memory`, then trust the hooks in `/hooks`

The catalogs pin each plugin to the release tag (vX.Y.Z), so a marketplace add only ever installs released plugin content, never unreleased edits on a branch.

What a plugin runs

Each plugin holds manifests, the ai-memory routing skills, a status skill, an MCP entry that runs ai-memory mcp-bridge, and one POSIX shell script, scripts/ai-memory-hook. There is no bundled binary, no build step and no first-run download.

The script hands each lifecycle event to the installed binary's native ai-memory hook command, the same command ai-memory install-hooks wires. That command applies capture policy (ignore_paths, allowlist mode, server profiles) before the event is spooled or sent, and delivers it only to your ai-memory server. The script itself sends nothing. Without the binary it prints one line of guidance at session start and exits 0, so the agent is never blocked.

No telemetry, and no credentials in any plugin file: hooks and the MCP bridge use the credentials the ai-memory CLI already stores.

The binary is installed separately

Install ai-memory once (install script, Homebrew, AUR, RPM, the Docker wrapper, or the macOS app) and run ai-memory setup. ai-memory upgrade updates the Claude Code plugin after replacing the binary, and ai-memory doctor reports the plugin, version skew against the binary, and double wiring with settings-file hooks.

See docs/install.md in the repository for the full guide.