Independent by design · no pay-to-rank placements  · How we evaluate tools →
Anclum Submit
V

virling/agentmem

Persistent project memory shared by every AI coding agent: Claude Code, Cursor, Codex, Gemini CLI, Windsurf…

Before you install: no copy-paste command · license NOASSERTION · link reachable

First step: npx -y @virling/agentmem install

View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Client config (built from the install command this repo gives)
{
  "mcpServers": {
    "virling-agentmem": {
      "command": "npx",
      "args": ["-y", "@virling/agentmem"]
    }
  }
}

Parsed from the README we fetched on 2026-10-31; we have not executed it.

command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
  "servers": {
    "virling-agentmem": {
      "command": "npx",
      "args": ["-y", "@virling/agentmem"]
    }
  }
}
Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio virling-agentmem -- npx -y @virling/agentmem
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
Star count
0 ★ · virling/agentmem · read from the GitHub search API · (checked 2026-11-13 20:00:50)
Source
read directly from its GitHub page · type: open-source project
Harvest history
first seen 2026-11-01 · last seen 2026-11-14 · seen 14× · listed by 1 sources
Score
score 103 · 1 sources · repo
Install
npx -y @virling/agentmem
FAQ (answers come from our records)
How do I install it?
The repository provides this install command: npx -y @virling/agentmem. It comes from the repository itself; we cannot guarantee it runs as-is in your client.
Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository virling/agentmem;first catalogued 2026-11-01;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.

# agentmem

以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →

Memory that lives with your code: reviewed in pull requests, enforced as guardrails, readable by every AI coding agent. Zero dependencies, no daemon, no account.
Zero dependencies. Plain Node.js, MCP over stdio, memories stored as Markdown files.
Per project. Memory is keyed by the git remote URL, so every clone of the same repo shares one memory.
Works across agents. Claude Code, Cursor, Windsurf, Codex, Gemini CLI, VS Code (Copilot), OpenCode, or anything with MCP support.
Handoffs. Stop mid-task in one agent, continue in another: the next session starts with what was done and what is next.
Automatic in Claude Code. Hooks inject memory at session start, surface notes when a linked file is opened, and auto-capture new facts when a session ends.
Team memory in git. Team memories live in .agentmem/ in your repo, so they are reviewed in PRs and shared on git pull.
Guardrails. Turn a memory into a rule: agents are blocked or asked before editing matching files.
Code-aware. Memories linked to files are flagged when those files change, so outdated knowledge does not linger.
Export to rule files. Compile team memories into AGENTS.md, CLAUDE.md, Copilot and Cursor rules for agents without MCP.
Contradiction checks. New memories come back with related ones to compare, and agentmem check finds conflicts.
PR memory Action. A GitHub Action turns decisions from merged pull requests into team memories, opened as a PR for review.
Safe by default. Writes that look like secrets are refused. Near-duplicate titles are refused unless forced.
## Contents
How it works
Requirements
Changelog
Install
Connect your agents
MCP tools
CLI
Claude Code hooks
Auto-capture
Team memory
Guardrails
Code-aware staleness
Export to rule files
Contradiction checks
Handoffs between agents
PR memory GitHub Action
Memory format
Configuration
Sharing with a team
Project structure
Troubleshooting
Uninstall
Contributing
License
## How it works
Claude Code ─┐ ┌─► ~/.agentmem/ - /.md local, private
Cursor ──────┼── MCP (stdio) ──► agentmem
Other agent ─┘ └─► /.agentmem/.md team, committed
1. An agent starts agentmem as an MCP server from inside a project folder.
2. agentmem finds the project with git remote get-url origin (falls back to the repo root path, then the current folder) and hashes it into a project id like my-app-1a2b3c4d5e6f.
3. Every memory is one Markdown file, either local (~/.agentmem/ /) or team ( /.agentmem/).
4. Any agent opened in the same repo reads both layers.
## Requirements
Node.js 18 or newer
git (optional, used to identify the project)
Claude Code CLI (optional, only for hooks and auto-capture)
## Changelog
See CHANGELOG.md and GitHub releases.
## Install
One line. Detects Claude Code, Cursor, Windsurf, Gemini CLI, Codex, VS Code and OpenCode on your machine and configures each one:
bash
npx -y @virling/agentmem install
Or install globally first (faster hooks, agentmem on your PATH):
bash
npm i -g @virling/agentmem && agentmem install
Configure only specific agents:
bash
agentmem install claude cursor
Restart your agents afterwards. Running install again is safe: it updates existing entries instead of adding duplicates.
### As a Claude Code plugin
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/virling-agentmem/)
Source
github · https://github.com/virling/agentmem
Browse by field
Open source
added
today

More like this

All 1,671 →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index