nowfound

AI · alternatives · 2026

24 alternatives to session-indexer

Semantic search over your own Claude Code session history

Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes.

  1. 1

    Store, review, and share your Claude Code sessions

    Mar 2026 · bench.silverstream.ai · its alternatives →

  2. 2

    I got tired of Claude Code forgetting all my context every time I open a new session: set-up decisions, how I like my margins, decision history. etc. We built a shared memory layer you can drop in as a Claude Code Skill. It’s basically a tiny memory DB with recall that remembers your sessions. Not magic. Not AGI. Just state. Install in Claude Code: /plugin marketplace add https://github.com/mutable-state-inc/ensue-skill /plugin install ensue-memory # restart Claude Code What it does: (1) persists context between sessions (2) semantic & temportal search (not just…

    Dec 2025 · github.com · its alternatives →

  3. 3

    I kept slamming into Claude Code limits mid-session and couldn’t find a quick way to see how close I was getting, so I hacked together a tiny local tracker. Streams your prompt + completion usage in real time Predicts whether you’ll hit the cap before the session ends Runs 100 % locally (no auth, no server) Presets for Pro, Max × 5, Max × 20 — tweak a JSON if your plan’s different GitHub: https://github.com/Maciek-roboblog/Claude-Code-Usage-Monitor It’s already spared me a few “why did my run just stop?” moments, but it’s still rough around the edges. Feedback, bug…

    2025 · github.com · its alternatives →

  4. 4
    Claudebin▲258

    Hi HN, We use Claude Code a lot, and after a long session there isn't a simple way to share exactly what happened with someone else. Prompts, responses, file edits, and tool calls all stay inside the terminal. We built Claudebin to make that easier. It's a plugin that lets you export the current session as a URL containing: - the full message thread - file reads and writes - bash commands - web and MCP calls You can send the link to someone, attach it to a PR, embed part of it, or resume the session locally. It's open source. GitHub:…

    Feb 2026 · claudebin.com · its alternatives →

  5. 5

    Did you know Claude Code deletes your session data after 30 days? I found out the hard way when I tried to check my spending history. My session files hit 3GB (2000+ files) and existing tools took 40+ seconds. Rewrote it in Rust with simd-json + rayon. - First run: ~1s (vs 40s+) - Daily use: ~0.04s (1000x faster, cached) - TUI dashboard with daily/weekly/monthly breakdown - Supports Claude Code, Codex CLI, Gemini CLI - Persistent cache — history survives even after CLI deletes files GitHub: https://github.com/mag123c/toktrack Feedback welcome!

    Feb 2026 · github.com · its alternatives →

  6. 6

    Ask Claude Code where your usage went. Token audit, limit diagnosis and usage forensics — built from the session logs already on your machine, nothing leaves it. - kelviq/tare

    Aug 2026 · github.com · its alternatives →

  7. 7

    *Claude Code History Viewer – A macOS Desktop App for Reviewing Claude Code History at a Glance* Hello everyone, I have a habit of reviewing my coding history when working with AI. It's important to trace back and understand "how did I get to this result?" Recently, while using Claude Code, I found it quite inconvenient to check the history in separate terminal tabs or editor windows. So I built a desktop app called *Claude Code History Viewer* using *Tauri + React + Rust*. ## Key Features & Highlights * *Claude Code Conversation History Visualization* When you install Claude Code,…

    2025 · github.com · its alternatives →

  8. 8

    I built a tool that stores your full Claude Code history to let you easily find and resume sessions. It has TUI, CLI and MCP interfaces. It's a single Go binary, and the session history is synced to SQLite each time you use it. Default mode is the TUI with a session browser and full-text search. Once a session is selected you can browse and search within it, resume it or export to markdown. The MCP server provides tools to let Claude search back through the session for pre-compact context or pull from prior sessions. I use this constantly. I've seen elaborate continuity systems to give…

    Jan 2026 · github.com · its alternatives →

  9. 9

    Built this after realizing I was spending ~$1400/week on Claude Code with almost no visibility into what was actually consuming tokens. Tools like ccusage give a cost breakdown per model and per day, but I wanted to understand usage at the task level. CodeBurn reads the JSONL session transcripts that Claude Code stores locally (~/.claude/projects/) and classifies each turn into 13 categories based on tool usage patterns (no LLM calls involved). One surprising result: about 56% of my spend was on conversation turns with no tool usage. Actual coding (edits/writes) was…

    Apr 2026 · github.com · its alternatives →

  10. 10

    I got tired of sharing AI demos with terminal screenshots or screen recordings. Claude Code already stores full session transcripts locally as JSONL files. Those logs contain everything: prompts, tool calls, thinking blocks, and timestamps. I built a small CLI tool that converts those logs into an interactive HTML replay. You can step through the session, jump through the timeline, expand tool calls, and inspect the full conversation. The output is a single self-contained HTML file — no dependencies. You can email it, host it anywhere, embed it in a blog post, and it works on mobile. Repo:…

    Mar 2026 · github.com · its alternatives →

  11. 11RG

    Hey HN! I'm José, and I built Recall to solve a problem that was driving me crazy. The Problem: I use Claude for coding daily, but every conversation starts from scratch. I'd explain my architecture, coding standards, past decisions... then hit the context limit and lose everything. Next session? Start over. The Solution: Recall is an MCP (Model Context Protocol) server that gives Claude persistent memory using Redis + semantic search. Think of it as long-term memory that survives context limits and session restarts. How it works: - Claude stores important context as "memories" during…

    2025 · npmjs.com · its alternatives →

  12. 12

    We built rudel.ai after realizing we had no visibility into our own Claude Code sessions. We were using it daily but had no idea which sessions were efficient, why some got abandoned, or whether we were actually improving over time. So we built an analytics layer for it. After connecting our own sessions, we ended up with a dataset of 1,573 real Claude Code sessions, 15M+ tokens, 270K+ interactions. Some things we found that surprised us: - Skills were only being used in 4% of our sessions - 26% of sessions are abandoned, most within the first 60 seconds - Session success rate varies…

    Mar 2026 · github.com · its alternatives →

  13. 13

    Never lose a vibe coding session. Archive, replay, search.

    Jan 2026 · yolog.dev · its alternatives →

  14. 14

    Persistent memory for AI coding agents

    Apr 2026 · contextpool.io · its alternatives →

  15. 15

    I've been building a tool that changes how LLM coding agents explore codebases, and I wanted to share it along with some early observations. Typically claude code globs directories, greps for patterns, and reads files with minimal guidance. It works in kind of the same way you'd learn to navigate a city by walking every street. You'll eventually build a mental map, but claude never does - at least not any that persists across different contexts. The Recursive Language Models paper from Zhang, Kraska, and Khattab at MIT CSAIL introduced a cleaner framing. Instead of cramming everything into…

    Feb 2026 · github.com · its alternatives →

  16. 16

    Hi HN, I built this because I got tired of the Claude Code CLI hiding details from me. Recent updates have replaced critical output with summaries like "Read 3 files" or "Edited 2 files". To see what actually happened, I was forced to use `--verbose`, which floods the terminal with unreadable JSON and system prompts. I wanted a middle ground: *Full observability without the noise.* `claude-devtools` is a local Electron app that tails the session logs in `~/.claude/` to reconstruct the execution trace in real-time. *Unlike wrappers, it solves the visibility gap in your native…

    Feb 2026 · github.com · its alternatives →

  17. 17
    Rudel▲94

    Claude Code & Codex session analytics for dev teams

    Apr 2026 · rudel.ai · its alternatives →

  18. 18

    Claude Code deleted my research and plan markdown files and informed me: “I accidentally rm -rf'd real directories in my Obsidian vault through a symlink it didn't realize was there: I made a mistake. “ Unfortunately the backup of my documentation accidentally hadn’t run for a month. So I built claude-file-recovery, a CLI-tool and TUI that is able to extract your files from your ~/.claude session history and thankfully I was able to recover my files. It's able to extract any file that Claude Code ever read, edited or wrote. I hope you will never need it, but you can find it on my GitHub…

    Feb 2026 · github.com · its alternatives →

  19. 19

    Hey HN! I built Retain as the evolution of claude-reflect (github.com/BayramAnnakov/claude-reflect). The original problem: I use Claude Code/Codex daily for coding, plus claude.ai and ChatGPT occasionally. Every conversation contains decisions, corrections, and patterns I forget existed weeks later. I kept re-explaining the same preferences. claude-reflect was a CLI tool that extracted learnings from Claude Code sessions. Retain takes this further with a native macOS app that: - Aggregates conversations from Claude Code, claude.ai, ChatGPT, and Codex CLI - Instant full-text…

    Jan 2026 · github.com · its alternatives →

  20. 20CM

    We built CodeYam Memory because Claude Code kept making the same mistakes on our codebase. Our claude.md files quickly got stale and maintaining by hand or with Claude wasn’t sufficient. While digging into this we found that Claude has a native rules system that allowed us to target specific parts of our repo with path matching. This was ideal for our use case but trying to manage these rules by hand was already not working and would be even harder with more granular, targeted rules. CodeYam Memory uses a background agent to review your coding session transcripts, identifies confusion…

    Mar 2026 · its alternatives →

  21. 21

    This is a project I recently worked on at Definitive. We’re hoping to make it easier to semantically query (changing) source code files. We’d love to see people use it as a building block. If you have any suggestions please leave a comment or open a GitHub issue!

    2023 · github.com · its alternatives →

  22. 22

    Hi HN, I'm Rob. Contextify indexes every Claude Code and Codex session on your machine into one local, searchable database. The current session, in either tool, can search all of it: /total-recall in Claude Code, $total-recall in Codex. Demo: https://www.youtube.com/watch?v=FvrvRGp4C9M | Mac app: https://contextify.sh (App Store or DMG) | Linux: CLI with a one-line installer, same search. No signup. I split my work between Claude Code and Codex. When I burn through rate limits on one, I switch to the other, and new models keep leapfrogging each other, so the…

    Jul 2026 · contextify.sh · its alternatives →

  23. 23

    Note: Use code SHOWHNFREE to get it for free. This is a scratch my own itch kind of app. The best way to get the most out of Claude Code is to learn from past sessions. Review past sessions, see where it worked, where it went wrong and what we could have done differently. However, the sessions are saved across multiple json files with cross references, and are hard to read. In a live session, many steps are hidden by default and cannot be easily accessed later. And the mindset when grappling with Claude Code in a session is not exactly ripe to later remembering the details of what went well…

    Jan 2026 · rcanand.gumroad.com · its alternatives →

  24. 24

    I built an MCP server that gives Claude Code long-term memory across sessions, backed by infrastructure you control. Every Claude Code session starts from zero, no memory of previous sessions. This server uses mem0ai as a library and exposes 11 MCP tools for storing, searching, and managing memories. Qdrant handles vector storage, Ollama runs embeddings locally (bge-m3), and Neo4j optionally builds a knowledge graph. Some engineering details HN might find interesting: - Zero-config auth: auto-reads Claude Code's OAT token from ~/.claude/.credentials.json, detects token type (OAT vs…

    Feb 2026 · github.com · its alternatives →

Also compare

Ranked by how close each launch is in meaning, then by votes. Prices were read from each product’s own site when checked and can change. Refine with your own description →