OPEN SOURCE · MIT LICENSE

Useful context.
A place to keep it.

Give your next AI conversation a starting point. MemHarbor keeps project context, decisions, and next steps in Markdown files you own, with a history you can review.

Get started locallyExplore the Skill

Markdown + Git. Start with the tools you already use.

memharbor-vaultLOCAL GIT

reading/networking/

  • CONTEXT.md
  • STATE.md
  • DECISIONS.md
  • TODO.md
  • SOURCES.md

## Goal

Learn networking fundamentals.

## Next step

Choose the first book.

# Resume in a new session

Review · approve · commitYour files. Your history.
An example memory vault. No cloud account required.

01 / THE WORKFLOW

Keep the outcome.
Pick up the thread.

Save what will help you later: the decision, the verified fix, the unfinished work. Retrieve it when the next conversation needs it.

01

Draft the useful context

The Skill finds related memories and prepares an update. Review what it will keep before you ask it to save.

Draft a memory of this fix, including what we verified.
02

Save it with a history

Once authorized, the agent writes Markdown, commits it to your vault, and reads it back to check the result.

Save the approved draft and read it back to verify.
03

Resume with the right context

Point a new session at the same vault. Ask for the topic, the current state, or the decision you need.

Find the project’s blockers and next steps. Read only.

02 / THE FORMAT

Plain files.
Lasting context.

Organized around a topic, not a chat transcript. Open the files in your editor, inspect the diff, or read the Git history.

  • CONTEXT.mdThe goal and lasting background
  • STATE.mdWhat is true right now
  • DECISIONS.mdChoices and their reasoning
  • TODO.mdThe work still to do
  • SOURCES.mdEvidence and references

Start with the files a topic needs. Keep stable background separate from changing state.

reading/networking/CONTEXT.md
---
path: reading/networking
title: Networking fundamentals
status: active
---

# Networking fundamentals

Build a practical understanding of networks.
Read one technical book each week.

03 / YOUR FIRST MEMORY

Start small. Stay local.

You need Git and an AI client with file access. The install command also needs Node.js/npm; the guide includes manual installation.

Read the first-use guide

1. Install the Skill

Use claude-code or cursor instead of codex for your client. Open a new session so it discovers the Skill.

npx skills add zyc945/memharbor-skill --skill memharbor --agent codex --copy

2. Create a separate Git vault

Initialize a new directory, check your Git identity, and give the agent access. Keep your vault separate from your software project.

Read the first-use guide

3. Ask for a draft

Review the draft, then ask: “Save the approved draft and read it back to verify.” In a new session, ask the agent to retrieve it from the same vault.

Use memharbor with /absolute/path/memharbor-vault as a local Git vault.
I plan to read one technical book each week. No book chosen yet.
Check for duplicates and show me a draft. Do not save yet.

Works with authorized file/Git access in Codex, Claude Code, and Cursor. Client setup and permissions vary.

04 / ROOM TO GROW

Choose where your
memory lives.

Local Git is the simplest starting point. Optional service tiers add GitHub-backed storage and remote MCP access.

T0 / START HERE

Local Git vault

The Skill works with Markdown and Git on your machine. No MCP service or cloud storage account required.

AI client · Skill · local Git
T1 / OPTIONAL SERVICE

GitHub + stdio MCP

A Node.js MCP server uses a private GitHub repository for persistent memory and a local serving cache.

AI client · stdio MCP · GitHub
T2 / OPTIONAL SERVICE

Worker + R2

A Cloudflare Worker provides remote MCP and REST. GitHub holds canonical history; private R2 serves rebuildable snapshots.

AI client · HTTPS MCP · Worker

The MIT-licensed Skill is public and ready to install. The service source repository is currently private. Service tiers require source access and your own configuration; there is no hosted memory account on this website.

A FEW PRACTICAL DETAILS

Before you begin.

Does it save every conversation?

No. Normal conversation is not saved automatically. Ask for a draft, then authorize the memory changes you want to keep. Existing authorization can cover the save.

Where does my memory go?

With T0, Markdown files and Git history stay in the vault you choose. Cross-device access and backups need separate setup. Optional service tiers use your private GitHub repository. This website does not receive your memories.

Do I need a vector database or another model?

The memory layer uses Markdown, Git, and optional storage adapters. It does not require a vector database, embeddings, or its own LLM. Your AI client does the reading and writing.

What happens if I stop using it?

Removing the Skill leaves your vault intact. You can keep reading and editing the Markdown files with ordinary tools. Git history remains available.

Is this a public cloud memory service?

No. This is an open-source Skill with optional service implementations. You run your own vault or deployment. Native client and remote write acceptance differ by setup; the repository documents the verification scope.

Let the next session start here.

Keep one useful memory. Retrieve it when you need it.

Get the MemHarbor Skill