Developer hjr265, known for creating the competitive programming platform Toph, published a detailed account this week of building GitTop — an htop-style terminal UI dashboard for Git repository statistics — over a single weekend using Claude Code in a fully agentic workflow. The finished project totals approximately 4,800 lines of Go and ships with seven interactive pages covering commit summaries, activity heatmaps, contributor analytics, branch comparisons, file statistics, release timelines, and a scrollable commit log with diff viewer. The stack combines Bubble Tea for the TUI framework, Lip Gloss for terminal styling, and go-git for direct repository access without shelling out to Git. The project is publicly available on GitHub under a BSD 3-Clause license.
The blog post documents several cases where Claude Code made architectural decisions without being explicitly prompted. When asked to implement a filter system supporting structured DSL queries like author:"alice" and path:*.go, Claude Code first wrote a hand-rolled parser, then rebuilt it cleanly around the Participle parser combinator library when asked, compiling queries into an AST where each node implements a Match(*CommitInfo) bool interface. For visualizations, it independently implemented Unicode braille character rendering for sub-character resolution on chart displays and used Unicode block elements for fractional-width bar charts across other pages — the latter without being asked. For branch filtering, rather than adding branch data to every CommitInfo struct, it pre-computed a hash set by walking reachable commits, keeping the data model clean. The author notes these represent decisions a skilled Go programmer would make, and the surprise was seeing them arrive autonomously within a single session.
The more reflective portion of the post addresses a question the agentic coding era keeps forcing open: <a href="/news/2026-03-15-developer-builds-cutlet-language-with-claude-code-without-reading-code">code ownership</a>. While the feature ideas, product direction, and judgment calls belonged entirely to hjr265, the code itself was written by Claude Code. The author describes genuine satisfaction with the result while also noting an unsettled feeling about not experiencing the same sense of ownership felt with previous projects built line-by-line. "Maybe ownership is more about authorship than I had realized," hjr265 writes, leaving the question open. It is a tension that will only sharpen as these tools become capable of coherent multi-thousand-line output from brief prompts.