词映 AI导航
工具库Skills 技能
我的收藏
词映 AI导航

Maestro Memory for Claude Code and Codex

Save project facts, daily notes, and lasting practices in a local store that Claude Code and Codex can query through MCP. The skill supports deliberate recall and requires confirmation for entries marked as key rules.

中文

Install in Claude Code、Codex

Use Claude Code or Codex with local MCP support. Maestro Memory 5.3.0 requires Node.js 22.19 through the 22.x line, or Node.js 24 and later. The example writes to local storage. Starting the pinned package via `npx` for the first time requires npm access.

  1. Get the complete `skills/memory/` folder from the pinned commit. For a project install, place it under `.claude/skills/` for Claude Code or `.agents/skills/` for Codex.
  2. Add a local stdio server named `maestro-memory` to `mcpServers` in the Claude Code project `.mcp.json`, or to `mcp_servers` in Codex user `~/.codex/config.toml`. Use command `npx` and args `-y`, `-p`, `@ddtcorex/maestro-memory@5.3.0`, `maestro-memory-mcp`. Merge the entry using each client's config format.
  3. Start with an empty demo project. Set `MAESTRO_MEMORY_DIR` in both server environments to one dedicated test store. Restart both clients and open the same demo project in each.

Example task

In Claude Code, open the demo project and send this after connecting the test store.

Use the memory skill to search for “demo backup”. If an identical project fact is absent, save this ordinary project fact: demo backups use the filename demo-backup-YYYYMMDD.zip. Return the entry ID.

Open the same project in Codex and ask it to search project memory for “demo backup”.

What to check

Claude Code should write one project entry and return a reference. Codex should retrieve the naming convention from the same store. A second search should reveal the existing record before any write is attempted.

Original SKILL.md on GitHub · Updated

Frequently asked question

Why can't the second client find a project fact?

Verify that both MCP processes use the same absolute store path and both sessions open the same project directory. Project entries are scoped by path. Restart MCP processes started before the settings changed.