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

@momomemory/pi-momo

v0.1.3

Published

Pi plugin that gives agents persistent memory using Momo

Readme

@momomemory/pi-momo

Persistent memory for Pi coding agent using Momo.

Features

  • Auto-recall: Automatically injects relevant memories and user profile before each agent turn
  • Auto-capture: Automatically stores conversation turns as episode memories
  • Manual tools: momo_search, momo_store, momo_forget, momo_profile
  • Slash commands: /remember, /recall, /momo-profile, /momo-debug
  • Flexible config: Supports JSONC config files at global and project level, plus environment variables

Installation

pi install npm:@momomemory/pi-momo

Or add to your ~/.pi/settings.json:

{
  "packages": ["npm:@momomemory/pi-momo"]
}

Configuration

Config is loaded with the following precedence (highest to lowest):

  1. Environment variables (MOMO_PI_* or MOMO_*)
  2. Project config (.momo.jsonc or momo.jsonc in current directory)
  3. Global oh-my-pi config (~/.omp/momo.jsonc)
  4. Global Pi config (~/.pi/momo.jsonc)
  5. Defaults

Config Files

Create ~/.pi/momo.jsonc for global config:

{
  "baseUrl": "http://localhost:7638",
  "apiKey": "your-api-key",
  "containerTag": "pi_global",
  "autoRecall": true,
  "autoCapture": true,
  "maxRecallResults": 10,
  "profileFrequency": 50,
  "debug": false
}

Or create .momo.jsonc in your project directory:

{
  // Project-specific Momo config
  "baseUrl": "http://localhost:7638",
  "apiKey": "project-api-key",
  "containerTag": "pi_myproject"
}

Environment Variables

| Variable | Default | Description | |----------|---------|-------------| | MOMO_PI_BASE_URL / MOMO_BASE_URL | http://localhost:3000 | Momo server URL | | MOMO_PI_API_KEY / MOMO_API_KEY | - | Optional API key | | MOMO_PI_CONTAINER_TAG / MOMO_CONTAINER_TAG | pi_{hostname} | Memory namespace | | MOMO_PI_AUTO_RECALL / MOMO_AUTO_RECALL | true | Inject memories before agent turns | | MOMO_PI_AUTO_CAPTURE / MOMO_AUTO_CAPTURE | true | Store conversation turns | | MOMO_PI_MAX_RECALL_RESULTS / MOMO_MAX_RECALL_RESULTS | 10 | Max memories per injection (1-20) | | MOMO_PI_PROFILE_FREQUENCY / MOMO_PROFILE_FREQUENCY | 50 | Inject full profile every N turns (1-500) | | MOMO_PI_DEBUG / MOMO_DEBUG | false | Enable verbose logging |

Note: MOMO_PI_* variables take precedence over MOMO_* variables.

Config Options

| Option | Type | Default | Description | |--------|------|---------|-------------| | baseUrl | string | http://localhost:3000 | Momo server URL | | apiKey | string | - | Optional API key for authentication | | containerTag | string | pi_{hostname} | Memory namespace for isolation | | autoRecall | boolean | true | Inject memories before agent turns | | autoCapture | boolean | true | Store conversation turns as memories | | maxRecallResults | number | 10 | Max memories per injection (1-20) | | profileFrequency | number | 50 | Inject full profile every N turns (1-500) | | debug | boolean | false | Enable verbose logging |

Tools

momo_search

Search memories by query:

Search for information about my project preferences

momo_store

Store an explicit memory:

Remember that I prefer TypeScript over JavaScript

momo_forget

Delete a memory by ID or query:

Forget the memory about X

momo_profile

View your memory profile:

Show me my profile

Commands

/remember

/remember I prefer dark mode in all editors

/recall

/recall project preferences

/momo-profile

/momo-profile

/momo-debug

Shows effective configuration plus per-field source (env/project/global/default), with API key redacted.

/momo-debug

How It Works

Auto-Recall

Before each agent turn, the plugin:

  1. Fetches your profile (static facts + recent signals)
  2. Searches for memories relevant to the current prompt
  3. Injects a <momo-context> block with:
    • Long-term profile facts
    • Recent signals
    • Relevant memory matches with similarity scores

The full profile is injected every profileFrequency turns; on other turns, only relevant search results are injected.

Auto-Capture

After each successful agent turn, the plugin:

  1. Collects the user/assistant message pair
  2. Strips previously injected context blocks
  3. Ingests the conversation as an episode memory

Requirements

  • Pi 0.50.0+
  • Momo server running and accessible

License

MIT