Early days. Memcrate ships Claude Code, Claude Desktop, and Codex integrations today. Cursor, Aider, and an MCP server are on the roadmap - see the repo for status.

Claude Code, Claude Desktop, and Codex

All three have a Memcrate integration today, and all three read the same SKILL.md format, so one canonical set of skills serves them. Cursor, Aider, and MCP are on the roadmap.

Install

From any directory:

memcrate

One command installs into both tools:

~/.claude/skills/          ~/.codex/skills/
├── save/SKILL.md          ├── save/SKILL.md
├── load/SKILL.md          ├── load/SKILL.md
└── pin/SKILL.md           └── pin/SKILL.md

On Windows those are %USERPROFILE%\.claude\skills\ and %USERPROFILE%\.codex\skills\.

Both tools pick the skills up on the next prompt. No restart, no permission setup.

Use

In any Claude Code or Codex session, the three verbs are typed commands. The prefix differs between the two tools:

VerbClaude CodeCodex
load/load$load
save/save$save
pin/pin$pin

Claude Code uses a leading slash; Codex invokes skills with a leading dollar sign. Same skill file, same behavior, different prefix.

Each one runs the matching skill. The skills handle:

  • Finding your vault (the path recorded at setup, with fallbacks if it moved)
  • Reading the canonical context files
  • Writing session logs and context updates in the right format

What each skill does

/load

Reads Core/Context/Profile.md, Core/Context/Projects.md, Core/Context/Current State.md, and the three most recent session logs. Gives you a short oriented summary. Accepts an optional argument to scope by topic or number of sessions.

/save

Reviews the current session and writes a structured log to Core/Sessions/YYYY-MM-DD-slug.md with frontmatter and the standard sections.

/pin

Promotes a fact, decision, or preference from the current session into one of the canonical context files. Figures out which file (Profile / Projects / Current State) and updates it in place.

Vault discovery

Setup writes your vault’s full path into the installed skills. The skills try these in order, and the first one that finds Core/Context/Profile.md wins:

  1. The path recorded at setup
  2. The current working directory
  3. ~/memcrate-vault, the default location
  4. A scan one level deep in your home directory for */Core/Context/Profile.md (catches custom locations like ~/myvault)

If none of them finds a vault, /load asks you where it is.

A step that fails, including a read your tool blocks, moves on to the next one instead of stopping. Your home directory comes from the environment ($HOME, or $env:USERPROFILE in PowerShell), never from a guessed username, so the same steps work on Windows.

Step four names the concrete call for each tool, since an explicit instruction is followed more reliably than an abstract one: Claude Code uses its Glob tool, Codex runs ls -d.

So a vault anywhere on disk works without configuration. If you move it later, run memcrate --vault <new path> once and the skills record the new location.

Skills you already own

Memcrate marks every skill it installs and never replaces a skill it did not install. If you already have your own load, save, or pin, it leaves yours alone and installs all three of its verbs in that tool under prefixed names:

VerbClaude CodeCodex
load/memcrate-load$memcrate-load
save/memcrate-save$memcrate-save
pin/memcrate-pin$memcrate-pin

Setup tells you which names it used. The choice is made per tool, so your own load in Claude Code does not rename the verbs in Codex. If you later remove your own skill, run memcrate again and it switches back to the plain names.

If one of the prefixed names is also taken by a skill Memcrate did not install, setup skips that tool, names the skill in the way, and still sets up the other tool.

Upgrading

Each Memcrate release ships the latest skill files. To upgrade:

memcrate

This refreshes the skill files in place with the current versions.


Claude Desktop

Nothing extra to install. Claude Desktop’s local agent mode reads the same ~/.claude/skills/ directory Claude Code does, so the memcrate run above already set it up. Type /load, /save, and /pin exactly as you would in the terminal.

Skills you upload through the Claude web UI are a separate thing. Those live in your account and sync down into a cache Claude Desktop manages, and they can’t reach a vault on your disk. For local work you want the filesystem install above, which is what memcrate does.


Other tools

The roadmap (in priority order):

  • Cursor - .cursorrules template that maps natural-language patterns to the verbs
  • Aider - .aider.conf.yml rewriter that adds the canonical context files
  • MCP - mcp-memcrate server exposing vault_save, vault_pin, vault_load, vault_search

Until those ship, the vault format works with any tool that can read files. Point your tool at the four canonical files and you get most of the value.