Skip to main content
Edition No. 1

The Git Gazette

Your weekly repo roundup

·anthropics/claude-code·Last 3 days

Claude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows - all through natural language commands.

2 commits25 PRs30 issues5 releases
summarize

Here's What Matters This Week: Token Limit Bumps, Windows BSOD Fix, and 456-Comment Phone Crisis

Here's what matters this week: 3 releases, 1 critical Windows fix, and a phone verification meltdown that's reached legendary status.

Major releases (#v2.1.76-78): Claude Opus 4.6 now supports 64k output tokens (128k max), MCP elicitation lets servers request structured input mid-task, and /copy N copies the Nth-latest response. Worth upgrading.

Critical Windows fix: PR #35710 prevents blue screen crashes caused by parallel filesystem enumeration. If you're on Windows and seeing Wof.sys BSODs, this tool-mutex plugin is essential.

Community crisis: Issue #34229 hit 456 comments as phone verification remains broken globally. Users report no phone numbers work for signup, and switching devices doesn't help. This is blocking new user onboarding completely.

Documentation cleanup: @coygeek closed 10+ doc issues this week, fixing outdated command references, missing environment variables, and incorrect permission descriptions. The docs are finally catching up to reality.

Platform issues persist: Chrome extension bridge failures (#35684), remote control auth problems (#35949), and private GitHub marketplace bugs (#28125) continue affecting multi-platform users.

Bottom line: Great progress on token limits and Windows stability, but the phone verification crisis needs immediate attention before it becomes a bigger PR nightmare.

Sources: #34229, #35710, #v2.1.78, #v2.1.77, #v2.1.76, #28125, #35949, #35684
Tone:
1 tone change remaining
theater_comedy
The Drama DeskBy Rita Conflictsón

Phone Verification Meltdown Spawns 456-Comment Mega-Thread

BREAKING: The longest-running drama in Claude Code history continues to unfold as issue #34229 reached a staggering 456 comments this week, with frustrated users unable to verify phone numbers for signup.

Folks, we haven't seen community outcry like this since... well, ever. With 521 thumbs-ups and counting, @jpiabrantes' bug report has become a rallying cry for locked-out users worldwide.

"Why did this error persist for so long and no dev noticed?" demands @manhbuithe, echoing the sentiment of hundreds. Meanwhile, @wueme-byte reports that "None of the phone numbers work for signup! Switching devices or using new numbers doesn't make any difference either."

The drama doesn't end there. Over in the private marketplace trenches, issue #28125 has @Satak and 12 others battling Cowork's refusal to accept private GitHub plugins. "I can add the plugin from a private Github repository to Claude Code desktop but not to Cowork or Chat," reports @skray, adding fuel to the platform consistency fire.

But wait, there's more! Authentication chaos spreads to issue #22685, where @SingCheung's desktop app login loop has attracted 14 sympathetic reactions and spawned its own support group.

Developing story: Will the phone verification saga finally find resolution, or are we witnessing the birth of Claude Code's most legendary issue thread?

Sources: #34229, #28125, #22685
Tone:
1 tone change remaining
rate_review

A Dizzying Display of Defensive Programming

This week's exhibition presents a fascinating study in the art of software preservation, with contributors demonstrating what one might call 'protective coding' — the noble practice of shielding one's work from the vagaries of modern computing.

Consider the masterful @VRDate, whose PR #35710 addresses a rather dramatic issue: preventing Windows blue screens through judicious mutex application. The technical description reads like a thriller — "Claude Code executes... with no concurrency limit" — before delivering salvation via the elegantly named "tool-mutex plugin." One observes a surgeon's precision in diagnosing filesystem enumeration chaos.

Meanwhile, @userFRM's worktree-guardian plugin (#35864) operates as a digital archaeologist, scanning for "orphaned agent worktrees with unsaved work." The defensive architecture is admirable — three layers of protection against data loss, like a Victorian mansion with multiple locks.

@cruzlauroiii emerges as this week's most prolific protector, offering no fewer than three defensive solutions: scroll-fix (#35683), bridge-fix (#35684), and powershell-default (#35761). Each addresses what appears to be an ecosystem groaning under the weight of its own complexity.

The discerning reviewer will note a pattern — modern software development has become an exercise in anticipating failure modes that would have mystified programmers of yesteryear. Today's commits read less like feature additions and more like insurance policies.

Adequate.

Sources: #35710, #35864, #35683, #35684, #35761
Tone:
1 tone change remaining
sailing
The Shipping ForecastBy Captain Semver

Steady Winds Across Claude Code Waters — Minor Patches Navigate Token Storms

SHIPPING FORECAST, issued 18 March 0800 UTC: All quiet in the Claude Code shipping lanes — three minor patch releases have cleared customs without incident. Current conditions: stable at v2.1.78.

RECENT PASSAGES: The v2.1.78 vessel arrived Tuesday with cargo including StopFailure hook events for API error handling and persistent plugin data storage via ${CLAUDE_PLUGIN_DATA} variables. Navigation notes report terminal notifications now properly surface through tmux channels.

The preceding v2.1.77 carried significant ballast adjustments — Claude Opus 4.6 token limits raised to 64k with emergency capacity to 128k tokens. Harbor master @ashwin-ant logged improved /copy command indexing and compound bash command fixes for the "Always Allow" maritime protocols.

Worthy of note: v2.1.76 brought MCP elicitation support aboard — servers can now request structured input mid-voyage through interactive dialogs. The --worktree sparse checkout feature provides trimmer sailing in monorepo waters.

FORECAST: Light commit activity suggests smooth seas ahead. The automated changelog updates from @actions-user indicate steady maintenance operations. No major storm systems visible on the horizon — expect continued patch-level releases as the crew maintains course.

NAVIGATION WARNING: Token limit adjustments may affect fuel consumption patterns. All vessels advised to review capacity planning.

Tone:
1 tone change remaining
group
Community PulseBy Flo Stargazer

Star Power: 79K Stars and a Bustling Community Keep Claude Code Cooking

What a powerhouse week for the anthropics/claude-code community! With nearly 80,000 stars and 6,551 forks, this agentic coding tool is clearly resonating with developers worldwide, and the activity shows no signs of slowing down.

Our community pulse this week shows 14 unique contributors staying engaged, generating 25 new issues and 22 thoughtful comments. That's the kind of steady engagement that keeps a project healthy! The conversation flow between community members and maintainers remains strong, which is exactly what you want to see in a rapidly-growing repository.

Looking at our contributor leaderboard, @actions-user continues to be the automation champion with 263 contributions, while @bcherny follows with a solid 70. But here's what really catches my eye — we've got a beautiful distribution across the contributor spectrum. From @ant-kurt's 31 contributions down to our newer faces like @whyuan-cc and @catherinewu at 8 each, this shows a healthy ecosystem where both seasoned contributors and fresh voices are making their mark.

The commit activity shows consistent maintenance with changelog updates, and with Shell as the primary language, this terminal-dwelling tool is staying true to its developer-focused roots. Keep those PRs coming, folks — this community momentum is exactly what drives great open source projects forward!

Tone:
1 tone change remaining
Git Gazette: anthropics/claude-code — March 18, 2026 | The Git Gazette