Alternatives
Products that do what PRISM does
Session intelligence for Claude Code
- 1
- 2
Store, review, and share your Claude Code sessions
Mar 2026 · bench.silverstream.ai
- 3CF
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
- 4
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
10d ago · github.com
- 5
See where Claude Code burns tokens. Hit your limits less.
May 2026 · latitude.so
- 6
Diet Claude▲423Diet Claude — a usage meter for Claude that drains as you go and refills when your session resets. Crack open the can — free on the Chrome Web Store.
13d ago · dietclaude.com
- 7
- 8IU
I think LLMs are overused to summarise and underused to help us read deeper. I built a system for Claude Code to browse 100 non-fiction books and find interesting connections between them. I started out with a pipeline in stages, chaining together LLM calls to build up a context of the library. I was mainly getting back the insight that I was baking into the prompts, and the results weren't particularly surprising. On a whim, I gave CC access to my debug CLI tools and found that it wiped the floor with that approach. It gave actually interesting results and required very little orchestration…
Jan 2026 · trails.pieterma.es
- 9CC
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
- 10CA
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
- 11SC
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
- 12
- 13
- 14
- 15
See what your Claude Code sessions actually cost
Jul 2026 · langwatch.ai
- 16RC
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
- 17CC
Hello everyone. Claudraband wraps a Claude Code TUI in a controlled terminal to enable extended workflows. It uses tmux for visible controlled sessions or xterm.js for headless sessions (a little slower), but everything is mediated by an actual Claude Code TUI. One example of a workflow I use now is having my current Claude Code interrogate older sessions for certain decisions it made: https://github.com/halfwhey/claudraband?tab=readme-ov-file#s... This project provides: - Resumable non-interactive workflows. Essentially `claude -p` with session support: `cband continue…
Apr 2026 · github.com
- 18
- 19CR
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
- 20
- 21FO
2025 · github.com
- 22
- 23
- 24IB
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
Ranked by how close each launch is in meaning, then by votes. Refine with a description →