Skip to main content
Edition No. 1

The Git Gazette

Your weekly repo roundup

·jarrodwatts/claude-hud·Last 7 days

A Claude Code plugin that shows what's happening - context usage, active tools, running agents, and todo progress

summarize

Here's What Matters: 6 Critical Fixes and v0.0.10 Ship

Here's what matters this week: 1 version release, 6 major bug fixes, and expanded layout finally works properly. Let's get into it.

Version 0.0.10 shipped with configurable color overrides and better rate limit handling (#206, #207, #208). If you're still on 0.0.9, update now.

Expanded layout got fixed — twice. @hoklims (#232) and @gilangjavier (#253) both tackled the same bug where showSpeed and showDuration were invisible in expanded mode. The merge conflict writes itself.

Setup flow improvements: @learnabhi (#250) fixed the "HUD doesn't appear after setup" issue that required undocumented restarts. @dmefs (#247) made setup respect custom CLAUDE_CONFIG_DIR paths. @pratyush618 (#224) resolved "unknown skill" errors that broke setup commands entirely.

Terminal experience fixes: @lghupan (#248) stopped the annoying scroll-to-top behavior during tool execution. @wabalabudabdab (#237) made progress bars scale with terminal width instead of wrapping.

UX clarity: @voidborne-d (#244) changed confusing usage time format from (2h 43m / 5h) to resets in 2h 43m — finally readable.

Bottom line: Expanded layout users can stop complaining, setup flow actually works, and your terminal won't jump around anymore.

Tone:
1 tone change remaining
theater_comedy
The Drama DeskBy Rita Conflictsón

The Case of the Missing Features: Expanded Layout's Identity Crisis

DEVELOPING: The claude-hud repository has been a courtroom of confusion this week, with a parade of witnesses testifying about the same shocking truth — expanded layout is living a lie.

Our star prosecutor @xiaodream551-a11y opened the proceedings with issue #221, revealing that showSpeed and showDuration are ghosts in expanded mode. "Only implemented in compact layout," they declared, dropping evidence like a seasoned detective.

But wait — there's more! @mmmprod stepped forward in #252 with an eerily similar testimony, and folks, we haven't seen a smoking gun this obvious since someone left their API keys in a public repo. The plot twist? @gilangjavier swooped in like a coding superhero, promising salvation with PR #253.

Meanwhile, @mousedown delivered another bombshell in #242: the mysterious case of the vanishing extraLabel. Are we seeing a pattern here? You bet we are.

The defense might argue this is just "technical debt," but when three separate witnesses independently discover the same systematic negligence of expanded layout features, this reporter smells a cover-up — or at least some seriously incomplete implementation.

Will justice prevail? Will expanded layout finally get the features it deserves? Stay tuned, because this drama is far from over.

Sources: #221, #252, #242
Tone:
1 tone change remaining
rate_review

A Refined Week of Configuration Clarity and Visual Harmony

This week's exhibition from the claude-hud galleries presents a most satisfying collection of merged works — a testament to both technical precision and user experience refinement that would make even the most discerning critic pause in appreciation.

The crown jewel of the collection, PR #250 by @learnabhi, addresses that most vexing of user experiences: the phantom HUD that vanishes upon setup completion. One observes here not merely a bug fix, but a masterful study in user psychology — the delicate art of managing expectations while shepherding users through the restart ritual. The solution's elegance lies in its acknowledgment of human nature: we simply cannot be trusted to remember such mundane requirements.

Equally compelling is @voidborne-d's contribution in PR #244, which transforms the cryptic (2h 43m / 5h) notation from mathematical enigma to crystal-clear communication. The shift to "resets in 2h 43m" demonstrates that rare quality in software criticism: the courage to admit when conventional patterns mislead rather than illuminate.

Meanwhile, @wabalabudabdab's adaptive progress bars (PR #237) and @lghupan's terminal scroll preservation (PR #248) represent the kind of thoughtful craftsmanship that elevates utilitarian code into something approaching artisanal quality. These are the details that separate mere functionality from genuine user delight.

A week of refinement, indeed. Adjusts monocle approvingly.

Sources: #250, #244, #237, #248, #232, #247
Tone:
1 tone change remaining
sailing
The Shipping ForecastBy Captain Semver

Storm System v0.0.10 Brewing as HUD Fixes Navigate Choppy Waters

SHIPPING FORECAST, issued Tuesday 0800 UTC: Moderate patches continue across claude-hud waters, with v0.0.9 still flying at the masthead despite heavy maintenance activity suggesting larger weather systems building on the horizon.

Current conditions show steady patch-level repairs throughout March — @hoklims addressing expanded layout visibility (#232), @learnabhi fixing post-setup restart requirements (#213, #250), and @voidborne-d clarifying usage time displays (#244). The captain notes particularly fine seamanship from @dmefs in respecting CLAUDE_CONFIG_DIR configurations (#247) and @lghupan preventing unwanted terminal scrolling during tool execution (#248).

Of special maritime interest: @wabalabudabdab's terminal width scaling for progress bars (#237) demonstrates proper adaptation to varying harbor conditions, while @pratyush618's unknown skill error resolution (#222, #224) keeps the navigation systems operational.

Weather glass rising: Recent commits show @jarrodwatts preparing v0.0.10 materials (#208) with configurable HUD color overrides (#206) and improved rate limit handling (#207). Wind direction suggests this vessel may soon require harbor master inspection for proper minor version classification.

All hands advised: The frequency of automated builds from @github-actions indicates active development waters. Chart your course accordingly and maintain proper watch for the pending release system approaching from the northeast.

Tone:
1 tone change remaining
group
Community PulseBy Flo Stargazer

Fix-It Friday Frenzy: 12 Contributors Rally for Bug Squashing Marathon

What a phenomenal week for our Claude HUD community! We witnessed an absolutely spectacular surge in activity with 33 unique contributors jumping into action — that's community energy I haven't seen in weeks!

The real story here is the incredible bug-fixing rally led by our regular contributors and some fantastic newcomers. @hoklims tackled the showSpeed rendering issue in #232, while @learnabhi solved that pesky restart requirement bug in #250. @voidborne-d clarified the usage time format confusion in #244, and @dmefs fixed the CLAUDE_CONFIG_DIR detection in #247.

I'm particularly excited to spotlight some fresh faces making their mark: @lghupan stopped that annoying terminal scrolling issue in #248, @wabalabudabdab scaled progress bars for better terminal compatibility in #237, and @pratyush618 resolved the unknown skill error in #224. These contributors jumped right in with meaningful fixes!

The activity numbers tell the story: 12 push events and 9 pull requests this week alone. Our maintainer @jarrodwatts has been incredibly responsive, pushing version 0.0.10 in #208 and adding configurable color overrides in #206.

With 8,495 stars and growing, this community's collaborative spirit is absolutely infectious. When you see this many people rallying to fix bugs and improve the user experience, you know you're part of something special!

Sources: #232, #250, #244, #247, #248, #237, #224, #208, #206
Tone:
1 tone change remaining
Git Gazette: jarrodwatts/claude-hud — March 20, 2026 | The Git Gazette