AI · alternatives · 2026
24 alternatives to Bench for Claude Code
Store, review, and share your Claude Code sessions
Bench for Claude Code is a storage and review tool that automatically captures Claude Code sessions, allowing developers to examine what changes were made and understand tool calls in detail. Users can share complete… Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes. Prices are shown for the 1 we have checked on their own sites, 1 of them free or with a free tier.
- 1
Claudebin▲258Hi 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 →
- 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
A new way to delegate coding tasks right from your browser
2025 · claude.com · its alternatives →
- 4
Let Claude use your computer from the CLI
Mar 2026 · code.claude.com · its alternatives →
- 5
See where Claude Code burns tokens. Hit your limits less.
May 2026 · latitude.so · its alternatives →
- 6
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 →
- 7
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 →
- 8
Sipcode▲148Keep Claude Code's context clean for sharper answers
Jun 2026 · anuj7411.github.io · its alternatives →
- 9
Continuous Claude is a CLI wrapper I made that runs Claude Code in an iterative loop with persistent context, automatically driving a PR-based workflow. Each iteration creates a branch, applies a focused code change, generates a commit, opens a PR via GitHub's CLI, waits for required checks and reviews, merges if green, and records state into a shared notes file. This avoids the typical stateless one-shot pattern of current coding agents and enables multi-step changes without losing intermediate reasoning, test failures, or partial progress. The tool is useful for tasks that require many…
Nov 2025 · github.com · its alternatives →
- 10
2025 · github.com · its alternatives →
- 11
Claude Code auto-fix ▲359Auto-fix PRs in the cloud while you stay hands-off
Mar 2026 · code.claude.com · its alternatives →
- 12
claude-devtools▲144See everything Claude Code hides from your terminal
Feb 2026 · claude-dev.tools · its alternatives →
- 13
Stop wasting tokens and re-explaining your project every session. Recall gives Claude Code durable memory — entirely offline. - raiyanyahya/recall
Jun 2026 · github.com · its alternatives →
- 14
Use any model inside Claude Code, keep your Claude plan
Mar 2026 · edgee.ai · its alternatives →
- 15RG
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 →
- 16
Never lose your work again
2025 · claude-checkpoints.com · its alternatives →
- 17
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 →
- 18
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 →
- 19
Claudy▲163A proper home for Claude Code — multi-session, multi-account
May 2026 · claudy.markg.app · its alternatives →
- 20
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 →
- 21
- 22
*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 →
- 23
A Claude Code status line showing how big your session has got and what the next turn costs before you type - Field-Logic-Ltd/ClaudeStatsBar
Sep 2026 · github.com · its alternatives →
- 24
We needed something like --dangerously-skip-permissions that doesn’t nuke your untracked files, exfiltrate your keys, or install malware. Claude Code's permission system is allow-or-deny per tool, but that doesn’t really scale. Deleting some files is fine sometimes. And git checkout is sometimes not fine. Even when you curate permissions, 200 IQ Opus can find a way around it. Maintaining a deny list is a fool's errand. nah is a PreToolUse hook that classifies every tool call by what it actually does, using a deterministic classifier that runs in milliseconds. It maps commands to action types…
Mar 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 →