Alternatives
Products that do what ZCCInfo – Fast status line for Claude Code written in Zig does
Startup time is ~10ms with Zig, which is why I built this small CLI tool for Claude Code that shows context usage, git branch, and model info in the status line. The original JavaScript version took ~143ms to start. Reducing this to ~10ms matters since the tool runs frequently during editor use.
- 1CC
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
- 2CC
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
- 3

All status line renderings are captured from live sandbox containers under various scenarios. Anyone can submit a status line, and each one is manually reviewed before approval. Source: https://github.com/NathanAB/statuslin.es Enjoy!
20d ago · statuslin.es
- 4

- 5

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

- 7

- 8

- 9

- 10IB
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
- 11

- 12

- 13

- 14CM
Every MCP tool call dumps raw data into Claude Code's 200K context window. A Playwright snapshot costs 56 KB, 20 GitHub issues cost 59 KB. After 30 minutes, 40% of your context is gone. I built an MCP server that sits between Claude Code and these outputs. It processes them in sandboxes and only returns summaries. 315 KB becomes 5.4 KB. It supports 10 language runtimes, SQLite FTS5 with BM25 ranking for search, and batch execution. Session time before slowdown goes from ~30 min to ~3 hours. MIT licensed, single command install: /plugin marketplace add mksglu/claude-context-mode…
Feb 2026 · github.com
- 15

- 16CCCode Claude Code▲117
In the nature of Open Source, I am releasing something I'm actively working on but is insanely simple and will likely be made anyways. It is an SDK for scripting Claude Code. It's a lightweight (155 lines) and free wrapper around claude code This is a big deal because it seems that using claude code and cursor has become largly repitive. My workflow typically goes like this: Plan out my task into a file, then have claude code implement the plan into my code. I'm actively building a product with this, but still wanted to make it OSS! Use it now with `pip install codesys`
2025 · github.com
- 17CC
Claude Code tends to be just slow enough you have time to tab away and get distracted. This plugin uses Claude Code's hooks to play music when Claude is waiting for user input so you don't just leave it sitting for 15 minutes.
Dec 2025 · github.com
- 18

- 19CA
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
- 20OS
2024 · github.com
- 21CC
I found myself frequently wanting to schedule tasks in Claude Code (both one-time and recurring) so I built a CC plugin to help with that. To install: /plugin marketplace add jshchnz/claude-code-scheduler /plugin install scheduler@claude-code-scheduler Then just tell Claude what you want (some examples): Every Wednesday at 3am find dead code: unused functions, unreachable branches, commented-out code, and unused imports. List by file with line numbers. Schedule a code review every weekday at 9am. Review commits from the last 24 hours, check for bugs, security issues, error…
Jan 2026 · github.com
- 22

- 23PD
Hi everyone, I'm a student from Flanders and I like to use Claude Code for my purposes, ideas and also just for fun and also make solutions for problems in our world!) So that's why I built "Pulse", it's an local application that you can easily install to your device and easily follow what your claude agent is doing right now in your terminal session with an ambiance design and easily give permissions for your agent. For those who wants to see directly how much tokens you spent, and how much the session costs, and approve tool calls from everywhere from your phone and everything runs locally…
Jun 2026 · github.com
- 24

Ranked by how close each launch is in meaning, then by votes. Refine with a description →