Skip to main content
plugin CX Codex

project-memory-core — Claude Code plugin: what it does and setup

project-memory-core keeps architectural decisions, task status, and codebase context inside a local Obsidian vault as plain Markdown files.

MIT ★ 1,596 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add hashgraph-online/awesome-codex-plugins
/plugin install project-memory-core@awesome-codex-plugins
Open on GitHub

What project-memory-core does

The plugin retains essential development context inside a local Obsidian vault instead of letting choices vanish in closed chat sessions. On first launch, it helps connect or initialize a vault, registers the current repository, and writes a central Project Home.md document. It scans the codebase to outline the repository layout, commands for running and testing, active priorities, and architectural boundaries.

During routine coding, the plugin identifies details that matter for future tasks and prompts for user approval before saving them. Dedicated templates organize decisions, debugging notes, established procedures, and handoffs. You can also request a memory check, prompting the assistant to report broken links, conflicting records, or completed items still marked as active.

Everything is stored as plain Markdown on your local disk. The tool runs without accounts, telemetry, remote servers, or Obsidian community extensions. It never writes durable records without clear user intent, keeping project documentation fully inspectable and editable.

What it helps with

  • Store architectural decisions and their rationales directly in a local Obsidian vault.
  • Scan the repository layout to generate an initial Project Home.md overview.
  • Document debugging findings, operational procedures, and verified system constraints.
  • Audit project notes to catch outdated statuses, dead links, and conflicting choices.

Example prompts for the agent

  • @PMC set up lasting memory for this project in my Obsidian vault
  • @PMC what do we already know about authentication?
  • @PMC check this project's memory and surface stale decisions

How to install project-memory-core

Plugin marketplace

/plugin marketplace add hashgraph-online/awesome-codex-plugins
/plugin install project-memory-core@awesome-codex-plugins

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

Questions about project-memory-core

How do I install project-memory-core in Claude Code?

First, add the marketplace with /plugin marketplace add hashgraph-online/awesome-codex-plugins, then run /plugin install project-memory-core@awesome-codex-plugins to finish installation.

What does project-memory-core do?

It connects your coding agent to an Obsidian vault, builds a central Project Home.md, and persists project constraints, decisions, and tasks in Markdown.

Does project-memory-core require an account or Obsidian extensions?

No, it operates entirely with local Markdown files, requiring no external account, remote servers, telemetry, or Obsidian community plugins.

Source text

project-memory-core · MIT
<p align="center">
  <img src="assets/logo.svg" alt="PMC" width="128" />
</p>

<h1 align="center">Give Codex a memory it can use</h1>

<p align="center"><strong>Stop explaining the same project in every task.</strong></p>

<p align="center">PMC turns approved project knowledge into private, portable Markdown inside your Obsidian vault.</p>

---

## The problem PMC solves

Yesterday's Codex task learned why an architecture was chosen, which requirement cannot change, what failed in production, and what should happen next. A new task usually starts without that context.

PMC gives the project a trustworthy place to restart.

| Without PMC | With PMC |
|---|---|
| Re-explain the project repeatedly | Start from a focused Project Home |
| Decisions disappear into old chats | Preserve decisions with rationale and evidence |
| Notes drift away from the code | Surface stale or contradictory knowledge |
| Documentation becomes an unstructured dump | Save only reviewed, durable information |
| Knowledge is trapped in one product | Keep ordinary Markdown you own |

## Your first useful result takes one prompt

> **@PMC set up lasting memory for this project in my Obsidian vault**

PMC guides you through creating or connecting a vault, registers the repository, builds a polished `Project Home.md`, and offers to scan the codebase. The scan can capture:

- what the project does;
- how the repository is organised;
- important run, test, and build commands;
- current status and next actions;
- verified constraints, decisions, discoveries, and procedures.

No terminal commands or configuration syntax are required.

## Work naturally

Use plain requests rather than memorising a command language:

```text
@PMC remember this
@PMC remember the decision we just made
@PMC update the project status
@PMC what do we already know about authentication?
@PMC wrap up this task
@PMC check this project's memory
```

During normal work, PMC notices information likely to matter later and asks one clear question before promoting it:

> **This will matter in future tasks. Add it to the project's Obsidian vault?**

## A useful Obsidian front door

Every configured project receives a scannable Project Home with status, current focus, commands, decisions, risks, next actions, and links to deeper notes. Focused templates cover:

- decisions;
- constraints;
- discoveries;
- procedures;
- debugging lessons;
- current state and handoffs.

## Keep the memory trustworthy

Ask PMC to check the project's memory. It can find broken links, overdue reviews, contradictory decisions, stale status, missing setup knowledge, completed actions still shown as active, and important repository changes not reflected in the vault.

Semantic changes are proposed for review rather than silently rewritten.

## Private by design

- Local Markdown only.
- No PMC account.
- No developer server or telemetry.
- No raw transcript capture.
- No Obsidian community plugin required.
- No durable write without user intent or approval.
- Easy to inspect, edit, sync, version, export, or delete.

## Start here

- [Quickstart](docs/quickstart.md)
- [Complete user guide](docs/user-guide.md)
- [Automatic orientation](docs/automatic-orientation.md)
- [Privacy](docs/privacy.md)
- [Support](docs/support.md)

PMC is MIT licensed. See [LICENSE](LICENSE).

© Duncan Main · MIT · hashgraph-online/awesome-codex-plugins

Similar plugins

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

From the same set391

The whole set →
quality-engineering-skills Twenty-three quality engineering skills and eight agents for automotive and manufacturing teams: 8D, FMEA, PPAP, APQP, SPC, MSA, ISO 9001 and IATF 16949 audits. CX Codex ★ 1,596repo stars codex-project-autopilot codex-project-autopilot guides project creation from raw concept to handoff: conducts discovery quizzes, drafts three plan tiers, coordinates roles, and prepares deployment checklists. CX Codex ★ 1,596repo stars pro-launch pro-launch guides a product from idea to release with phase gates and concrete artifacts. Use it for naming, UI work, GTM planning, and shipping. CX Codex ★ 1,596repo stars praxis praxis — a plugin for Claude Code and Codex that brings workflow discipline to coding agents: you state the goal and what done looks like, not the steps. CX Codex ★ 1,596repo stars personal-data-protection personal-data-protection is a plugin for Claude Code and Codex that groups personal-data duties in six Southeast Asian countries by stack layer. It includes checklists for new features, data fields, vendors and breaches. CX Codex ★ 1,596repo stars odw odw — a plugin for Claude Code and Codex: runs multi-agent workflows through a local daemon. Parallel agents operate in the background without blocking the main chat. CX Codex ★ 1,596repo stars ontoly ontoly guides agents to use a Software Graph, CLI reports, and MCP when examining a repository. It covers architecture, dependencies, request paths, and change impact. CX Codex ★ 1,596repo stars oh-my-openspec oh-my-openspec — a spec-first workflow for Codex CLI and OpenCode, where an MCP gate checks the finished work against the written spec. CX Codex ★ 1,596repo stars

Project sponsors

Companies that keep this analytics open