Show HN: I built a tool to un-dumb Claude Code's CLI output (Local Log Viewer)

Based on their Terms of Service, we are not allowed to use a Claude Code subscription outside of Claude Code itself. Although it may work with tools like pi or other harnesses, doing so puts your account at risk of being banned.

Claude Code is not developer friendly.

OpenCode works nicely, I wish it web mode would be developed more. Currently, as it stands, you have to work on the same host in order to pass the full OAuth login flow (it redirects to localhost) for subscription based providers (Claude, ChatGPT). I wish it used some BASE_URL variable I could set, so it would be used instead.

I think you're not supposed to use your claude max plans etc with external harnesses. In theory your account could get banned.

Nothing can compare for me with $200 Max CC subscription

Are there any good benchmarks comparing CC with openCode and Pi ?

i had the exact same problem as op , CC showed razzmatazing , analyzing and other B.S i was bit irked. then i tried pi agent after @mitsuhiko suggested it on YT , X and this issue went away. now pi tells me or shows me the entire action that the model takes. i would still want the actions to be summarized or the harness explain me a concept that i missed (evident from my context) - but thats probably too far fetched.

True. They actually do support basic OTel now, but it's mostly limited to high-level metrics like token usage and session counts. Until then, parsing the local files seem to be pretty much the only way to get real observability.

To clarify on what the others mentioned: `/usage` and `/status` in the CLI do give you basic session token counts.

But regarding khoury's original point about the actual "gas in the tank" (billing/account balance)—no, my tool doesn't show that either.

Since `claude-devtools` strictly parses your local `~/.claude/` logs and makes zero network calls, it doesn't have access to your Anthropic account to pull your actual dollar balance.

What it does provide is high-resolution context usage. Instead of just a total session count, it breaks down tokens per-turn (e.g., how many tokens were eaten by reading a specific file vs. the tool output). It helps you manage your context window locally, but for billing, you're unfortunately still stuck checking the web dashboard.

Why not just /usage?

/status?

Yeah, debugging swallowed command outputs is definitely a pain.

Thanks for giving it a spin tonight! Let me know if you run into any issues.

Fair point. The root directory can be seen noisy right now. There are two main reasons for that:

1. Cross-platform distribution: Shipping an Electron app across macOS (ARM/Intel), Linux (AppImage/deb/rpm), Windows, and maintaining a standalone Docker/Node server just requires a lot of platform-specific build configs and overrides (especially for electron-builder).

2. Agentic coding guardrails: As I built most of this project using Claude Code itself, I wanted strict boundaries when it writes code

The ESLint, Prettier, strict TS, Knip (dead code detection), and Vitest configs act as quality gates. They are what keep the AI's output from drifting into unmaintainable spaghetti code. Without those strict constraints, agentic coding falls apart fast.

I'd rather have 20 config files enforcing quality than a clean root directory with an AI running wild. That said, I totally take your point—I should probably consolidate some of these into package.json to clean things up.

This is some next level nitpicking. It's like criticizing XCode or Idea config of someone, instead of their product (or more popularly whether their website hijacks the back button). But at least in this case the dev config is checked in and reproducible.

I actually had the exact same worry when I started building this.

But it turns out Claude Code's official VS Code extension is built to read these exact same local `.jsonl` files. So unless Anthropic decides to intentionally break their own first-party extension, it should remain relatively stable.

Of course, they will add new payload types (like the recent "Teams" update), but when that happens, it's pretty trivial to just add a new parser handler for it—which I've already been doing as they update the CLI.

So far, it's been surprisingly easy to maintain!

Yeah this is a risk, the jsonl format is not a documented api surface.

I have a similar project that started out as just a log viewer but is now a full session manager etc (https://github.com/kzahel/yepanywhere). My approach was to occasionally run zod schema validations against all my local sessions to make sure the frontend has a pretty faithful schema. I've noticed sometimes when I run claude cli it modifies some jsonl files, it might be doing some kind of cleanup or migration, I haven't looked too deeply into it (yepanywhere detects when files change so I see those sessions as "unread, externally tracked")

The problem with `--verbose` is that it floods the terminal, making real-time debugging a headache.

Also, this isn't a wrapper—it’s a passive viewer. I built it specifically to keep the native terminal workflow intact.

It’s especially useful when you're running multiple parallel sessions. Have you ever tried digging through raw JSON logs to retroactively debug passed sessions at once, since the session is already shut down? It’s nearly impossible without a proper UI. This tool is for those "post-mortem" moments, not just for watching a single stream.

I don't sit there watching every session either—that's definitely not the point.

It's more like standard observability. You don't watch your server logs all day, but when an error spikes, you need deep tracing to find out why.

I use this when the agent gets stuck on a simple task or the context window fills up way faster than expected. The tool lets me "drill down" into the tool outputs and execution tree to see exactly where the bad loop started.

If you're running multiple parallel sessions across different terminal tabs, trying to grep through raw logs to find a specific failure is a massive productivity sink. This is for when things go sideways and you need to solve it in seconds, not for babysitting every keystroke.

Depends on the work you're doing. Cookie cutter / derivative work like I do for some hobby projects? Sure, it can near full auto it. More abstract or cutting edge stuff like in academic research enviornments? It needs correction at just about every step. Your workflow sounds like it deals with the former, which is fine, but that isn't everyone.

Nobody said every keystroke. That’s not like for like.