Memory Store Plugin for Claude Code

Give Claude persistent memory. Stop re-explaining your codebase every session. Claude remembers corrections, patterns, and decisions—learning from mistakes instead of repeating them.

A comprehensive Claude Code plugin that automatically tracks your development flow, captures session context, analyzes git commits, and maintains team knowledge across projects.

Quick Start (60 Seconds)

Three Simple Steps:

# 1. Add marketplace
claude plugin marketplace add julep-ai/memory-store-plugin

# 2. Install plugin
claude plugin install memory-store

# 3. Add Memory Store MCP server
claude mcp add memory-store -t http https://beta.memory.store/mcp

That's it! OAuth authentication will open in your browser. Authenticate once and you're done.

Start Using:

cd your-project
claude

Memory tracking works automatically!

Check your session:

cat .claude-session
# Shows: Session ID, start time, files tracked, commits tracked

Note: Memory Store retrieval requires OAuth 2.1 authentication. See Authentication Setup below.

What Gets Tracked Automatically

Once installed, the plugin automatically tracks (no manual commands needed):

📊 Every Session

✅ Session start: Project state, git branch, file count
✅ Session end: Duration, files changed, commits made, quality score
✅ Context loading: Previous session learnings loaded automatically

📝 Every File Change

✅ Write/Edit operations: File path, language, patterns detected (API, UI, Service, etc.)
✅ Change count: Tracked per session
✅ Automatic checkpoints: Every 10 file changes

🔄 Every Git Commit

✅ Commit analysis: Message, files changed, patterns
✅ Ownership tracking: Who commits where
✅ Pre-commit validation: Security checks, secret detection

🎯 Every Error/Correction

✅ Error detection: Automatic capture when you say "wrong", "error", "failed"
✅ High-priority learning: Stored as corrections with is_resolution: true
✅ Session quality tracking: Reduces quality score for feedback

📋 Context Compaction

✅ Before compression: Saves important context automatically
✅ Preserves decisions: Key reasoning and patterns retained

Zero Configuration - Just Ask Questions!

The plugin automatically:

✅ Tracks your work in the background
✅ Searches memory when you ask questions
✅ Loads context at session start
✅ Preserves debugging state

Just use Claude Code normally:

You: "Add authentication to the API"
Claude: [Creates auth.ts]

Behind the scenes:

✅ Hook fires (PreToolUse on Write)
✅ track-changes.sh extracts file info
✅ Item written to .memory-queue.jsonl
✅ memory-queue-processor skill reads queue
✅ Claude calls mcp__memory-store__record
✅ Data stored: "Created src/api/auth.ts - API authentication pattern"
✅ User sees: "💾 Saved to Memory Store: File created..."

You see: Normal Claude Code workflow + brief confirmation Plugin does: All tracking automatically via queue!

Features

🎯 Automatic Session Tracking

Session-level context: Every development session is tracked with complete context
File change monitoring: Real-time tracking of Write/Edit operations
Background processing: Hooks run asynchronously without interrupting workflow
Smart storage: Only relevant context is captured and stored

📊 Git Intelligence

Commit analysis: Automatic analysis of commit patterns, types, and impact
Branching strategy: Tracks and documents team branching workflows
Historical context: Preserves the "why" behind code changes
Breaking change detection: Automatically flags significant changes

📝 CLAUDE.md Synchronization

Anchor comment tracking: Monitors and syncs anchor comments across files
Cross-team consistency: Ensures all team members have latest documentation
Pattern documentation: Captures and shares coding patterns
Convention enforcement: Helps maintain consistent standards

🤖 Intelligent Context Retrieval

Manual context queries: Use /memory-context to retrieve relevant past work
Pattern awareness: Query established patterns with /memory-overview
Decision history: Access reasoning behind past technical choices
Team knowledge: Shared context available across team members

🔧 Custom Slash Commands

/memory-status - View current tracking status and statistics
/memory-overview - Generate comprehensive project overview
/memory-recall [query] - Retrieve relevant context (usually automatic)

Note: You rarely need /memory-recall - Claude automatically searches memory when you ask questions!

Installation

Quick Install via Marketplace (Recommended)

Step 1: Install Plugin

claude plugin marketplace add julep-ai/memory-store-plugin
claude plugin install memory-store@claude-plugin

Step 2: Configure MCP Server

claude mcp add memory-store https://beta.memory.store/mcp

OAuth will open in your browser. Authenticate once and it works everywhere!

Alternative Installation Methods

From Local Repository

# Clone and install plugin
git clone https://github.com/julep-ai/memory-store-plugin.git
claude plugin marketplace add ./memory-store-plugin
claude plugin install memory-store@claude-plugin

# Configure MCP server (required!)
claude mcp add memory-store https://beta.memory.store/mcp

From Git URL

# Install plugin from Git
claude plugin marketplace add https://github.com/julep-ai/memory-store-plugin.git
claude plugin install memory-store@claude-plugin

# Configure MCP server (required!)
claude mcp add memory-store https://beta.memory.store/mcp

Team Installation

For team-wide deployment, add to your project's .claude/settings.json:

{
  "extraKnownMarketplaces": {
    "julep-plugins": {
      "source": {
        "source": "github",
        "repo": "julep-ai/memory-store-plugin"
      }
    }
  },
  "enabledPlugins": [
    "memory-store"
  ]
}

When team members trust the repository, the plugin is automatically installed!

Verify Installation

# Start Claude Code
cd your-project
claude

# You should see at session start:
# ✅ Memory Store MCP: Connected
# OR
# ⚠️  Memory Store MCP: Not configured
#    📝 To enable memory storage, run:
#       claude mcp add memory-store -t http https://beta.memory.store/mcp

# Check plugin loaded
/plugin
# Should show: ✔ memory-store · Installed

# Check MCP connected (manual verification)
/mcp
# Should show: ✓ memory-store - Connected

# Check tracking active
/memory-store:memory-status
# Should show: Session tracking information

✅ If all checks pass and session start shows "✅ Memory Store MCP: Connected", automatic tracking is working!

Usage

Automatic Tracking

The plugin works automatically in the background:

Session Start: Captures project state when you start Claude Code
File Changes: Tracks every file you create or modify
Git Commits: Analyzes commits you make during the session
Session End: Summarizes and stores session learnings

You don't need to do anything - it just works!

Essential Commands

Command	What It Does
`/memory-status`	Show tracking status
`/memory-overview`	Generate project overview
`/memory-recall [query]`	Get relevant context (usually automatic)

Example Workflow

Morning - Start Work

cd your-project
claude

Plugin initializes and loads yesterday's context

During Development

Add authentication to the API

Plugin tracks all your changes automatically

Making Commits

git commit -m "feat: add OAuth2 authentication"

Plugin analyzes and stores commit context

End Session

<Ctrl+D to exit>

Plugin summarizes and stores session learnings

Next Day

When you or a teammate starts Claude Code, all that context is available!

Intelligent Context Retrieval

Claude automatically uses stored context:

Example 1: Following Patterns

You: "I need to add a new API endpoint"

Claude: "I'll help you create that endpoint. Based on our established
patterns (see src/api/auth.ts:45), I'll follow the same authentication
and error handling conventions..."

Example 2: Decision History

You: "Should we use MongoDB or PostgreSQL?"

Claude: "Looking at our memory store, the team decided to use PostgreSQL
3 months ago for ACID compliance and complex relationships. Unless this
feature has different requirements, I'd recommend staying consistent..."

Working with CLAUDE.md Files

The plugin automatically syncs your CLAUDE.md files and anchor comments:

<!-- AUTH-FLOW -->
## Authentication Flow

Our authentication uses OAuth2 with JWT tokens...

When you reference anchor comments in code or documentation, the plugin maintains these relationships in memory.

How It Works

Architecture (v1.2.3+: Queue-Based)

Claude Code Session
       ↓
   Plugin Hooks (SessionStart, PreToolUse, SessionEnd, etc.)
       ↓
┌──────────────────────────────────────┐
│  Hook Scripts write to:              │
│  .memory-queue.jsonl                 │
│  (Producer Pattern)                  │
└──────────────────────────────────────┘
       ↓
┌──────────────────────────────────────┐
│  memory-queue-processor Skill        │
│  (Consumer Pattern - Automatic)      │
│  • Reads queue every message         │
│  • Processes all items               │
│  • Invokes MCP tools                 │
│  • Reports to user                   │
│  • Clears queue                      │
└──────────────────────────────────────┘
       ↓
┌──────────────────────────────────────┐
│  Memory MCP Server                   │
│  (mcp__memory-store__record)         │
└──────────────────────────────────────┘
       ↓
┌──────────────────────────────────────┐
│  Memory Store (Cloud/Local)          │
│  (beta.memory.store)                 │
└──────────────────────────────────────┘

Why Queue-Based?

Hook additionalContext is not visible to Claude in conversation
File-based communication bypasses this limitation
Reliable, testable, works on all platforms (macOS, Linux)
Producer-consumer pattern is proven distributed systems architecture

Hook Execution Flow

SessionStart Hook (scripts/session-start.sh)
- Initializes session tracking
- Writes session start to .memory-queue.jsonl
- Generates session ID and metadata
- Captures project snapshot
PreToolUse Hooks (scripts/track-changes.sh)
- Fires before Write/Edit operations
- Writes file changes to .memory-queue.jsonl
- Detects patterns (API, Service, UI, etc.)
- Smart filtering (skips node_modules, build/, etc.)
SessionEnd Hook (scripts/session-end.sh)
- Writes session summary to .memory-queue.jsonl
- Calculates duration, quality metrics
- Cleans up temporary tracking files
memory-queue-processor Skill (Automatic)
- Activates on every user message
- Reads .memory-queue.jsonl
- Invokes mcp__memory-store__record for each item
- Reports to user: "💾 Saved to Memory Store: ..."
- Clears processed items from queue

Memory Storage

The plugin stores:

Development patterns: How features are implemented
Team conventions: Coding standards and practices
Decision history: Why certain approaches were chosen
Business logic: Core workflows and rules
Git context: Commit patterns and branching strategies
Documentation: CLAUDE.md files and anchor comments

Team Collaboration

Local Development

Each developer runs the plugin locally:

Personal context is captured
Stored to shared memory store
Available to all team members

Knowledge Sharing

The plugin enables powerful knowledge sharing:

New developers can query past decisions
Code reviews reference established patterns
Architecture discussions are preserved
Business logic is documented automatically

Cross-Project Context

If your team works on multiple related projects:

Install the plugin in each project
Authenticate once with the same memory store account
All projects share the same memory context automatically

Best Practices

✅ Do This

Use conventional commit messages: feat:, fix:, docs:, etc.
Keep CLAUDE.md files updated: Document patterns as you establish them
Trust the automatic tracking: The plugin captures everything in the background
Use /memory-overview periodically: Get a comprehensive project snapshot

❌ Avoid This

Don't disable the hooks - they provide automatic tracking
Don't skip commit messages - they're analyzed for patterns
Don't ignore pattern suggestions - they represent team knowledge

Configuration

Extending with Additional MCP Servers

You can add support for Linear, Jam.dev, or other MCP servers:

Copy .mcp-extensions.json.example to .mcp-extensions.json
Add your API keys
Restart Claude Code

Example with Linear integration:

{
  "mcpServers": {
    "memory": { ... },
    "linear": {
      "command": "npx",
      "args": ["@linear/mcp-server"],
      "env": {
        "LINEAR_API_KEY": "your-key-here"
      }
    }
  }
}

The plugin will automatically integrate Linear issues into memory context!

Customizing Hooks

Edit hooks/hooks.json to customize when hooks fire:

{
  "hooks": {
    "PostToolUse": [
      {
        "matcher": "Write|Edit",
        "hooks": [
          {
            "type": "command",
            "command": "${CLAUDE_PLUGIN_ROOT}/scripts/track-changes.sh"
          }
        ]
      }
    ]
  }
}

Troubleshooting

Plugin Not Loading

Common Issue: Duplicate Hooks Reference

If the plugin fails to initialize, check for duplicate hooks loading:

# This should return NOTHING:
grep '"hooks"' .claude-plugin/plugin.json
grep '"hooks"' .claude-plugin/plugin.json.local

If you see "hooks": "./hooks/hooks.json", remove that line. Claude Code automatically discovers hooks/hooks.json by convention - explicit references cause hooks to load twice and break initialization.

Other checks:

# 1. Check plugin structure
ls -la .claude-plugin/

# 2. Verify plugin.json is valid
cat .claude-plugin/plugin.json | jq .

# 3. Check Claude Code debug output
claude --debug

Hooks Not Firing

# 1. Ensure scripts are executable
chmod +x scripts/*.sh

# 2. Check hook configuration
cat hooks/hooks.json | jq .

# 3. Test scripts manually
bash scripts/session-start.sh

Authentication Setup

⚠️ Memory Store retrieval requires OAuth 2.1 authentication

If you get this error:

Error: "No valid session ID provided" (HTTP 400)

What works without auth:

✅ Local session tracking (.claude-session file)
✅ File change tracking (automatic)
✅ Commit tracking (manual via skill)

What requires auth:

❌ Memory retrieval (mcp__memory-store__recall)
❌ /memory-recall command
❌ Automatic context retrieval in responses

To set up authentication:

Visit https://beta.memory.store
Sign in with GitHub/Google
Follow OAuth setup instructions
Restart Claude Code

Check connection after auth:

# Verify MCP server
claude mcp list
# Should show: ✓ memory-store - Connected

# Test recall (requires auth)
claude mcp call memory-store overview --mode basic
# Should return overview, not auth error

Memory Store Connection Issues

Quick Check: Every session start shows MCP status:

✅ "Memory Store MCP: Connected" = Working!
⚠️ "Memory Store MCP: Not configured" = Follow the command shown
ℹ️ "Memory Store MCP: Status unknown" = Claude CLI issue

If you see "Not configured":

# Run the command shown in session start message:
claude mcp add memory-store -t http https://beta.memory.store/mcp

# OAuth will open in browser - authenticate once

If you see "Connected" but storage not working:

# 1. Check MCP server status
claude mcp list

# 2. Re-authenticate if needed
claude mcp remove memory-store
claude mcp add memory-store -t http https://beta.memory.store/mcp

# 3. Restart Claude Code session
# 4. Verify OAuth authentication completed in browser

Plugin Not Found

# 1. Verify marketplace is added
/plugin marketplace list

# 2. Refresh marketplace
/plugin marketplace update claude-plugin

# 3. Try reinstalling
/plugin uninstall memory-store
/plugin install memory-store@claude-plugin

Common Use Cases

New Feature Development

/memory-context authentication patterns

→ Check existing patterns

Implement OAuth2 following established patterns

→ Build with consistency

git commit -m "feat: add OAuth2 support"

→ Pattern stored for team

Onboarding New Developer

/memory-overview

→ Generate comprehensive project overview with architecture, patterns, and decisions

Code Review

/memory-context why did we choose PostgreSQL

→ Get historical decision context

Bug Investigation

/memory-context error handling in API layer

→ See how errors are handled elsewhere

Development

Local Testing

Make changes to plugin files
Restart Claude Code
Test with /memory-status

Adding New Hooks

Create script in scripts/
Make it executable: chmod +x scripts/your-script.sh
Add to hooks/hooks.json
Test the hook

Adding New Commands

Create markdown file in commands/
Add frontmatter with description
Document usage and examples
Restart Claude Code

Support

Issues: GitHub Issues
Discussions: GitHub Discussions
Email: developers@autotelic.inc

Changelog

See CHANGELOG.md for version history.

License

MIT License - see LICENSE file for details.

Credits

Built by the Autotelic team with ❤️ for the Claude Code community.

Special thanks to:

The Claude Code team at Anthropic
The memory.store team
All contributors and users

Name		Name	Last commit message	Last commit date
Latest commit History 69 Commits
.claude-plugin		.claude-plugin
.github		.github
agents		agents
commands		commands
hooks		hooks
scripts		scripts
skills		skills
.claude-project-context		.claude-project-context
.gitignore		.gitignore
.mcp-extensions.json.example		.mcp-extensions.json.example
.mcp.json.example		.mcp.json.example
CHANGELOG.md		CHANGELOG.md
CONTRIBUTING.md		CONTRIBUTING.md
KNOWN_ISSUES.md		KNOWN_ISSUES.md
LICENSE		LICENSE
MARKETPLACE.md		MARKETPLACE.md
QUICKSTART.md		QUICKSTART.md
README.md		README.md
TESTING.md		TESTING.md
USER_GUIDE.md		USER_GUIDE.md

License

julep-ai/memory-store-plugin

Folders and files

Latest commit

History

Repository files navigation

Memory Store Plugin for Claude Code

Quick Start (60 Seconds)

Three Simple Steps:

Start Using:

What Gets Tracked Automatically

📊 Every Session

📝 Every File Change

🔄 Every Git Commit

🎯 Every Error/Correction

📋 Context Compaction

Zero Configuration - Just Ask Questions!

Features

🎯 Automatic Session Tracking

📊 Git Intelligence

📝 CLAUDE.md Synchronization

🤖 Intelligent Context Retrieval

🔧 Custom Slash Commands

Installation

Quick Install via Marketplace (Recommended)

Alternative Installation Methods

From Local Repository

From Git URL

Team Installation

Verify Installation

Usage

Automatic Tracking

Essential Commands

Example Workflow

Intelligent Context Retrieval

Working with CLAUDE.md Files

How It Works

Architecture (v1.2.3+: Queue-Based)

Hook Execution Flow

Memory Storage

Team Collaboration

Local Development

Knowledge Sharing

Cross-Project Context

Best Practices

✅ Do This

❌ Avoid This

Configuration

Extending with Additional MCP Servers

Customizing Hooks

Troubleshooting

Plugin Not Loading

Hooks Not Firing

Authentication Setup

Memory Store Connection Issues

Plugin Not Found

Common Use Cases

New Feature Development

Onboarding New Developer

Code Review

Bug Investigation

Development

Local Testing

Adding New Hooks

Adding New Commands

Support

Changelog

License

Credits

About

Resources

License

Contributing

Uh oh!

Stars

Watchers

Forks

Releases 4

Packages 0

Uh oh!

Packages