V
virling/agentmem
Persistent project memory shared by every AI coding agent: Claude Code, Cursor, Codex, Gemini CLI, Windsurf…
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
客户端配置（取自该仓库的安装命令）
{
"mcpServers": {
"virling-agentmem": {
"command": "npx",
"args": ["-y", "@virling/agentmem"]
}
}
}解析自我们于 2026-10-31 抓取的该仓库 README；我们未执行过。
command/args 来自仓库写明的安装命令；不确定时请以该项目 README 为准。
VS Code（.vscode/mcp.json —— 键名是 servers）
{
"servers": {
"virling-agentmem": {
"command": "npx",
"args": ["-y", "@virling/agentmem"]
}
}
}VS Code 顶层键是 <code>servers</code>，其余与上面那份相同。
Claude Code（命令行）
claude mcp add --transport stdio virling-agentmem -- npx -y @virling/agentmem
Claude Code 不收 JSON 文件，用这条命令直接加。
配置项的键名以你的客户端为准：客户端与 CLI
- ★ 数取值
- 0 ★ · virling/agentmem · 取自 GitHub 搜索 API · （2026-11-13 20:00:50 核对）
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型：开源项目
- 收录与活跃
- 收录于 2026-11-01 · 最近见到 2026-11-14 · 共见到 14 次 · 被 1 个来源列出
- 评分构成
- 综合分 103 · 1 个来源 · repo
- 安装
npx -y @virling/agentmem
常见问题（答案都来自我们的记录）
怎么安装？
该仓库给出的安装命令是
npx -y @virling/agentmem。我们的记录里它是仓库自己提供的；不保证在你的客户端上直接可用。它适合谁 / 用来做什么？
我们把它归在这些标签下: 开源项目。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
virling/agentmem；我们收录于 2026-11-01；最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。# 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
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
收录徽章（可选）
想把收录标记放进 README 就复制这行，可选，不影响收录。
[](https://anclum.com/zh/s/virling-agentmem/)
- 来源
- github · https://github.com/virling/agentmem
- 按领域浏览
- 开源项目
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。