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

clgrep

v0.0.1

Published

Search through Claude Code conversation history

Readme

clgrep

"Wait, didn't I already solve this with Claude?"

Search your entire Claude Code history instantly. Find that mass prompt, solution, or conversation you know you had somewhere.

npm install -g clgrep

The Problem

You've been using Claude Code for weeks. You know you solved a similar problem before. You know you had a great conversation about webpack configs, or that regex pattern, or that API design. But where?

Your ~/.claude folder has hundreds of conversation files. Good luck finding anything.

The Solution

clgrep "webpack"
═══ Your Prompts ═══

[2024-12-15 14:32]
  dir: /home/user/myproject
  msg: how do I configure webpack to handle SVG imports...

═══ Conversations ═══

───────────────────────────────────────
session: a1b2c3d4-e5f6-7890
    cwd: /home/user/myproject
   file: projects/-home-user-myproject/a1b2c3d4.jsonl

  [2024-12-15 14:32] (user)
    how do I configure webpack to handle SVG imports...
  [2024-12-15 14:32] (assistant)
    You'll need to add a rule to your webpack config...

Found 42 matches

Features

  • Instant search across all your Claude Code conversations
  • Zero dependencies - just Node.js builtins
  • Color-coded output - timestamps, roles, and matches highlighted
  • Full context - see the project directory, session ID, and timestamps
  • Finds both your prompts AND Claude's responses

Install

npm install -g clgrep

Or run directly:

npx clgrep "your search term"

Usage

# Find all conversations about authentication
clgrep "auth"

# Find that regex you wrote
clgrep "regex"

# Find conversations in a specific project
clgrep "myproject"

# Case-insensitive by default
clgrep "React"

How It Works

Claude Code stores your conversation history in ~/.claude/:

  • history.jsonl - Your prompt history
  • projects/*//*.jsonl - Full conversation logs per session

clgrep searches through all of these files and presents results with full context.

Requirements

  • Node.js >= 14
  • Claude Code (obviously)

Why "clgrep"?

cl (Claude) + grep (the OG search tool) = clgrep

License

AGPL-3.0


Pro tip: Alias it in your shell:

alias cg="clgrep"

Then just: cg "that thing I asked about"


Made for developers who talk to Claude more than their coworkers.