developer-tools

2 posts with the tag “developer-tools”

Agents Killed the Pull Request: Zed Launches Delta in Public Beta

Sep 17, 2026

Christopher Shaun Godwin

Author

Agents Killed the Pull Request: Zed Launches Delta in Public Beta

Zed did something most teams treat as unthinkable: it turned off pull requests on its own repository. On September 16, 2026, the company launched Delta in public beta (Zed, 2026). Delta is a multiplayer environment where developers and coding agents work, review, and revise code together in shared threads (Zed, 2026). The pull request, says CEO Nathan Sobo, does not fit a world where agents write most of the code (Zed, 2026).

Why the pull request is the problem now

“Since GitHub introduced pull requests over 15 years ago, they’ve become the standard way to ask teammates to review changes to your codebase,” Sobo writes (Zed, 2026). “But with agents generating so much code, the diffs we’re asking each other to review have mushroomed” (Zed, 2026).

A small diff still hides the decisions behind it. A reviewer often feeds the diff to another agent, and that agent has to reconstruct choices the author already worked through (Zed, 2026). The result is a review loop built for human-sized changes, applied to agent-sized output.

The pressure on GitHub itself is real. The platform suffered a near-eight-hour outage in August 2026, with web and API error rates reaching around 20 percent at the height of the incident (InfoWorld, 2026). “Everyone is in a race to replace GitHub right now,” Sobo says (Zed, 2026). Most contenders promise better uptime on top of the same old primitives: branches, commits, and diffs (Zed, 2026). Zed instead bets that the thread becomes the new unit of software development (Zed, 2026).

How Delta works: the thread replaces the PR

Delta’s core unit is the thread: a running record of an agent-assisted task where the conversation and the files stay connected (Delta docs, 2026). Collaboration no longer depends on committing and pushing code (Zed, 2026). You invite teammates directly into the conversation with the agent. They see the same worktrees you do, on their own machines, and can ask the agent why you chose a Mutex instead of an RwLock (Zed, 2026). If you log off, they can keep working with the agent where you left off (Zed, 2026).

Review happens in dedicated subthreads (Zed, 2026). A review subthread gets an isolated copy of the parent thread’s worktrees (Zed, 2026). The reviewer can explore the code with agents, try changes without disrupting the original work, and request a revision or fix it themselves (Zed, 2026). Fixes made during review fold back into the parent thread before landing (Zed, 2026).

The storage layer is DeltaDB, which extends Git’s content-based versioning with incremental versions called deltas (Zed, 2026). It records edits between commits alongside the messages from humans and agents, so the code’s evolution stays attached to the reasoning behind it (Zed, 2026). A commit remains the checkpoint you push, pull, and build from (Zed, 2026). Git compatibility is intact: teammates who never open Delta still see a normal Git repository (Zed, 2026).

Zed calls the resulting workflow continuous engineering: the idea, the implementation, the review, and the landing of a change all happen in one place (Zed, 2026). CI is not replaced yet. For now, an agent triggers a run with an existing CI provider and checks the results before landing the change (Zed, 2026).

The proof is in Zed’s own repo

Zed disabled pull requests on the Delta repository last week and now builds the product entirely within Delta (Zed, 2026). Since the switch, 33 developers have landed 570 changes to main without using pull requests (Zed, 2026). Sobo expects the company is only a few months away from leaving GitHub behind entirely (The New Stack, 2026).

Delta is not a fork-and-run migration. It rides alongside Git today: you can use it with any repository, keep GitHub for community contributions, and share Delta threads next to pull requests (Zed, 2026). The company keeps zed-industries/zed on GitHub because hundreds of external developers contribute there each month, and it does not want to strand them (The New Stack, 2026). Delta is free during the public beta, with paid plans coming later and a free version promised forever (Zed, 2026). It runs on macOS, Linux, and Windows, on the web without any download, and from a mobile browser (Zed, 2026).

For context, Zed is not a new player. The editor was founded in 2021 by veterans of GitHub’s Atom editor team, and the company raised a $32 million round led by Sequoia Capital in August 2025 (The New Stack, 2026).

What this means for your team

Review the conversation, not just the diff. Agents produce context a diff cannot carry. When the reasoning is attached to the change, reviewers stop reverse-engineering it (Zed, 2026).
You can start without migrating. Run threads alongside pull requests. Contributors who never open Delta still get a normal Git repository (Zed, 2026).
Automate the landing loop. Zed’s own flow: the agent squashes the work into one commit, pushes a branch, runs CI, lands on main after CI passes with approval, then deletes the branch (Zed on X, 2026). That same squash-and-merge discipline is how this very post ships to production through the cgodwin.io merge-request flow.
Watch the race to replace GitHub. The outage in August showed the cost of a single review platform (near-8-hour, ~20 percent error rates at the peak) (InfoWorld, 2026). Sobo is explicit that most challengers just promise uptime on old primitives; Delta is the first serious bet that the review artifact itself changes (Zed, 2026).

The takeaway

Pull requests were designed for human review of human diffs. Agents changed the volume and the context of the code, and the review tool did not change with it (Zed, 2026). Delta’s bet is that review becomes a shared conversation with the agent, not a batch handoff of files. It is in public beta, running in production on its own dogfood, and 570 changes in. Download it today and try a thread with your next agent-driven change (Delta, 2026).

Anthropic Calls It a Permanent 25% Raise. Your Claude Code Meter Drops 17% on September 14

Sep 6, 2026

Christopher Shaun Godwin

Author

Anthropic’s Claude Code announcement reads like a win. Starting September 14, weekly limits go up 25% for Pro, Max, Team, and seat-based Enterprise plans. Permanently. Set that headline next to the meter in your terminal and the story inverts: what you get drops about 17% against today (BleepingComputer).

Both numbers are true. Only one of them lands on your usage bar.

The Arithmetic

Claude Code’s weekly allowance has been running on a temporary 50% boost. Anthropic’s developer account announced the change on X on August 29: “Starting September 14, we’re permanently raising standard weekly limits in Claude Code by 25% for Pro, Max, Team, and seat-based Enterprise plans. Until then, the current 50% increase will be in place.” (Anthropic on X)

Limit state	Value (baseline = 100)
Original weekly baseline	100
Today, with the temporary boost	150
From September 14, permanent	125
Change vs. pre-promo baseline	+25%
Change vs. today’s meter	-17%

If your plan’s original weekly allowance was 100 units, you get 150 today. On September 14, that becomes 125. You end with a quarter more than the old baseline and a sixth less than what you are burning right now (BleepingComputer).

The Walk-Back

The framing did not survive contact with users. Readers attached context notes to the announcement, and community members called out the post for leading with the gain while leaving out the net reduction. Anthropic employees conceded the messaging could have led with the change (X). The company then deleted the original thread and published a clarification that states the number outright: “Compared to today, this works out to a 17% reduction in weekly limits on Claude Code.” It added that it is working on changes that give users “more visibility and control” over usage (Windows Report).

Theo of t3.gg posted a public reply coaching Anthropic on announcement writing: lead with the delta from the meter users see today, not the baseline nobody remembers (X).

Why the Meter and the Headline Diverge

The temporary 50% boost was never built to last. It was scheduled to end August 31, and Anthropic extended it twice, most recently to September 14 (explainx.ai). A promotion inflates a baseline. When it ends, the meter drops even though the underlying limit never moved. For anyone who budgeted against 150, the switch to 125 reads as a cut, because against their working number it is one.

The frustration runs deeper than one post. Through July and August, users reported weekly allowances draining faster than expected. One report from August 15 describes a two-hour session consuming an entire five-hour window plus 17% of a weekly limit. A user on the $200-per-month Max 20x plan said a fresh subscription hit its weekly cap after roughly two and a half hours (Uprise RI). A federal lawsuit over how Anthropic marketed its Max plan multipliers sits in the background (explainx.ai).

Anthropic’s position is that usage varies by conversation length, model choice, tool usage, and effort level, so no weekly allowance translates into a fixed number of prompts (BleepingComputer). That is honest arithmetic. It also means the only number you can trust is the one in your own terminal.

The debate is still live. On Hacker News this weekend, the defense of Anthropic is simple: the boosted amount was always temporary, and the app said so every time it opened (Hacker News). The complaint is just as simple: “25% more” and “17% less” describe the same event, and the announcement picked the flattering one (Hacker News).

What to Do Before September 14

Re-baseline your budgets at 125. If you plan agent capacity against today’s 150, every week after September 14 goes over. Update the runbooks and the cost sheets now.
Spend promo capacity on real work this week. Long refactors and bulk migrations burn weekly allowance fastest. Run them before September 13.
Check /usage, not the docs. Anthropic says allowances do not map to a fixed prompt count. Your meter is the only live number.
Read every limit announcement against the current meter. Percentages need a reference point. Ask which one the sender is using. If the announcement anchors on the baseline and your meter anchors on a promo, expect the smaller number to win.

The Takeaway

Anthropic frames the change as sustainability: “Thanks for hanging with us while we figured out what we can sustainably serve going forward” (Anthropic via Hacker News). Subsidized 150% capacity was never going to last, and operators know subsidized capacity when they see it.

The order of operations still matters. State the cut first, then the raise. Teams plan against the meter in front of them. An announcement that anchors on the baseline and buries the delta spends trust to save a headline. Developers noticed in hours. Your users will too.