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

codex-memory

v1.0.9

Published

Local persistent memory for Codex agents that captures, searches, and reuses project knowledge.

Vulnerabilities

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

Links

Git

Maintainers

adrianosky99adrianosky99

Keywords

codexcodex-memoryai-agentagent-memorypersistent-memorymcpmcp-servercodex-plugindeveloper-toolslocal-firstsqliteclitypescript

Readme

codex-memory

Project-local memory for Codex agents.

codex-memory installs a local memory runtime for a Codex workspace. It stores project knowledge in SQLite, exposes MCP tools, and wires Codex hooks so agents can search, capture, and reuse decisions, fixes, facts, and patterns across sessions.

Quick Start

npx codex-memory install
codex-memory doctor
codex-memory remember --type decision --title "Use SQLite" --context "Local memory storage" --resolution "Keep canonical memory in SQLite."
codex-memory query "SQLite"

On Windows PowerShell, use npx.cmd codex-memory install if npx is not resolved. Run codex-memory doctor after install to confirm the API URL, SQLite path, MCP server, plugin config, hooks, and worker port.

Common Commands

codex-memory status
codex-memory restart
codex-memory debug --query "current task"
codex-memory uninstall

Memory Types

Use fact, decision, bug, solution, and pattern for durable project knowledge:

codex-memory remember --type fact --title "Frontend uses Next.js" --context "Application stack"
codex-memory remember --type bug --title "Windows shell cannot resolve npx" --context "PowerShell install path" --resolution "Run npx.cmd codex-memory install."
codex-memory query "PowerShell npx"

MCP

The installer writes MCP configuration for the packaged server. The server uses CODEX_MEM_API_URL, usually http://127.0.0.1:8000, and exposes memory tools such as query_memory, store_memory, get_memory, update_memory, and delete_memory.

Guides

Data

Memory is local-first and stored under ~/.codex-mem by default. Do not store secrets, tokens, credentials, or private personal data as memory.

Package Publishing

The GitHub repository is a monorepo. The root package.json is private and is used for development, workspaces, and shared scripts.

The npm package users install is published from apps/cli, because that directory contains the codex-memory CLI manifest, built dist files, runtime assets, license, and this README.

cd apps/cli
npm pack --dry-run
npm publish --access public

The dry run should list README.md before publishing.