11–20 of 108 posts
is there a reason, other than general faith in humanity, to assume those '1573 sessions' are real? I do not see any link or source for the data. I assume it is to remain closed, if it exists.
It might be worthwhile to include some of an example run in your readme. I scrolled through and didn’t see enough to justify installing and running a thing
The gates categorize issues into auto-fix or human-review. Auto-fix gets sent back to the coding agent, it re-reviews, and only the hard stuff makes it to me. That structure took me from about 73% first-pass acceptance to over 90%.
What I've been focused on lately is figuring out which gates actually earn their keep and which ones overlap with each other. The session-level analytics you're building would be useful on top of this, I don't have great visibility into token usage or timing per stage right now.
I wrote up the analysis: https://michael.roth.rocks/research/543-hours/
I also open sourced my log analysis tools: https://github.com/mrothroc/claude-code-log-analyzer
No, thanks
Nice, I've been working on the same problem from a different direction. Instead of analyzing sessions after the fact, I built a pipeline that structures them. Stages (plan, design, code, review, same as you'd have with humans) with gates in between. The gates categorize issues into auto-fix or human-review. Auto-fix gets sent back to the coding agent, it re-reviews, and only the hard stuff makes it to me. That struct…
> That's it. Your Claude Code sessions will now be uploaded automatically. No, thanks
Or you can run your own instance, but we will need to add docs, on how to control the endpoint properly in the CLI.
For those unaware, Claude Code comes with a built in /insights command...
[flagged]