Alternatives
Products that do what Termi does
Termi watches Claude Code sends a notification when its idle
- 1

See what your Claude Code sessions actually cost
Jul 2026 · langwatch.ai
- 2

- 3CC
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
- 4

- 5

- 6

See exactly how much you spend on Claude, across every tool
Mar 2026 · github.com
- 7SC
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
- 8

- 9

- 10

- 11

- 12

- 13

- 14

- 15

- 16

- 17IB
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
- 18
- 19NC
Hi HN, my name's Clifford and I'm one of the creators of Nori. I’ve been using Claude Code heavily since last summer, and after understanding some of the tradeoffs with their TUI implementation, I knew I couldn't see myself living for years with this interface as one of my daily-driver tools. It is not a hard problem to make monospace text output performant, so why does Claude Code suffer from flicker and strobing in the terminal (https://github.com/anthropics/claude-code/issues/1913)? Even after they've released multiple improvements for this, I still see the…
Jan 2026 · github.com
- 20CC
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
- 21CR
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
- 22

- 23

- 24

See Claude's 2× usage window live in your macOS menu bar
Mar 2026 · double.raphaelduhs.at
Ranked by how close each launch is in meaning, then by votes. Refine with a description →