Skip to main content
plugin CX Codex

memory · dodo-labs-ai, codex — Claude Code plugin: features and installation

memory is a Claude Code plugin that connects to MemForge search and memory tools. Session-start guidance appears automatically; retrieval runs on request.

Apache-2.0 ★ 104 updated 2026-11-17

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add dodo-labs-ai/mem-forge
/plugin install memory@memforge
Open on GitHub

What memory does

The plugin connects an MCP proxy to the MemForge API and adds static guidance when a session starts, resumes, or compacts. The proxy can search and read memories, fetch related files, and create a private memory after confirmation. It does not capture or save anything on its own.

Access to the MemForge API is required. The default target is the local server at http://127.0.0.1:8765/api/v1; set MEMFORGE_API_URL in ~/.codex/config.toml to use another server, and provide MEMFORGE_API_TOKEN separately when bearer authentication is required. Do not add a manual [mcp_servers.memforge] block; the plugin registers its MCP server itself.

What it helps with

  • search MemForge memories by topic
  • read details and retrieve a source file for a memory
  • save a private memory after confirming its preview
  • list recent memories for a chosen time window

Example prompts for the agent

  • Search MemForge for memories about <topic> and show the details of a relevant result.
  • Fetch the source file for this memory and show its local path.
  • Save this as a private memory, but show me the preview first.

How to install memory

Plugin marketplace

/plugin marketplace add dodo-labs-ai/mem-forge
/plugin install memory@memforge

Step by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own

Questions about memory

How do I install memory in Claude Code?

Run these commands in order: /plugin marketplace add dodo-labs-ai/mem-forge, then /plugin install memory@memforge.

What does memory do?

It connects MCP tools for searching and reading MemForge memories, and adds guidance when a session starts. It saves a new memory only after confirmation.

What does memory need to work?

It requires access to the MemForge API. The default target is http://127.0.0.1:8765/api/v1; set MEMFORGE_API_URL for another server and MEMFORGE_API_TOKEN separately when bearer authentication is required.

Source text

memforge-memory · Apache-2.0
# MemForge Memory for Codex

This plugin connects Codex to a MemForge API through a thin local MCP proxy
for memory tools, and adds MemForge usage guidance when a session starts.
The packaged runtime and plugin version is `0.2.0-beta.4`.

With no routing variables, the plugin targets local OSS at
`http://127.0.0.1:8765/api/v1`. Otherwise set the origin in
`~/.codex/config.toml`. `MEMFORGE_API_URL` must be an HTTP(S) origin without an
API path. Set `MEMFORGE_API_TOKEN` separately when bearer authentication is
required.

```toml
[memforge]
MEMFORGE_API_URL = "https://memforge.example.com"
MEMFORGE_API_TOKEN = "..."
```

The same `/api/v1` surface is used for OSS and Cloud. Call `list_workspaces` to
discover accessible workspaces when useful, then pass optional `workspace_id`
to any data tool for a one-request override. It may be omitted when the account
has exactly one accessible workspace or the project has a user-confirmed local
binding. Use the `memforge-setup` skill to bind a Git repository or ordinary
directory.
Use `memforge-daemon-setup` when the agent should securely install, configure,
verify, troubleshoot, or remove the managed local collection daemon.
Repository context remains provenance attribution; it never selects or
authorizes a workspace.

Do not add a manual `[mcp_servers.memforge]` block. The plugin's `.mcp.json`
registers the MCP server; duplicating it in `config.toml` can pin Codex to a
stale plugin cache path after upgrades.

The bundled MCP proxy does not need a local MemForge CLI or local-DB MCP
process. It forwards search, current recent-Memory listing, memory detail, memory write, and Review
calls through the configured immutable target. `get_resource(mode="file")` is
handled locally so returned `local_path` values point to the agent machine.

```text
Codex MCP stdio -> plugin-local proxy -> HTTP(S) MemForge API
get_resource(mode=file) -> ~/.memforge-agent/artifacts -> local_path
```

The proxy negotiates Codex's request-scoped `codex/sandbox-state-meta`
capability. Codex then attaches the current task environment's `sandboxCwd` to
each MCP tool call, allowing the proxy to derive a normalized Git remote
without relying on a process-global directory.
An explicit `repository_context.working_directory` remains available for other
hosts and takes precedence when supplied. Compatible MCP Roots are attribution
fallbacks. Local paths are discarded before OSS or Cloud calls;
malformed negotiated or explicit context fails before HTTP instead of silently
reading another workspace.

Install from GitHub (no checkout required):

```bash
codex plugin marketplace add dodo-labs-ai/mem-forge
codex plugin add memory@memforge
```

Start a new Codex session after install.

To push a local folder as a source, open the MemForge Admin UI, choose
**Add Source -> Local Repository**, and run the printed CLI command.

```bash
# optional
codex mcp get memforge --json
```

Try a search:

```text
Use MemForge to search for "<topic>". If source evidence matters, call
get_memory on the relevant result before citing source details.
```

List current Memories observed from active sources during a resolved time
window without inventing a topic query:

```text
Use MemForge list_recent_memories for 2026-07-21T00:00:00+08:00 through
2026-07-28T00:00:00+08:00. This is a current-Memory view, not a source
changelog. Follow next_cursor with the same filters until has_more is false.
```

Fetch backing evidence:

```text
Search MemForge for "<topic>". Call get_memory for the relevant memory, then
call get_resource with mode="file" on the best content_url or pdf_url and show
the local_path.
```

The plugin registers one hook, `SessionStart`. It adds static MemForge usage
guidance to a new, resumed or compacted session, and it makes no network call
and writes no local state. Per-prompt memory retrieval is left to the MCP
`search` tool, which fetches query-aware context on demand.

The bundled MCP proxy exposes tools such as `search`, `list_recent_memories`,
`get_memory`, and `get_resource`.
`get_resource` fetches `content_url` / `pdf_url` artifacts through
`MEMFORGE_API_URL`; in `file` mode it writes the artifact to
`~/.memforge-agent/artifacts`.

The plugin captures nothing on its own. To keep something, ask Codex to
remember it: the agent shows a preview, and after you confirm it writes one
private Memory with the MCP `create_memory` tool.

## Upgrading from 0.2.0-beta.1 or earlier

Earlier plugin releases uploaded redacted session windows automatically. That
capture is removed, and MemForge refuses those uploads. Update the plugin and
restart Codex:

```bash
codex plugin marketplace upgrade memforge
codex plugin add memory@memforge
```

After the update:

- You can delete `queue.sqlite`, `queue.sqlite-wal`, `queue.sqlite-shm` and
  `worker.lock` in `~/.memforge-agent`; nothing reads them. Keep `~/.memforge-agent/artifacts` if you use
  `get_resource(mode="file")`.
- A `hook_workspace_id` entry in `~/.memforge/workspace-bindings.json` is
  ignored. The `memforge-setup` skill reports it and can remove it.
- Memories captured from earlier sessions belong to the Codex Session
  Source. A MemForge server on a release after 0.2.0b2 retires that Source
  when it upgrades, with the Memories no other Source supports. On a server
  still on 0.2.0b2, delete the Source in the admin UI to retire it the same way.

## Troubleshooting

**Codex shows `MemForge hook skipped: /hooks/receipts returned HTTP 410` or
`MemForge hook skipped: /hooks/receipts returned HTTP 404` at the end of a turn
or at compaction.** An earlier plugin release is still installed, and MemForge
no longer accepts its session uploads: a 0.2.0b2 server answers `410`, and a
later server, which no longer has the upload routes, answers `404`. Update the
plugin with the commands above and restart Codex.

© MemForge Team · Apache-2.0 · dodo-labs-ai/mem-forge

Similar plugins

All plugins for Agent setup: memory, context, orchestration →

memory by other authors comes first.

memory MemForge Team memory is a Claude Code plugin that links the agent to the MemForge API via a local MCP proxy. It adds session guidance and on-demand memory lookup tools. CX Codex ★ 104repo stars para-memory-files paperclipai para-memory-files — a skill for storing knowledge and facts across IA coder sessions. Organizes memory by the PARA method: projects, areas, resources, and archives in separate files, with vector and keyword search. CX Codex +1 1,900installs memory-reflect basicmachines-co memory-reflect is a Claude Code skill that reviews recent project logs and merges durable decisions into persistent notes. It runs on a scheduled heartbeat or on request. CX Codex +1 1,500installs memory-capture basicmachines-co memory-capture turns the current outcome of a conversation into a Basic Memory note and revises that note when run again. Use it when a thread has produced decisions or context worth keeping. CX Codex +1 1,500installs memory-management aaron-he-zhu memory-management is a Claude Code skill for project working memory. It saves, retrieves, merges, and archives notes when an agent handles cross-session context or an erasure request. CX Codex +1 1,200installs memory-intake nhadaututtheky memory-intake turns messy notes and conversations into typed memories with tags, priority and expiry. Useful when raw input needs to be filed instead of dumped. CX Codex +1 780installs video-memory oxbshw video-memory is a Claude Code skill that searches videos watched in earlier sessions. Ask about a past clip, a meeting decision, or a topic covered across several recordings. CX Codex +1 748installs

From the same set8

memory memory is a Claude Code hook that loads MemForge guidance and MCP memory tools at session start. It triggers automatically whenever a session starts, resumes, or compacts. CX Codex ★ 104repo stars memory memory is a Claude Code plugin that links the agent to the MemForge API via a local MCP proxy. It adds session guidance and on-demand memory lookup tools. CX Codex ★ 104repo stars lifecycle-canary-convergence lifecycle-canary-convergence is a Claude Code skill that checks Memory lifecycle state through an inventory, dry-run, apply, and audit. It runs before another retry or canary. CX Codex +1 ★ 104repo stars self-hosted-release-validation self-hosted-release-validation is a Claude Code skill that validates OSS self-hosted releases via Docker Compose. Evaluates SQLite persistence, agent sources, and beta readiness. CX Codex +1 ★ 104repo stars memforge-setup memforge-setup is a Claude Code skill for configuring MemForge workspace routing. It runs on requests to bind or remove a project binding, or to diagnose workspace selection. CX Codex +1 ★ 104repo stars plugin-release-validation plugin-release-validation is a Claude Code skill that validates MemForge memory plugin releases via remote marketplace paths. Runs when testing RC tags, checking caches, hooks, and MCP servers. CX Codex +1 ★ 104repo stars memforge-daemon-setup memforge-daemon-setup is a Claude Code skill that installs and configures the MemForge local daemon as a macOS or Linux user service. It runs for requests to connect, inspect, repair, or remove that service. CX Codex +1 ★ 104repo stars

Project sponsors

Companies that keep this analytics open