Engram Plugins — AI skill for Claude Code

Weaviate Engram Plugins

Persistent, cross-session memory for **Claude Code**, backed by [Weaviate Engram](https://docs.weaviate.io/engram). Claude remembers your preferences, decisions, and project context across sessions — and recalls what's relevant before it answers.

• Recall — before each answer, relevant memories are fetched and added to the conversation.
• Store — after each turn, the exchange is saved so it can be recalled later.

Memory is best-effort: it never blocks or breaks a session. When something needs your attention (bad key, misconfigured scope), Claude surfaces a short `Engram · …` note at the top of its reply.

Install

Get your API key by creating a project on https://console.weaviate.cloud/engram. Then set your API key — in your shell, or a shell profile like `~/.zshenv` so it persists:

export ENGRAM_API_KEY=...

Inside Claude Code CLI session do:

/plugin marketplace add weaviate/engram-plugins
/plugin install engram@weaviate-engram

That's it. Memory starts working on your next prompt.

Identity

When Engram project uses `user_id` to isolate memories, it ties it to:

• Defaults to your git config user.email.
• Override it with ENGRAM_USER_ID if you want a different identity.

Configuration (optional)

If you have customized your Engram project (custom topics and property scopes), you may need or want to customize how scopes are resolved.

• Global — ~/.engram/config.json: your defaults, everywhere. Full flexibility, including the dynamic sources below.
• Per-directory — .engram.json in a project: committed, shared with your team. Literals and from tokens only — no cmd (see below).

Full custom configuration example

Global `~/.engram/config.json`:

{
  "properties": {
    "codebase": { "from": "git-repo" },
    "chat": { "from": "session_id" }
  },
  "search": {
    "properties": ["codebase"],
    "topics": [
      "tooling_preferences",
      "product_summary",