Locus
Local persistent memory for AI coding tools. Built on MCP. Optimized for Codex CLI.

接入你的智能体
從發布者安裝。不是 PlugMCP 端點。
遠端 URL 還是本機指令? 兩種安裝方式的差異
Quick links: Install · Why Locus · Competitive Snapshot · Full comparison
AI coding agents forget project context between sessions. Locus gives them a local memory database they can query through MCP:
Locus is local-first. It stores data on your machine, uses SQLite, and does not require a cloud account, hosted database, embeddings provider, or LLM call to write memory.
npx -y locus-memory@latest install codex --yes
Restart Codex, then verify:
npx -y locus-memory@latest doctor codex
Remove the Codex MCP entry while keeping local memory data:
npx -y locus-memory@latest uninstall codex --yes
The installer adds the Locus MCP server, installs the Codex skill, sets practical redacted capture defaults, and pins the recurring MCP runtime to the installed package version.
New in v3.7 / Track D: Codex memory reliability. memory_recall, memory_search, and memory_timeline are scoped to the current project, date-aware recall reports searched buckets, memory_calendar gives day/week/month activity discovery, and memory_project_state summarizes current package/git/memory state before the agent relies on old context.
Track C richer recall is still carried forward: memory_recall can summarize imported redacted Codex sessions, durable decisions, explicit memory_remember entries, rejected alternatives, validation facts, user style, and dated questions such as "what did we do yesterday?". If several matches are plausible, Locus returns candidateGroups so the agent can ask a focused clarification instead of guessing.
Codex CLI is the primary validated path. Codex Desktop uses the same MCP model where exposed by the upstream surface, and the Track D marker acceptance validates the desktop MCP path when LOCUS_CODEX_SURFACE=desktop is set. Extension parity still depends on target-surface testing.
Locus is not trying to be a full agent runtime or cloud memory platform. It is a small local memory layer for coding agents, with Codex as the first-class product path.
Full comparison: docs/comparison.md
Recommended Codex settings:
LOCUS_CODEX_CAPTURE=redacted
LOCUS_CAPTURE_LEVEL=redacted
For product claims: full is maximum recall and must be treated as explicit opt-in, not a safe default.
Locus exposes 17 MCP tools:
For broad period questions, use memory_calendar first. It defaults to last_30d, so agents should pass this_month, last_month, or an explicit range for user period questions. Date-scoped memory_recall reports searched date buckets, and current-project recall must not mix other project memories unless the user asks for global recall.
Locus is an MCP server, so it can run in Claude Code, Cursor, Windsurf, Cline, Zed, Claude Desktop, and similar clients.
Current maturity:
Manual MCP fallback:
codex mcp add locus -- node /path/to/locus/dist/server.js
git clone https://github.com/Magnifico4625/locus.git
cd locus
npm install
npm run check
npm run build
MIT — see LICENSE.
Persistent project-aware memory for AI coding tools. Built on MCP. Works with Codex, Claude Code, and other MCP-compatible clients.
工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
這筆記錄未列出必要的環境變數。
Locus 透過 stdio 在本機執行。
上次檢查時間:2026-10-28。 Persistent project-aware memory for AI coding tools. Built on MCP. Works with Codex, Claude Code, and other MCP-compatible clients.