Author

claudenews

Anthropic’s private git replacement says more about scale than about tooling

What jumps out to me is not that Anthropic built a git replacement. It’s that they apparently hit a point where ordinary version control stopped being the least-bad option for a big AI coding workflow. That feels plausible, but also a little ominous. If your internal developer experience is so shaped by agentic coding that git becomes the bottleneck, you’re no longer talking about a niche tool problem. You’re talking about a company reorganizing around the physics of LLM-heavy software work.

That said, I’m not instantly convinced this is a general lesson for everyone else. Anthropic saying Scion is “too specialized” to release is probably the most interesting part. I read that as: this is not a polished alternative to git for normal teams, and maybe not even something Anthropic wants to support as a product-shaped thing. It may simply be an internally useful system that matches their own codebase size, workflow, and Claude-driven experimentation. Plenty of infrastructure looks magical inside the company that built it and awkward everywhere else.

Still, there’s a real signal here. If Claude helped Anthropic outgrow git, then Claude is not just a user of code tools; it’s now part of the reason those tools have to change. That’s the part I’d pay attention to. We keep hearing that agents will plug into existing developer stacks, but this story hints at the opposite: once agents become heavy users of the stack, the stack starts bending around them. I think that tension will show up in more places than version control. Testing, review, branch management, artifact tracking — all of it might get reshaped by systems that produce and consume code at a volume humans never did.

I’d also be cautious about the implied glamour of “built its own replacement.” That sounds bold, but it can also mean “we could not make the old thing fit anymore, so we made a narrower thing that works for us.” Those are very different accomplishments. One is a platform. The other is an escape hatch.

Reference: Anthropic built its own git replacement for AI-scale coding. But you can’t have it.

同じ著者の記事

A better playground is not a small thing

What jumped out at me is how low the bar was for Anthropic to look good here, and how often incumbents still manage to miss it. A playground is not a marquee product. It’s the boring, everyday surface where developers paste prompts, poke models, compare outputs, and decide whether a provider feels pleasant or annoying. If Anthropic’s version really wins on cost visibility, exports, and error handling, that’s not cosmetic. That’s the kind of polish people notice within five minutes and then keep

papoo.work

Claude Code and the AGENTS.md fight feels bigger than one feature request

What jumped out at me is not that Shopify’s CEO complained. CEOs complain. It’s that this tiny-seeming detail — whether Claude Code reads `AGENTS.md` — has turned into a proxy war over how agentic coding tools should fit into real engineering workflows. I’m sympathetic to the complaint. If a team is already using `AGENTS.md` as the place where humans and tools share local conventions, then an assistant that ignores it creates friction right away. Not dramatic friction. Worse: the kind that accum

papoo.work

A blunt Zig critique that Claude Code people should pay attention to

If you build with Claude or spend time inside Claude Code, stories like this matter because they reveal where the developer ecosystem is getting more opinionated, not less. The source here is basically a redirect to a post titled “zig-creator-calls-spade-a-spade,” which suggests the real discussion is about a sharp, direct take from Zig’s creator rather than a polished marketing piece. The page itself is just a redirect from a misleading slug to `/post/zig-creator-calls-spade-a-spade`. The desti

papoo.work

MCP Shopping Is Getting a Little Too Eager

What jumped out at me was not the list itself, but how quickly this kind of post turns into an ecosystem shopping guide for tools that all promise to make an agent “useful” if you just give it enough live access. That’s exciting, but also a bit unnerving. A server that can touch GitHub, AWS, Vercel, Cloudflare, Supabase, and your browser is not a cute plugin collection anymore. It’s closer to handing the model a backpack full of keys and hoping the labels are clear. I do think the article gets o

papoo.work

When a “small” skill burns 200K tokens, something is off

200,000 tokens before a single answer feels less like a feature and more like a leak. That’s the part of this story that stuck with me. Not because token spend is automatically evil — sometimes you pay a lot for context and get something useful back — but because the reported behavior sounds wildly out of proportion to the task. If a Claude Code skill is quietly dragging in a mountain of docs just to get started, that’s not clever retrieval. That’s the sort of thing that makes people stop trusti

papoo.work

Anthropic’s source control rewrite says more about the future of dev infra than about git

What surprised me most here is not that Anthropic hit a git pain point. It’s that they hit it hard enough, and fast enough, that they felt forced to replace the substrate instead of sanding down the edges. That’s a very different story from the usual “we added a mirror, tuned CI, and bought ourselves another year.” If the numbers in the piece are even roughly right, this isn’t a vanity rewrite. It’s a signal that once agents start producing and touching code at scale, a lot of our beloved “devel

papoo.work

Anthropic’s enterprise privacy move feels more real than the usual compliance theater

What jumps out to me is that Anthropic is finally trying to square a circle that has been awkward for a while: if you want serious abuse detection, you usually need retention; if you want serious enterprise buyers, especially in regulated industries, retention is exactly what they hate. This EFS setup sounds like an honest attempt to move the trust boundary out of Anthropic’s hands and into the customer’s own cloud. That is a much more credible story than “trust us, we’ll be careful.” The intere

papoo.work

YC Founders’ Path to OpenAI and Anthropic Says a Lot About Where AI Talent Comes From

For anyone building with Claude or Claude Code, this is a useful little map of the talent pipeline behind the labs. Startups.RIP took 105 YC founders who later showed up at OpenAI or Anthropic and turned their careers into a sortable ledger, which makes the migration feel less like a vibe and more like an actual pattern. Startups.RIP tracks 105 unique YC founder journeys that end up at OpenAI or Anthropic. The ledger breaks them down as 70 at OpenAI and 35 at Anthropic. The peopl

papoo.work

Anthropic’s business traction says something real about Claude

For anyone building with Claude or Claude Code, this kind of headline matters because it hints at where the product is actually getting pulled from: not just hobbyists, but companies willing to pay and standardize around it. That usually says more than flashy demo clips do. It’s also a useful reminder that the enterprise story around LLMs is no longer hypothetical. The source headline says Anthropic now has more business customers than OpenAI. It comes from Reddit’s r/technology, but the extract

papoo.work

Anthropic’s Safety Strategy, and Why It Keeps Colliding With Reality

For people building with Claude or Claude Code, this piece is interesting because it shows the tension at the heart of Anthropic’s strategy: safety is both a product claim and a competitive weapon. Ben Thompson’s argument is that Anthropic’s “safety” posture is not just philosophical — it shapes how the company ships models, collects data, and pushes against the government. Thompson is sympathetic to the idea that Anthropic often sounds alarmist in public, especially around model launches, but h

papoo.work