| ▲ | neomantra a day ago | |
The second bubble there is a tool for 3D visualization and analytics of Claude Code sessions. The sample conversation is the one that made the tool itself! That was a fun toy I learned a lot from. I’m not expanding that but am working intensely on the first bubble: thinkt a CLI/TUI/Webapp for exploring your LLM conversations. Makes it easy to see all your local projects, view them, and export them. It has an embedded OpenAPI server and MCP server. So you can open Kimi and say “use thinkt mcp to look at my last Claude session in this project, look at the thinking at the end and report on the issues we were facing”. I added Claude Teams support by launching a Team and having that team look at its own traces and the changing ~/.Claude folder. Similar for Gemini CLI and Copilot (which still need work). Doing it in the open. Only 2 weeks old - usable, but early. I’m only posting as it’s what I’m working on. Still working on polish and deeper review (it is vibe-crafted). There’s ergonomic issues with ports and DuckDB. Coming up next is VSCode extension and an exporter/collecter for remote agents. | ||
| ▲ | smithclay 4 hours ago | parent [-] | |
The Claude Code analytics space is really interesting to me right now as well, this is cool. I'm coming at it from more of the data infrastructure side (e.g. send all of your logs and metrics to a cheap Iceberg catalog in the cloud so you have a central place to query[1]) but also check out https://github.com/tobilg/ai-observer -- duckdb popping up everything to make this interesting and easy. | ||