PulseAugur
EN
LIVE 02:20:37

Developer builds claude-grep to search Claude Code history

By PulseAugur Editorial · [1 sources] ·

A developer created a tool called claude-grep to improve the searchability of Claude Code conversation history. The tool allows users to perform full-text searches across their stored transcripts, which can be difficult to navigate due to Claude Code's default session title-based resume function. Claude-grep utilizes ripgrep for fast searching and fzf for an interactive user interface, enabling users to quickly find and resume specific past conversations, including those involving sub-agents. AI

IMPACT Enhances developer productivity by improving access to AI assistant conversation history.

RANK_REASON A user-developed tool that enhances an existing product's functionality.

Read on dev.to — Claude Code tag →

AI-generated summary · Google Gemini · from 1 sources. How we write summaries →

Developer builds claude-grep to search Claude Code history

How we ranked this

Signal score
0 / 100
Composite score across the factors below. Higher = stronger signal that this story matters right now.
Newsworthiness bucket
Tool
A user-developed tool that enhances an existing product's functionality.
Source corroboration
Single-source cluster
Only one publisher covered this so far. Single-source stories can still rank when the publisher is high-authority, but they lack cross-source corroboration.
Topics
product, other
Editorial topic classification. Feeds into how the story surfaces on /topic/<slug> hub pages and into the per-entity coverage mix.
AI-industry relevance
High
Clearly on-topic for AI-industry coverage.
Story freshness
109 days old
Aged out of breaking-news scoring windows; ranking reflects the durable signal from the full source set.

Full methodology in our editorial standards.

COVERAGE [1]

  1. dev.to — Claude Code tag TIER_1 English(EN) · coolcorexix ·

    I had 1,063 Claude Code conversations and couldn't find anything — so I built claude-grep

    <p>I use Claude Code a <em>lot</em>. Enough that when I finally counted, I had <strong>1,063 conversations</strong> sitting in <code>~/.claude/projects/</code> — around 256 MB of JSONL transcripts.</p> <p>And I could never find the one I needed.</p> <p>You know the feeling: <em>"…

RELATED ENTITIES

RELATED TOPICS