Persistent memory for Claude Code. Remember decisions, recall past context, and maintain institutional knowledge across sessions.

# Add the marketplace
/plugin marketplace add rawcontext/engram-claude-plugin

# Install the plugin
/plugin install engram@rawcontext-engram

The plugin includes the Engram MCP server - no additional configuration needed. On first use, you'll be prompted to authenticate via OAuth.

Start a session by loading relevant memories and context.

/engram:prime implementing user authentication
/engram:prime refactoring the API layer
/engram:prime

Search memories using semantic similarity.

/engram:recall authentication decisions
/engram:recall code style --type=preference
/engram:recall debugging tips --type=insight

Types: decision, preference, insight, fact

Store information for future sessions.

/engram:remember We chose PostgreSQL for its JSON support
/engram:remember Always run tests before pushing --type=preference
/engram:remember The timeout was caused by connection pooling

Find reasoning behind past decisions.

/engram:why did we choose React?
/engram:why use tabs over spaces?
/engram:why NATS instead of Kafka?

Engram stores memories in a bitemporal graph database with vector embeddings for semantic search. All memories are tagged with time metadata for temporal queries.

Memory Types:

• decision: Architectural choices with rationale
• preference: User conventions and patterns
• insight: Debugging discoveries and learnings
• fact: Objective information about the codebase

This plugin includes hooks that automatically capture Claude Code events and forward them to the Engram ingestion service. This provides:

• Session tracking: SessionStart/SessionEnd events for session lifecycle
• Tool usage: PostToolUse events capture every tool invocation
• Completion tracking: Stop events mark agent completion

Set the ingestion URL via environment variable:

# Local development (default)
export ENGRAM_INGESTION_URL="http://localhost:6175"

# Cloud deployment
export ENGRAM_INGESTION_URL="https://api.engram.rawcontext.com"

For authenticated cloud deployments, the plugin reads OAuth tokens from ~/.engram/auth.json (populated by the MCP server's device flow authentication).

The hooks run asynchronously in the background and never block Claude Code.

MIT