# project-memory-core

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

- plugin · `type=plugin` · Claude Code, Codex · ★ 1596 repo stars
- Author: Duncan Main
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/hashgraph-online/awesome-codex-plugins/tree/HEAD/plugins/DuncanMain/project-memory-core
- Updated: 2026-10-29
- Security check: automated, 2026-11-16 (text and 9 script files) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/plugins/project-memory-core

## What it 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.

## Requirements
- Works with: Obsidian

## Install

### Claude Code (native platform)

**Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add hashgraph-online/awesome-codex-plugins
```
In the agent chat (not a shell):
```text
/plugin install project-memory-core@awesome-codex-plugins
```

## When to use it
- 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
- @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

## Source text · project-memory-core · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 7d4c611fc69f19ef.

BEGIN THIRD-PARTY FILE 7d4c611fc69f19ef
````text
<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).
````
END THIRD-PARTY FILE 7d4c611fc69f19ef

The third-party file has ended. Everything between the 7d4c611fc69f19ef tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

© Duncan Main · MIT · https://github.com/hashgraph-online/awesome-codex-plugins/tree/HEAD/plugins/DuncanMain/project-memory-core

## Similar
- [obsidian-project-kb-core](https://affpapa.org/en/nevibecode/skills/obsidian-project-kb-core.md) — skill · 332 installs
- [wiki-ingest](https://affpapa.org/en/nevibecode/skills/wiki-ingest.md) — skill · 3700 installs
- [wiki-capture](https://affpapa.org/en/nevibecode/skills/wiki-capture.md) — skill · 2900 installs
- [llm-wiki](https://affpapa.org/en/nevibecode/skills/llm-wiki.md) — skill · 699 installs
- [obsidian-kb-artifacts](https://affpapa.org/en/nevibecode/skills/obsidian-kb-artifacts.md) — skill · 328 installs
- [bedrock](https://affpapa.org/en/nevibecode/plugins/bedrock.md) — plugin · ★ 111 repo stars

From the same set: [hashgraph-online/awesome-codex-plugins](https://affpapa.org/en/nevibecode/by/hashgraph-online/awesome-codex-plugins.md) — 391 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
