npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

locus-memory

v3.6.1

Published

Persistent project-aware memory for AI coding tools. Built on MCP. Knows your project, remembers your decisions, costs almost nothing.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

magnidarkmagnidark

Keywords

claude-codepluginmemorymcpai-agent

Readme

Locus

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

Locus hero image

npm version Node.js License: MIT MCP Compare

Quick links: Install · Why Locus · Competitive Snapshot · Full comparison

What Locus Does

AI coding agents forget project context between sessions. Locus gives them a local memory database they can query through MCP:

  • project structure: files, exports, imports
  • saved decisions: architecture choices, preferences, constraints
  • Codex conversation recall: recent work, errors, rejected alternatives, next steps
  • diagnostics: what is stored, what was imported, what capture mode is active

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.

Install For Codex

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.6

New in v3.6 / Track C: richer Codex recall. 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 / extension uses the same MCP model where exposed by the upstream surface, but parity is still treated as unverified until tested there.

Why Choose Locus

| Need | Locus approach | | --- | --- | | One-command Codex setup | npx -y locus-memory@latest install codex --yes | | Local-only storage | SQLite under $CODEX_HOME/memory/, ~/.claude/memory/, or ~/.locus/memory/ | | Low token cost | Writes happen locally; tokens are spent only when the agent recalls memory | | Privacy control | metadata, redacted, and full capture modes; full is explicit warning territory | | Project-aware memory | Structural scan plus durable decisions and conversation events | | Inspectability | memory_status, memory_doctor, memory_audit, memory_review | | Cross-client base | Any MCP client can use the server; Codex and Claude Code have the strongest adapters today |

Competitive Snapshot

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.

| Project | Main strength | Trade-off vs Locus | | --- | --- | --- | | agentmemory | Very broad coding-agent memory stack with many tools, hooks, viewer, and benchmark claims | Larger system surface; Locus is smaller, simpler, Codex-first, and ships as one npm MCP runtime | | AIDE Memory | Path-scoped local memory and very small context nudge | Locus focuses more on MCP tools, Codex JSONL import, diagnostics, and explicit recall UX | | Mem0 | Popular general-purpose memory layer for AI agents with SDKs, hosted/self-hosted options, and benchmarks | Usually an application integration layer; Locus is ready-to-use for coding tools through MCP | | Letta | Full stateful agent platform with advanced memory | More framework/runtime commitment; Locus plugs into existing tools instead of replacing them | | Zep / Graphiti | Temporal knowledge graphs and production context infrastructure | Strong for app/enterprise memory; Locus is lighter and local by default for individual coding workflows |

Full comparison: docs/comparison.md

Capture Modes

| Mode | Use it when | What to expect | | --- | --- | --- | | metadata | You want safest diagnostics-first behavior | Minimal content recall | | redacted | You want practical Codex memory | Bounded snippets and keyword extraction with best-effort secret redaction | | full | You explicitly want maximum recall | More content stored locally after redaction; not risk-free |

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.

MCP Tools

Locus exposes 14 MCP tools:

| Tool | Purpose | | --- | --- | | memory_recall | Summary-first recall for questions about past work | | memory_search | Full-text search across structure, decisions, and conversation events | | memory_remember | Save important decisions or preferences | | memory_review | Inspect durable memories, states, evidence, and topic keys | | memory_import_codex | Manually import Codex rollout JSONL sessions | | memory_timeline | Chronological event feed | | memory_scan | Index project structure | | memory_explore | Browse indexed project structure | | memory_status | Runtime state and Codex diagnostics | | memory_doctor | Actionable health checks | | memory_audit | Storage and privacy audit | | memory_config | Show effective configuration | | memory_compact | Prune old episodic entries | | memory_forget / memory_purge | Delete selected or all memory with safety confirmation |

Other Clients

Locus is an MCP server, so it can run in Claude Code, Cursor, Windsurf, Cline, Zed, Claude Desktop, and similar clients.

Current maturity:

| Surface | Status | | --- | --- | | Codex CLI | Primary validated path | | Claude Code | Supported through hooks and shared runtime | | Codex desktop / extension | Same config model where MCP is exposed; parity still unverified | | Cursor / Windsurf / Cline / Zed | MCP tools work; passive conversation adapters are future work |

Manual MCP fallback:

codex mcp add locus -- node /path/to/locus/dist/server.js

Docs

Development

git clone https://github.com/Magnifico4625/locus.git
cd locus
npm install

npm run check
npm run build

License

MIT — see LICENSE.