Memcrate memcrate

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.

Quick start

From an empty machine to your first load in Claude Code or Codex. About five minutes.

1. Install the CLI

curl -fsSL https://memcrate.dev/install.sh | sh

Other platforms and methods: install guide.

2. Run it

memcrate

One question, then it does the rest: creates your vault and installs the skills for Claude Code and Codex.

Where should your vault live? [~/memcrate-vault]:
>

Created your vault at ~/memcrate-vault.

Installed 3 skills for Claude Code to ~/.claude/skills
Installed 3 skills for Codex to ~/.codex/skills

You end up with the minimum viable shape:

~/memcrate-vault/
├── Core/
│   ├── Context/
│   │   ├── Profile.md
│   │   ├── Projects.md
│   │   └── Current State.md
│   └── Sessions/
└── .memcrate

The .memcrate file is a marker - it tells the CLI and skills “this folder is a Memcrate vault.”

The skills land in ~/.claude/skills/ and ~/.codex/skills/ as load/, save/, and pin/. Both tools pick them up automatically, no restart needed.

Re-running memcrate is safe: it reuses an existing vault and refreshes the skills.

Options

memcrate --vault ~/notes    # skip the location prompt
memcrate --yes              # take every default (implied when there is no terminal)
memcrate --full             # also create Projects/, Daily/, Tasks/, Inbox/

3. Tell it who you are (optional)

memcrate profile

Four questions - your name, what you build, the tools you use daily, and the projects you’re on - written into Profile.md and Projects.md. Enter skips any of them.

Nothing depends on this step. You can edit those two files by hand instead, or just let /pin fill them in as you work.

4. Use the verbs

Open Claude Code or Codex in any directory. At the start of a session, type the load verb. Claude Code uses a leading slash, Codex a leading dollar sign:

/load     # Claude Code
$load     # Codex

Claude reads your Profile.md, Projects.md, Current State.md, and the three most recent session logs, and gives you a short oriented summary.

Work for a while. When you’re done:

/save     # Claude Code
$save     # Codex

Claude writes a structured session log to Core/Sessions/ - decisions, learnings, files touched, what’s pending.

When something from the conversation is worth keeping permanently:

/pin      # Claude Code
$pin      # Codex

Claude figures out which context file the insight belongs in (Profile, Projects, or Current State), edits it, and bumps the last_updated field.

What’s next?

  • Browse your vault. Open ~/memcrate-vault in Obsidian, VS Code, or any text editor. You own the files.
  • Sync across machines. Use Obsidian Sync, iCloud Drive, Dropbox, or git - anything that mirrors a folder. The vault doesn’t care.
  • Read the references. The vault and the verbs explain the design in more depth.