It runs inside the Claude Code process. The side panel is only what the author's README names. Read the repo before you install, or run claude plugin validate on the plugin folder.
Version
3.2.0
License
MIT
Repo stars
5
Last change
2026-10-16
What it can reach
Draws in the session
Reaches the network or an outside service
Calls another program on this machine
vector-memory-mcp is a local-first memory server. Embeddings are generated on this machine with all-MiniLM-L6-v2, and memories stay in ~/.vector-memory/memories.db. The plugin runs that server with bunx, and Bun 1.0 or newer is required. The README says the first install of the server downloads the ML models, about 90 MB. As of 3.1.0 the plugin lives in the aeriondyseti-plugins marketplace. Before compaction, /clear, and /exit, you are asked first. Compaction can save a waypoint instead of compacting, save memories and then compact, compact as usual, or cancel. Cancel applies only to /compact. An auto-compaction cannot be cancelled, and Esc there saves a waypoint and compacts. At session start, and after /clear, a saved waypoint asks whether to load. Dismissing that question loads it. The draft comes from one prompt-cached fork of the conversation. /waypoint:set and /waypoint:get save and restore a waypoint. The server table defaults the HTTP port to 3271 and leaves HTTP enabled. --no-http turns that transport off.
The install name is vector-memory. This page adds the author's name. The marketplace name is aeriondyseti-plugins. The marketplace is a separate repository, AerionDyseti/aeriondyseti-plugins, whose vector-memory entry points at this folder, pinned to v3.2.0. The ask before compaction, /clear, and /exit is why this page files it under workflow. Cancel stops a slash command, not a tool call, so this page does not list a hold. supermemory gives Claude memory across sessions through Supermemory, with a recall strip above the prompt that shows what it found for your prompt. cognee-memory draws a memory status row above the prompt, with a dataset picker, and recalls saved context each turn. This one asks before the context is cleared and keeps the memories on this machine. It does not draw a recall strip. The draft is a model call on the login Claude Code already holds, so this page does not list that call as network access. The network access is the model download and the package fetch from npm. Memories are not sent. The plugin's server config also passes --enable-history, so history indexing is on for this install. The CLI table leaves it off. fileMemorySync defaults to on in the plugin settings: a memory file Claude writes is also stored as a vector memory. compactCheckpoint, exitCheckpoint, and loadCheckpoint default to ask.
Demo
Screenshot of the author's GitHub page.
What it hooks into
session.compactWhen the context is compacted
classic.SessionStartA Claude Code event
command.runWhen you run its slash command/clear/exit
tool.callAround a tool call, where it can hold oneWriteEditBash
Read from the on() calls in its hook modules. Open its source under Files to check what each one does.