In Memoria

Giving AI coding assistants a memory that actually persists.

Quick Demo

Watch In Memoria in action: learning a codebase, providing instant context, and routing features to files.

The Problem: Session Amnesia

You know the drill. You fire up Claude, Copilot, or Cursor to help with your codebase. You explain your architecture. You describe your patterns. You outline your conventions. The AI gets it, helps you out, and everything's great.

Then you close the window.

Next session? Complete amnesia. You're explaining the same architectural decisions again. The same naming conventions. The same "no, we don't use classes here, we use functional composition" for the fifteenth time.

Every AI coding session starts from scratch.

This isn't just annoying, it's inefficient. These tools re-analyze your codebase on every interaction, burning tokens and time. They give generic suggestions that don't match your style. They have no memory of what worked last time, what you rejected, or why.

The Solution: Persistent Intelligence

In Memoria is an MCP server that learns from your actual codebase and remembers across sessions. It builds persistent intelligence about your code (patterns, architecture, conventions, decisions) that AI assistants can query through the Model Context Protocol.

Think of it as giving your AI pair programmer a notepad that doesn't get wiped clean every time you restart the session.

Current version: 0.6.0 - See what's changed

What It Does

• Learns your patterns - Analyzes your code to understand naming conventions, architectural choices, and structural preferences
• Instant project context - Provides tech stack, entry points, and architecture in <200 tokens (no re-analysis needed)
• Smart file routing - Routes vague requests like "add password reset" directly to relevant files
• Semantic search - Finds code by meaning, not just keywords
• Work memory - Tracks current tasks and architectural decisions across sessions
• Pattern prediction - Suggests how you'd solve similar problems based on your history

Example Workflow

# First time: Learn your codebase
npx in-memoria learn ./my-project

# Start the MCP server
npx in-memoria server

# Now in Claude/Copilot:
You: "Add password reset functionality"
AI: *queries In Memoria*
    "Based on your auth patterns in src/auth/login.ts, I'll use your
     established JWT middleware pattern and follow your Result<T>
     error handling convention..."

# Next session (days later):
You: "Where did we put the password reset code?"
AI: *queries In Memoria*
    "In src/auth/password-reset.ts, following the pattern we
     established in our last session..."

No re-explaining. No generic suggestions. Just continuous, context-aware assistance.

Quick Start

Installation

# Install globally
npm install -g in-memoria

# Or use directly with npx
npx in-memoria --help

Connect to Your AI Tool

Claude Desktop - Add to your config (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "in-memoria": {
      "command": "npx",
      "args": ["in-memoria", "server"]
    }
  }
}

Claude Code CLI:

claude mcp add in-memoria -- npx in-memoria server

GitHub Copilot - See Copilot Integration section below

Learn Your Codebase

# Analyze and learn from your project
npx in-memoria learn ./my-project

# Or let AI agents trigger learning automatically
# (Just start the server and let auto_learn_if_needed handle it)
npx in-memoria server

How It Works

In Memoria is built on Rust + TypeScript, using the Model Context Protocol to connect AI tools to persistent codebase intelligence.

Architecture

┌─────────────────────┐    MCP     ┌──────────────────────┐    napi-rs    ┌─────────────────────┐
│  AI Tool (Claude)   │◄──────────►│  TypeScript Server   │◄─────────────►│   Rust Core         │
└─────────────────────┘            └──────────┬───────────┘               │  • AST Parser       │
                                              │                           │  • Pattern Learner  │
                                              │                           │  • Semantic Engine  │
                                              ▼                           │  • Blueprint System │
                                   ┌──────────────────────┐               └─────────────────────┘
                                   │ SQLite (persistent)  │
                                   │ SurrealDB (in-mem)   │
                                   └──────────────────────┘

The Core Components

Rust Layer - Fast, native processing:

• Tree-sitter AST parsing for 12 languages (TypeScript, JavaScript, Python, PHP, Rust, Go, Java, C/C++, C#, Svelte, SQL)
• Blueprint analyzer (detects project structure, entry points, architecture patterns)
• Pattern learner (statistical analysis of your coding style)
• Semantic engine (understands code relationships and concepts)

TypeScript Layer - MCP server and orchestration:

• 13 specialized tools for AI assistants (organized into 4 categories)
• SQLite for structured data, SurrealDB with SurrealKV for persistent vector embeddings
• File watching for incremental updates
• Smart routing that maps features to files

Storage - Local-first:

• Everything stays on your machine
• SQLite for patterns and metadata
• SurrealDB with SurrealKV backend for persistent vector embeddings
• Local transformers.js for embeddings (Xenova/all-MiniLM-L6-v2)

What Makes It Different

This isn't just another RAG system or static rules engine:

• Learns from actual code - Not manually-defined rules, but statistical patterns from your real codebase
• Predicts your approach - Based on how you've solved similar problems before
• Token efficient - Responses optimized to minimize LLM context usage (<200 tokens for project context)
• Routes to files - "Add login" → automatically suggests src/auth/login.ts
• Remembers context - Tracks work sessions, tasks, and architectural decisions
• Multi-mode search - Semantic (meaning), text (keywords), or pattern-based

What's New in v0.5.x

We recently completed Phases 1-4 of the implementation roadmap:

🗺️ Project Blueprints (Phase 1)

Instant project context without full learning. Ask about a codebase and get tech stack, entry points, key directories, and architecture all in under 200 tokens.

💼 Work Context System (Phase 2)

AI agents can now track work sessions, maintain task lists, and record architectural decisions. Resume work exactly where you left off.

🧭 Smart File Routing (Phase 3)

Feature-to-file mapping across 10 categories (auth, API, database, UI, etc.). Vague requests like "add password reset" get routed to specific files automatically.

⚡ Smooth Progress Tracking (v0.5.3)

No more janky console spam. Progress bars update in-place with consistent 500ms refresh rates.

MCP Tools for AI Assistants

In Memoria provides 13 specialized tools that AI assistants can call via MCP. They're organized into 4 categories (down from 16 after Phase 4 consolidation merged redundant tools):

🎯 Core Analysis (2 tools)

• analyze_codebase - Analyze files/directories with concepts, patterns, complexity (Phase 4: now handles both files and directories)
• search_codebase - Multi-mode search (semantic/text/pattern)

🧠 Intelligence (7 tools)

• learn_codebase_intelligence - Deep learning to extract patterns and architecture
• get_project_blueprint - Instant project context with tech stack and entry points ⭐ (Phase 4: includes learning status)
• get_semantic_insights - Query learned concepts and relationships
• get_pattern_recommendations - Get patterns with related files for consistency
• predict_coding_approach - Implementation guidance with file routing ⭐
• get_developer_profile - Access coding style and work context
• contribute_insights - Record architectural decisions

🤖 Automation (1 tool)

• auto_learn_if_needed - Smart auto-learning with staleness detection ⭐ (Phase 4: includes quick setup functionality)

📊 Monitoring (3 tools)

• get_system_status - Health check
• get_intelligence_metrics - Analytics on learned patterns
• get_performance_status - Performance diagnostics

Phase 4 Consolidation: Three tools were merged into existing tools for better AX (agent experience haha):

• get_file_content → merged into analyze_codebase
• get_learning_status → merged into get_project_blueprint
• quick_setup → merged into auto_learn_if_needed

For AI agents: See AGENT.md for complete tool reference with usage patterns and decision trees.

GitHub Copilot Integration

In Memoria works with GitHub Copilot through custom instructions and chat modes.

Setup

This repository includes:

• .github/copilot-instructions.md - Automatic guidance for Copilot
• .github/chatmodes/ - Three specialized chat modes:
  • 🔍 inmemoria-explorer - Intelligent codebase navigation
  • 🚀 inmemoria-feature - Feature implementation with patterns
  • 🔎 inmemoria-review - Code review with consistency checking

GitHub Copilot Integration (VS Code)

In Memoria integrates with GitHub Copilot Chat using MCP + Custom Agents (formerly called Chat Modes). These agents allow Copilot to query In Memoria’s persistent intelligence when working in Agent mode.

⚠️ Important: Copilot will only call MCP tools when the chat is in Agent mode (not Ask or Edit).

Requirements

• VS Code 1.106+
• GitHub Copilot Chat enabled
• In Memoria MCP server configured and running

MCP Server Setup (Required)

Create or edit the following file in your workspace:

.vscode/mcp.json

{
  "servers": {
    "in-memoria": {
      "command": "npx",
      "args": ["in-memoria", "server"]
    }
  }
}

Open this file in VS Code and click Start when prompted, or start it manually.

Copilot Instructions (Automatic)

This repository includes:

• .github/copilot-instructions.md

VS Code automatically loads this file and applies guidance to Copilot Chat. No additional setup is required.

Custom Agents (formerly “Chat Modes”)

This repository provides three Custom Agents for Copilot:

Agent File Location

⚠️ VS Code has renamed Chat Modes → Custom Agents

To ensure compatibility with current VS Code versions:

1. Create the folder:

   Code

   Copy

   .github/agents/
   

2. Move or copy files from:

   Code

   Copy

   .github/chatmodes/
   

   into:

   Code

   Copy

   .github/agents/
   

3. Rename each file:

   Code

   Copy

   *.chatmode.md → *.agent.md
   

Example:

inmemoria-feature.chatmode.md → inmemoria-feature.agent.md

Using Agents in VS Code

1. Open Copilot Chat
2. Select the custom agent (e.g., inmemoria-featurename) directly from the dropdown.

If agents do not appear:

• Reload the window
• Ensure files are in .github/agents/

Example Usage

Where is the authentication logic?

→ Copilot queries In Memoria’s semantic index

Add password reset functionality

→ Copilot retrieves:

• file routing
• architectural patterns
• prior auth decisions

Review this code for consistency

→ Copilot compares against learned conventions

Common Pitfalls

• ❌ Using Ask/Edit mode → MCP tools are ignored
• ❌ MCP server not running
• ❌ Agent files left in .github/chatmodes/ only
• ❌ VS Code version < 1.106

Notes on VS Code Terminology

VS Code still recognizes legacy files, but .github/agents/*.agent.md is the recommended format going forward.

Language Support

Native AST parsing via tree-sitter for:

• TypeScript & JavaScript (including JSX/TSX)
• Python
• PHP
• Rust
• Go
• Java
• C & C++
• C#
• Svelte
• SQL

Build artifacts (node_modules/, dist/, .next/, etc.) are automatically filtered out.

Status: Work in Progress

Let's be honest: In Memoria is early-stage software. It works, but it's not perfect.

What Works Well

• ✅ Pattern learning from real codebases
• ✅ Semantic search across concepts
• ✅ Project blueprint generation
• ✅ MCP integration with Claude Desktop/Code
• ✅ Cross-platform support (Linux, macOS, Windows)
• ✅ Token-efficient responses

Known Limitations

• ⚠️ Large codebases (100k+ files) can be slow on first analysis
• ⚠️ Pattern accuracy improves with codebase consistency
• ⚠️ Some languages have better tree-sitter support than others
• ⚠️ Documentation could be more comprehensive

We Need Your Help

This is open-source infrastructure for AI-assisted development. Currently a solo project by @pi22by7, but contributions are not just welcome, they're essential.

Before contributing code, please:

• Check the GitHub Projects board to see what's planned
• Join Discord to discuss your ideas (@pi_22by7)
• Open an issue to discuss the feature/fix
• Email me at talk@pi22by7.me for larger contributions

Ways to contribute:

• 🐛 Report bugs - Found something broken? Open an issue
• 💡 Suggest features - Have ideas? Discuss on Discord or GitHub Discussions
• 🔧 Submit PRs - Code contributions are always appreciated (discuss first!)
• 📖 Improve docs - Help make this easier to understand
• 🧪 Test on your codebase - Try it out and tell us what breaks
• 💬 Join the community - Discord for real-time discussions

See CONTRIBUTING.md for development setup and guidelines.

Technical Comparison

vs GitHub Copilot's memory:

• Copilot: Basic fact storage, no pattern learning
• In Memoria: Semantic analysis + pattern learning + architectural intelligence + work context

vs Cursor's rules:

• Cursor: Static rules, manually defined
• In Memoria: Dynamic learning from actual code + smart file routing + project blueprints

vs Custom RAG:

• RAG: Retrieves relevant code snippets
• In Memoria: Understands patterns + predicts approaches + routes to files + tracks work context

Team Usage

In Memoria works for both individual developers and teams:

Individual:

• Learns your personal coding style
• Remembers architectural decisions you've made
• Provides context-aware suggestions

Team:

• Share .in-memoria.db files to distribute learned patterns
• Onboard new developers with pre-learned codebase intelligence
• Ensure consistent AI suggestions across the team

Build from Source

git clone https://github.com/pi22by7/in-memoria
cd in-memoria
npm install
npm run build

Requirements:

• Node.js 18+
• Rust 1.70+ (for building from source)
• 2GB RAM minimum

Development:

npm run dev          # Start in development mode
npm test            # Run test suite (98.3% pass rate)
npm run build:rust  # Build Rust components

Quality metrics:

• 118/120 unit tests passing (98.3%)
• 23/23 MCP integration tests passing (100%)
• Zero clippy warnings in Rust code
• Zero memory leaks verified

FAQ

Q: Does this replace my AI coding assistant? A: No, it enhances them. In Memoria provides the memory and context that tools like Claude, Copilot, and Cursor can use to give better suggestions.

Q: What data is collected? A: Everything stays local. No telemetry, no phone-home. Your code never leaves your machine. All embeddings are generated locally using transformers.js models.

Q: How accurate is pattern learning? A: It improves with codebase size and consistency. Projects with established patterns see better results than small or inconsistent codebases. The system learns from frequency and repetition.

Q: What's the performance impact? A: Minimal. Initial learning takes time (proportional to codebase size), but subsequent queries are fast. File watching enables incremental updates. Smart filtering skips build artifacts automatically.

Q: What if analysis fails or produces weird results? A: Open an issue with details. Built-in timeouts and circuit breakers handle most edge cases, but real-world codebases are messy and we need your feedback to improve.

Q: Can I use this in production? A: You can, but remember this is v0.5.x. Expect rough edges. Test thoroughly. Report issues. We're working toward stability but aren't there yet.

Q: Why Rust + TypeScript? A: Rust for performance-critical AST parsing and pattern analysis. TypeScript for MCP server and orchestration. Best of both worlds: fast core, flexible integration layer.

Q: What about other AI tools (not Claude/Copilot)? A: Any tool supporting MCP can use In Memoria. We've tested with Claude Desktop, Claude Code, and GitHub Copilot. Others should work but may need configuration.

Roadmap

We're following a phased approach:

• ✅ Phase 1: Project Blueprint System (v0.5.0)
• ✅ Phase 2: Work Context & Session Memory (v0.5.0)
• ✅ Phase 3: Smart File Routing (v0.5.0)
• ✅ Phase 4: Tool Consolidation (v0.5.0)
• 🚧 Phase 5: Enhanced Vector Search & Embeddings
• 📋 Phase 6: Multi-project Intelligence
• 📋 Phase 7: Collaboration Features

See GitHub Projects for detailed tracking.

Community & Support

Project maintained by: @pi22by7

• 💬 Discord: discord.gg/6mGsM4qkYm - Join the community, ask questions, discuss improvements (ping @pi_22by7)
• 📧 Email: talk@pi22by7.me - For private inquiries or larger contribution discussions
• 🐛 Issues: GitHub Issues - Report bugs and request features
• 💡 Discussions: GitHub Discussions - General discussions and Q&A
• 📖 Documentation: See AGENT.md for AI agent instructions
• 🤝 Contributing: Check CONTRIBUTING.md for development guidelines

Before contributing: Please discuss your ideas on Discord, via email, or in an issue before starting work on significant features. This helps ensure alignment with project direction and avoids duplicate efforts.

License

MIT - see LICENSE

Built with ❤️ by @pi22by7 for the AI-assisted development community.

Try it: npx in-memoria server

Latest release: v0.6.0 - Smooth progress tracking and Phase 1-4 complete

In memoria: in memory. Because your AI assistant should remember.

Questions? Ideas? Join us on Discord or reach out at talk@pi22by7.me