AI · alternatives · 2026
24 alternatives to CCDash
Monitor and schedule your Claude Code sessions visually
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 2 we have checked on their own sites, 2 of them free or with a free tier.
- 1
A new way to delegate coding tasks right from your browser
2025 · claude.com · its alternatives →
- 2
Store, review, and share your Claude Code sessions
Mar 2026 · bench.silverstream.ai · its alternatives →
- 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
Schedule recurring tasks locally and in the cloud easily
Mar 2026 · claude.ai · its alternatives →
- 5
Codync▲80Monitor Claude Code sessions in real-time, from anywhere
Mar 2026 · codync.dev · its alternatives →
- 6
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 →
- 7
runCLAUDErun▲112I built runCLAUDErun because I got tired of manually running the same Claude Code tasks every day. It's free and it runs locally. What it does: It's a macOS app that schedules your local Claude Code to run on any schedule you want - daily, weekly, or custom cron expressions. My use case: Every night at 11pm, it automatically summarizes my Obsidian daily notes. But, it can schedule any Claude task - code reviews, data processing, report generation, web research, file organization, etc... Technical details: - Native macOS app (Electron + React) - Uses launchd for scheduling (proper macOS…
2025 · runclauderun.com · its alternatives →
- 8
See exactly how much you spend on Claude, across every tool
Mar 2026 · github.com · its alternatives →
- 9
Let Claude use your computer from the CLI
Mar 2026 · code.claude.com · its alternatives →
- 10
Glance ▲87Real browser for Claude Code Test, Screenshot, Automate
Mar 2026 · glance.debugbase.io · its alternatives →
- 11
claude-devtools▲144See everything Claude Code hides from your terminal
Feb 2026 · claude-dev.tools · its alternatives →
- 12
- 13
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 →
- 14
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 · its alternatives →
- 15
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 →
- 16
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 →
- 17
Claudy▲163A proper home for Claude Code — multi-session, multi-account
May 2026 · claudy.markg.app · its alternatives →
- 18
AgentManager▲125Never miss a Claude Code session waiting for your input
Jul 2026 · agentmgr.app · its alternatives →
- 19
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 →
- 20
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 →
- 21
*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 →
- 22
This project (Agents Observe) started as an exploration into building automation harnesses around claude code. I needed a way to see exactly what teams of agents were doing in realtime and to filter and search their output. A few interesting learnings from building and using this: - Claude code hooks are blocking - performance degrades rapidly if you have a lot of plugins that use hooks - Hooks provide a lot more useful info than OTEL data - Claude's jsonl files provide the full picture - Lifecycle management of MCP processes started by plugins is a bit kludgy at best The biggest takeaway is…
Apr 2026 · github.com · its alternatives →
- 23
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 →
- 24
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 →
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 →