As a regular vibe coder, I came to really like claude-devtools for the level of observability it gives into tool calls, context allocation, and token consumption. But, I'm also a visual learner and the dialogue-style flow was not cutting it for me, especially when it came to system design. So, I went and built Centrality which combines some of my favorite features of claude-devtools with my own needs for codebase visualization.
It shows you:
- A graph of your codebase and which files have been touched
- Detailed views of tool calls
- Context window summarization
- API cost broken down per message and per session
- Where the session took place in your git log
You can also use it to:
- Resume existing Claude Code sessions (macOS and Windows)
- Open focused files directly in your IDE
- Connect to remote Claude Code sessions and codebases via SSH
It's for anyone who vibe codes but still wants some insight into what's happening under the hood, and you need to see something to really understand it. I enjoy using Centrality as a companion tool for my own projects, and I hope you do, too!
It shows you: - A graph of your codebase and which files have been touched - Detailed views of tool calls - Context window summarization - API cost broken down per message and per session - Where the session took place in your git log
You can also use it to: - Resume existing Claude Code sessions (macOS and Windows) - Open focused files directly in your IDE - Connect to remote Claude Code sessions and codebases via SSH
It's for anyone who vibe codes but still wants some insight into what's happening under the hood, and you need to see something to really understand it. I enjoy using Centrality as a companion tool for my own projects, and I hope you do, too!