The Problem

Every new Claude Code session starts from zero:

You: "Remember our auth setup from yesterday?"
Claude: "I don't have context from previous sessions..."
Copy

You end up re-explaining the same decisions, architecture, and constraints — over and over.

How MeMesh Helps

MeMesh gives Claude a persistent memory that survives across sessions:

# Monday: You make a decision
buddy-remember "auth"
# → JWT auth: access tokens 15min, refresh tokens 7 days
# → Decided on Jan 15, stored permanently
Copy

Your project decisions, architecture context, and debugging history — all remembered automatically.

Install

Prerequisites: Claude Code CLI and Node.js >= 20

npm install -g @pcircle/memesh
Copy

Restart Claude Code. That's it.

Verify it works — in a new Claude Code session, type:

buddy-help
Copy

If you see a list of available commands, MeMesh is running.

git clone https://github.com/PCIRCLE-AI/claude-code-buddy.git
cd claude-code-buddy
npm install && npm run build
Copy

Usage

MeMesh provides 3 core commands inside Claude Code:

Examples:

buddy-do "explain this codebase"
buddy-do "add user authentication"
buddy-remember "API design decisions"
buddy-remember "why we chose PostgreSQL"
Copy

Memories are stored locally on your machine and persist across sessions (90 days for decisions, 30 days for session context).

Troubleshooting

MeMesh not loading?

# Check installation
npm list -g @pcircle/memesh

# Check Node.js version (needs >= 20)
node --version

# Repair installation
memesh setup
Copy

Then restart Claude Code completely.

See the full Troubleshooting Guide for more.

Documentation

• Getting Started — First-time setup walkthrough
• User Guide — Complete usage guide with real-world examples
• Development Guide — Contributor guide for local development
• API Reference — Auto-generated API documentation
• Commands Reference — All commands and tools
• Architecture — How MeMesh works internally

Contributing

Contributions welcome! See CONTRIBUTING.md.

License

AGPL-3.0 — See LICENSE