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

opencode-notes

v0.1.0

Published

Per-session notes for OpenCode V2 with a /notes TUI editor and sidebar preview. Stored as plain Markdown and never injected into model context.

Readme

opencode-notes

npm license

Per-session notes for OpenCode V2, in the terminal.

Notes are plain Markdown, stored outside your repo, and never injected into model context — the agent cannot see them unless you paste them in. That is the point: a scratch space that costs zero tokens.

Why

Sessions end, context gets compacted, and the thing you meant to do next disappears with them. opencode-notes gives every session one private note that survives restarts and lives in the sidebar where you actually see it.

It is deliberately not a memory plugin: nothing is added to prompts, nothing is sent anywhere, no embeddings, no database. One Markdown file per session.

Install

opencode plugin add opencode-notes

Or add it to ~/.config/opencode/opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "plugins": ["opencode-notes"]
}

To pin a commit or branch instead of the published release:

opencode plugin add 'github:mmhlego/opencode-notes#main'

Requires OpenCode V2. The plugin is TUI-only; the server part is an intentional no-op.

Usage

| Action | Key | | --- | --- | | /notes | open the editor for the current session | | /notes <text> | append a line without opening the editor | | Esc | save and close | | <leader>e | edit in $VISUAL / $EDITOR | | Enter | insert a newline |

The session sidebar shows a collapsible Notes section with a read-only preview (first 20 lines). When it is collapsed and the session has no note, the header reads No notes yet. Select text normally in the terminal to copy it.

Storage

~/.local/share/opencode/notes/<sessionID>.md

Set OPENCODE_DATA_DIR to change the base data directory, or pass a dataDir option:

{
  "plugins": [{ "package": "opencode-notes", "options": { "dataDir": "/path/to/data" } }]
}

One file per session. Delete a file to delete that session's notes; back up the directory to keep them. Nothing is written into your project or your git repo.

Development

bun install
bun run typecheck

Load the local checkout by pointing plugins at the directory:

{
  "plugins": ["/absolute/path/to/opencode-notes"]
}

License

MIT