> The interface is an interactive terminal UI built with Ink (React for terminals)
Just like Claude Code btw.
I'm working on a custom harness because I don't like or trust some of the ones out there, so I'm going to build one purely for myself and my own needs to see just how they work, and figure out some of what you've learned by looking at how Claude works, so I might add your project to my list of tooling to look at.
you are right. thats cursor-agent (the CLI), not the Cursor IDE. CodeBurn only parses the IDE's state.vscdb right now. cursor agent keeps transcripts under ~/.cursor/projects/*/agent-transcripts/ which we dont read yet.
Made something similar a while back: https://www.clauderank.com/ Completely open source
> The interface is an interactive terminal UI built with Ink (React for terminals)
Just like Claude Code btw.
I'm working on a custom harness because I don't like or trust some of the ones out there, so I'm going to build one purely for myself and my own needs to see just how they work, and figure out some of what you've learned by looking at how Claude works, so I might add your project to my list of tooling to look at.
yeah Ink, it was the fastest path to something that felt native next to Claude Code itself
Very cool! I saw a similar product recently that I liked but I much prefer your approach to theirs[1]
[1] https://github.com/cordwainersmith/Claudoscope
"Built this after realizing I was spending ~$1400/week on Claude Code with almost no visibility into what was actually consuming tokens."
holy slop. the $200/month plan has NEVER hit rate limits for me and I often run 5+ tabs of concurrent agents in a large 300k LoC codebase
Doesn't seem to work with Cursor Agent (which may store its data in ~/.cursor).
you are right. thats cursor-agent (the CLI), not the Cursor IDE. CodeBurn only parses the IDE's state.vscdb right now. cursor agent keeps transcripts under ~/.cursor/projects/*/agent-transcripts/ which we dont read yet.
filed an issue to add it: https://github.com/AgentSeal/codeburn/issues/55
cursor support only landed yesterday, so CLI is next. thanks for catching it.
Cursor Agent itself suggests that this probably won't be easy as some of the data is missing.