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

mindbook

v0.2.5

Published

Auto-generate narrative work journal entries from Claude Code sessions

Downloads

402

Readme

mindbook

Auto-generate narrative work journal entries from Claude Code sessions.

Every time you work with Claude Code, mindbook quietly watches your sessions and distills the work into human-readable prose — what you were trying to do, what decisions you made, what obstacles you hit.

Install

npm install -g mindbook
mindbook setup
mindbook daemon start

Usage

| Command | Description | |---------|-------------| | mindbook setup | First-time setup (auto-detects Claude Code token) | | mindbook daemon start | Start background watcher (auto-triggers on session inactivity) | | mindbook trigger --cwd <path> | Manually generate a journal entry for a project |

How it works

  1. mindbook daemon polls ~/.claude/sessions/ every 30 seconds
  2. When a session file hasn't changed for 3 minutes, it reads the session context and calls Claude to generate a narrative paragraph
  3. The entry is written to ~/.mindbook/<project-name>.md — one file per project, chronological

Journal format

# my-project

## 2026-06-04 · 2026-06-04-my-project

I was working on building out the architecture for mindbook. The core question 
was how to handle the "3-minute inactivity" trigger reliably...

Token detection

Looks for API token in this order:

  1. ~/.claude/settings.jsonenv.ANTHROPIC_AUTH_TOKEN (Claude Code users: zero config)
  2. ANTHROPIC_API_KEY environment variable
  3. ~/.mindbook/config.json (saved by mindbook setup)

Triggers

  • Automatic: 3 minutes after session goes idle (requires daemon)
  • Pre-/new: Before starting a new Claude Code session
  • Pre-/compact: Before compacting context
  • Manual: mindbook trigger --cwd .