github.com
aasixh/devgrep
Terminal-native search for shell history, logs, and markdown notes. Go + Bubble Tea TUI, MIT, v1.0.0. go install github.com/aasixh/devgrep@latest
devgrep: one TUI to search shell history, logs, and notes
devgrep is a one-day-old Go + Bubble Tea TUI (MIT, v1.0.0, 26★) that indexes shell history, .log files, and markdown notes into a local SQLite database and exposes all three through a single fuzzy-search interface — framed honestly as an early radar find with zero community signal and a broken curl installer.
You fixed a gnarly Docker networking issue three weeks ago. The exact
iptables command is somewhere in your shell history — buried under 2,000 newer entries, behind a zsh session boundary, or gone after a history rotation. Your runbook lives in a markdown file you haven't opened since. The relevant log line is in a .log you'd have to grep six directories deep.Ctrl+R doesn't span log files. rg doesn't rank results by when you last used them. You end up grep-ing memory instead of files.devgrep is a one-day-old Go tool that takes a different angle: index shell history,
.log files, and markdown notes into a single local SQLite database, then expose all three through one fuzzy-search TUI 1. As the README puts it 2:"devgrep is a terminal-native search engine for developer workflows."
It is genuinely new — the v1.0.0 release landed on May 22, 2026 3, the repo has 26 stars and zero community discussion anywhere (HN, Reddit, Twitter/X — checked) 1. Read that as: this is an early find, not a vetted pick.
The one working install path
Three install methods are documented. One works reliably. Use this 4:
go install github.com/aasixh/devgrep@latestThe
curl | sh release script is broken — it expects .tar.gz archives but the release assets are bare binaries 5 3. The make build path works if you clone the repo. Neither Homebrew nor any package manager is available yet.The docs say Go 1.21+ is required, but the actual
go.mod declares Go 1.24.5 6 4. If go install fails, check your Go version first.リンクプレビューを読み込んでいます…
A concrete scenario
You're debugging a Kubernetes auth failure you hit two months ago. You know you ran a
kubectl command to rotate a service account token, but you can't remember the exact flags. You also have a notes file from that debugging session.# Build your index first
devgrep index
# Search across everything
devgrep search "kubectl service account"The TUI opens, shows results tagged
[history], [note], and [log] in ranked order — fuzzy-matched and scored by recency, frequency, and how close the working directory was to your current project. You can also hit it from a script without the TUI:devgrep --plain search "kube auth failed" --source history,logsOutput includes the original command, when it last ran, and the working directory it ran from 2.
The ranking weights are configurable (fuzzy: 0.38, recency: 0.26, exact: 0.16, frequency: 0.10, directory relevance: 0.08, command length: 0.02) 7. You can also watch a project directory for live re-indexing:
devgrep index ~/projects/api # index + start watching
devgrep index ~/projects/api --no-watch # index once, no watcherWatch mode uses
fsnotify with a 500 ms debounce; deleted files are removed from the index automatically 7.
doctor output — health check view inside the Bubble Tea TUI 2What the tool doesn't overlap with
The closest tools in this space each cover one source:
| Tool | What it searches | Multi-source index |
|---|---|---|
Ctrl+R / fzf | Shell history only | No |
| atuin (20k+ ★) | Shell history, optional sync | No |
| mcfly | Shell history, neural ranking | No |
| hstr | Shell history | No |
| ripgrep (rg) | File contents (logs, notes, etc.) | No unified index |
| devgrep | Shell history + logs + notes | Yes |
atuin is the production-ready choice for shell history specifically — 20k+ stars, multi-machine sync, a large community, and active development 2. devgrep's bet is that crossing the source boundary (history and logs and notes, ranked together) is worth the tradeoff. Whether that bet pays off at real scale is unknown; no one has reported using it yet 1.
The rough edges
Zero community signal. Every major developer community was checked: Hacker News, r/golang, r/commandline, Twitter/X, Google. Nothing 8. That isn't necessarily a red flag for a tool that launched yesterday, but it means you're the first tester, not the hundredth.
The release description is wrong. The v1.0.0 GitHub Release body says "Fast recursive code search, Extension filtering, Colored terminal output, Multi-language support" 3 — a description that describes a different tool entirely. It reads like a template copy-paste. The actual tool does none of those things; it indexes history, logs, and notes.
The star/fork ratio is unusual. 26 stars and 16 forks on a one-day-old, zero-discussion repo is atypical — new tools usually see a 10:1 star-to-fork ratio or higher 1. The fork accounts haven't been audited.
No functional verification. The Go 1.24.5 toolchain wasn't available in the research environment, so the install and actual TUI behavior are unconfirmed. All feature claims come from the README and documentation site, not from a live test run.
The author has limited community presence. Ashish Ranjan (aasixh) registered on GitHub in May 2023, has 4 public repositories (3 of which are forks with 0 stars), no Twitter/X account, and no HN history 9. That's not a disqualifier — every tool author starts somewhere — but it means there's no track record to lean on.
リンクプレビューを読み込んでいます…
Worth bookmarking, not yet worth depending on
The architecture is coherent: Cobra CLI wiring, a pluggable indexer interface, SQLite in WAL mode, fuzzy ranking with configurable weights, and a Bubble Tea TUI that falls back to plain output for pipes 7. The developer's own contribution guideline reflects the right instincts 2:
"Please keep changes offline-first, terminal-first, and dependency-conscious."
If you have Go 1.24.5+ on your machine and ten minutes, the
go install is worth running to see whether the TUI works as described. The install script is not. Check your Go version before you try, star the repo if the concept interests you, and revisit in a few weeks to see whether the install.sh gets fixed, the release description gets corrected, and any community usage surfaces. A tool this new earns its spot on the radar by surviving the next month, not by having the features today.Cover image: AI-generated illustration
このコンテンツについて、さらに観点や背景を補足しましょう。