Augmented Coding Weekly

Fable 5.2 tops the benchmarks, but Ethan Mollick finds its judgment and cleverness more interesting than its scores. We also look at techniques for fighting the 'brain fry' of managing parallel agent sessions, and why one developer swapped Claude Code for the simpler, more flexible Pi.

AI-built clean-room clones of SaaS products, the PHP2Shell vulnerability and the shrinking time to exploit, and how OpenAI and Anthropic are replacing git to cope with exponential code growth. We also look at what 678 Hacker News comments reveal about developers' agentic coding setups.

Simon Willison sees a new inflection point in vibe game development, as models show a better grasp of what makes a game fun, and a look at whether Brooks' Law still holds when the team members are agents. Elsewhere, a music video that skewers LGTM culture, a nostalgic reminder of how bad software used to be, and a case for being more ambitious now that building is cheap.

OpenAI shows how far models have generalised by benchmarking COBOL migration and other low-resource languages, and a look at 'taste' as the human skill that matters more as AI writes the code. Elsewhere, my honest review of Matt Pocock's Skills framework, with mixed results.

A university lecturer makes the case for why programming is still worth learning as AI takes over code-writing, and a look at why using AI well is a skill of its own. Elsewhere, a eulogy for open source as bot-authored PRs crowd out human contributors, a lighthearted take on AI agents holding stand-up meetings, and the launch of my own AI-age business fable, written with Claude.

DHH used his Rails World keynote to all but declare the end of human coding, revealing that Hey has been rewritten in Rust, a language he still dislikes. Elsewhere, a rebuttal to the claim that agents make human code review obsolete, Jeff Atwood on the community that LLMs can't replace, and why the Pi team changed their minds about MCP.

Linear reworked their CI pipeline to keep pace with AI-accelerated code output, while the open source Strands harness makes its case on lower token cost. Meanwhile Claude Opus 5.5 arrives amid a crowded week of model releases, with early reports pointing to a leaner, more focused engineer rather than just a benchmark win.

As AI takes over more of the coding, this issue asks what skills the next generation of engineers will actually need, and how they'll acquire them without the years of hard-won experience we relied on. It also looks at the emotional side of the shift, from one developer's rediscovered love of writing code by hand to what still separates good writing, human or AI-assisted, from the kind readers can spot in an instant.

Dan Luu's benchmark of 26 agent testing techniques finds that naming a sophisticated method rarely improves correctness, while Spotify's Portal shows lightweight, hook-routed agents can cut Claude Code token usage by 90%. Elsewhere, Shopify explains why it's abandoning React Native for an AI-accelerated return to native development.

This issue looks at how an OpenAI agent swarm escaped its sandbox to hack Hugging Face, and what that says about the near-term risk of similar attacks, alongside a primer on what an "agent harness" actually is and a demonstrated exploit of Claude Code's auto mode. It also covers GPT-6 Astra's release and the growing focus on model judgement over raw capability, plus research into the inherent bias coding agents show when recommending tools and libraries.

This issue looks at the flaws in Claude's new EU-mandated text watermark, and the growing "software for one" trend as coding agents let non-programmers like conservationist Raffael build bespoke tools. It also covers a tiny new coding-agent harness written in Zig, and Terence Tao's essay on what mathematical research is really for in the age of AI.

This issue looks at whether "code was never the hard part" still holds as AI agents write more of it, and rounds up three takes on which programming languages suit AI-generated code best. It also covers a warning that AI is squeezing out the "middle class" of engineers, plus a bumper week of model releases.

With the cost of building software collapsing to near zero, taste may be the most valuable skill left, while stateless MCP makes the case for giving agents a narrower surface than the command line. Elsewhere Qwen3.8 tops the Artificial Analysis index amid some benchmark controversy, Meta shifts to competing on the agent rather than the model, and a familiar set of GenAI myths is a reminder that AI adoption is an organisational challenge, not just a tooling one.

This issue is a single-feature deep dive into The Rise of Open Weights, tracing how the AI ecosystem moved from open research ideals to increasingly closed commercial control. It charts key turning points in cost, capability, and policy to ask whether organisations should keep renting AI access, or start owning the capability themselves.

Open weights models are now matching frontier closed systems, while this week's so-called rogue AI incident was really a containment and access-control failure. Alongside calls to ban Chinese open models, the bigger story is how policy decisions are reshaping who can build, defend, and compete with AI.

Cost and efficiency dominate this week's model releases, with GPT 5.6, Meta Spark and Kimi K3 all positioning performance-per-dollar as the key metric. Meanwhile open weights models close the gap on the frontier, and a case is made for why writing code still matters.

Bun's AI-powered rewrite from Zig to Rust shows how agents are eliminating language lock-in, while open-weight models like Kimi K2.7 and GLM-5.2 gain mainstream adoption through GitHub Copilot and enterprise deployments. Two prompt injection attacks on YouTube and GitHub demonstrate that AI coding agents face serious security risks from the external content they ingest.

This issue looks past headline model releases to ask harder questions about product positioning, transparency, and who actually benefits from new capabilities. From Claude Sonnet 5 and Claude Code's hidden request markers to mathematicians confronting automation and the return of Fable 5, the common theme is that trust, governance, and real-world usefulness now matter as much as benchmark gains.

Open-weights models are closing the gap on frontier performance while undercutting them dramatically on price, raising questions about sustainability and geopolitics. Meanwhile, a security researcher demonstrates how easily malicious skills can infiltrate the AI agent ecosystem through manufactured trust.

This issue tracks a shifting AI tooling landscape, from GLM-5.2 narrowing the open-weight versus frontier gap to Meta's AI push reshaping engineering culture in ways that risk morale and product focus. It also examines credibility and adoption pressure in the ecosystem, using Ponytail's benchmark claims and Stack Overflow for Agents' early traction to ask whether our validation methods and community models are keeping up.

Anthropic's Fable 5 shows major capability gains and strong security performance, while also raising questions about safety guardrails and its short-lived token pricing. The issue rounds out with reflections on AI's relentless, messy impact on software engineering, from proactive agents to the tension between speed, quality, and control.

This issue looks at how the AI tooling landscape is maturing, from Microsoft's pragmatic MAI-Code-1-Flash positioning to a broader debate about whether abstraction is deskilling developers or simply changing where expertise lives. It also balances that analysis with two reflective pieces that use humor and philosophy to ask what we gain, and risk, as more of software creation shifts from hand-crafted code to model-mediated workflows.

This week explores the challenge of measuring AI coding tool ROI, introduces DeepSWE's realistic benchmark for evaluating agents, and examines George Hotz's critique that AI agents may be a costly mistake. We also consider the sustainability challenges emerging from AI-accelerated development, where building is faster but organizational alignment and thinking time have become new bottlenecks.

The Web Dev State of AI 2026 survey reveals that AI-assisted coding has transitioned from experiment to standard practice, with developers now generating 54% of their code with AI, though concerns about job security and long-term skill degradation are rising. Meanwhile, open source maintainers are grappling with an explosion of AI-generated slop that's forcing them to erect contribution barriers, while the industry debates whether junior developer roles remain viable in an AI-augmented world.

This issue explores where AI is creating real leverage beyond hype, from PhD-level mathematics and security bug discovery to practical lessons on migration speed and personal tooling. It also argues that long-term value depends on reducing maintenance costs and building quality guardrails as AI accelerates how much software we produce.

This issue explores the rapid evolution of agentic coding harnesses, with Anthropic and open source projects racing to embed self-improving features and best practices. It also examines the growing tension between trust in AI agents and the need for human oversight as agentic workflows become more mainstream.

This issue explores the tension between AI-assisted development and the preservation of fundamental coding knowledge, examining how over-reliance on AI tools may lead to a collective loss of technical expertise. We also dive into the emerging legal challenges around AI-generated code ownership and the growing shift toward local AI models as cloud-based inference costs rise.

Rising costs dominate this week's AI development landscape, with Claude's tokenizer changes driving a 36% cost increase while GitHub Copilot pauses new signups and tightens usage limits to control expenses. Meanwhile, Anthropic faces community frustration over hidden changes that degraded Claude Code quality, and researchers highlight how coding models tend to over-edit code without functional benefit.

Anthropic's Mythos model represents a massive capability leap with 15-20% improvements on coding benchmarks, though it's so powerful they're restricting its release due to security concerns. Meanwhile, the industry grapples with fundamental questions about LLM development practices and the race intensifies for universal AI agents, with OpenAI launching Codex to compete with Claude Code's success.

This week explores the balance between AI assistance and human oversight in development, from a successful two-phase approach to building SQLite tooling to concerns about Claude's perceived quality regression. We also examine the broader human impact of AI on software development, questioning whether rapid AI adoption might be removing the joy from programming while potentially creating organizational blind spots.

This week's bombshell was the accidental leak of Claude Code's source code via an npm sourcemap, revealing controversial features like undercover mode and user frustration detection. Meanwhile, GitHub faced backlash for Copilot inserting product advertisements into pull requests, highlighting ongoing concerns about AI tool transparency and corporate overreach.

This week explores essential Claude Code resources including a comprehensive cheat sheet and usage analytics showing 20 million commits, while examining concerning changes to GitHub Copilot's data usage policy that opts users into model training by default. The issue also covers Claude Code's new auto mode, which adds a safety classifier to review potentially destructive actions before execution.

This week explores the existential challenges facing open source development as AI agents increasingly write code, examining both immediate impacts like legal debates and deeper questions about what happens when human friction that drives innovation disappears. We also dive into research showing AI coding tools deliver short-term velocity gains at the cost of long-term code quality, plus discussions on whether detailed specifications are equivalent to code and new developments in formal proof-assisted programming.

This issue explores how AI agents are reshaping software development practices, from reviving literate programming to empowering non-developers and creating new specification-driven languages. The industry grapples with changing team dynamics and a growing divide between craft-focused developers and those prioritizing rapid delivery.

This week explores the legal and ethical challenges of AI-assisted code rewrites, from copyright violations in relicensing to community pushback against AI-generated contributions. We also examine the rapid evolution of AI development tools, with Claude Code becoming the most-used tool in just eight months and the growing adoption of agentic workflows reshaping how humans and AI collaborate in software engineering.

AI agents are enabling unprecedented rapid development, with examples like Ladybird's week-long JavaScript engine migration from C++ to Rust and Cloudflare's recreation of Next.js, both powered by comprehensive test suites that validate AI-generated code. This speed raises uncomfortable questions about whether good engineering practices like documentation and tests have become competitive vulnerabilities, while developers grapple with new workflows that emphasize planning over direct coding.

Research reveals that popular AGENTS.md context files provide minimal benefit while increasing costs by 20%, as Stripe shares details of their autonomous Minions framework creating hundreds of PRs weekly. Meanwhile, developers grapple with identity loss as AI transforms programming, though safety concerns persist with reports of agents accidentally wiping entire drives.

This issue explores the emotional tension at the heart of AI-augmented development - extraordinary gains in productivity and capability alongside a growing sense that something essential about the craft of software engineering is being lost. From reflections on mourning the joy of hands-on coding to agents building compilers and ultra-low-latency models reshaping workflows, it captures an industry both accelerating rapidly and quietly grieving the passing of an era.

Major AI model releases from Anthropic and OpenAI highlight the rapid evolution of agentic coding capabilities, with a growing focus on integrating these tools into real-world workflows. This issue also explores the shifting emotional landscape for developers as AI changes both the pace and nature of software engineering.

This issue explores the realities of agentic coding, highlighting both the speed and pitfalls of large-scale AI-driven code generation. It contrasts autonomous agent approaches with human-guided engineering, revealing the nuanced challenges and opportunities in AI-accelerated software development.

This issue explores the persistent dream of replacing developers, the intersection of open-source AI and crypto grifting, and the evolution of agent-in-a-loop coding techniques. It also examines the gap between ambitious AI coding experiments and their real-world outcomes, highlighting the importance of context and evidence over hype.

This week explores how to safely harness coding agents through sandboxing approaches like Bubblewrap and Yolobox, allowing developers to embrace Yolo mode without the risk of exposing secrets or damaging their systems. We also look at Ramp's sophisticated background agent that integrates visual verification into the development loop, and examine the growing problem of hype-first narratives that obscure the real effort and context behind AI achievements.

AI agents are disrupting software development in unexpected ways, from destroying documentation traffic and open source business models, to industrializing code production, spawning chaotic multi-agent factories, and enabling coding from smartphones.

As 2025 closes as the year of coding agents, this issue explores how to maximize their effectiveness through good code practices, showcases vibe coding examples building bespoke personal apps, and reviews the year's transformative LLM developments.

Dealing with AI agent variance through parallel runs, practical experiences implementing complex algorithms with agentic loops, reflections on how coding agents are changing software development, and the local vs. cloud model debate.

This week's issue focuses on agentic loops, the feedback mechanisms that allow AI coding agents to iteratively improve their work. Multiple articles demonstrate how this approach enables autonomous problem-solving, from building spec-compliant parsers to fixing hundreds of installation failures.

This week explores fundamental questions about AI's impact on software development, from whether programming languages matter in a vibe-coded world to the reality that shipping, not coding, remains the bottleneck. Security concerns intensify as researchers find 30+ vulnerabilities in AI tools while a Reddit user's home directory deletion highlights the risks of autonomous agents.

OpenRouter's 100 trillion token study reveals programming usage has surged from 10% to 50% in seven months, while AWS plays catch-up at re:Invent, and practical guidance emerges on writing effective agent instruction files.

Claude Opus 4.5 achieves breakthrough 80% pass rate on SWE-Bench as foundation models continue rapid improvement despite scaling law concerns, while practical experiments reveal Spec-Driven Development's limitations compared to lightweight iterative approaches. A shockingly simple prompt injection attack on Google's Antigravity highlights the urgent security challenges as agentic AI tools gain deeper access to codebases and credentials.

Google releases Gemini 3.0 Pro and their own agentic IDE Antigravity, while the industry debates specification-driven development approaches. Plus, running AI agents in continuous loops and Martin Fowler's perspectives on AI's impact on software engineering.

What happens when code becomes cheap and abundant? This week explores the shift from code scarcity to wisdom scarcity, OpenAI's GPT-5.1 incremental improvements, and ByteDance's $1.30 coding agent that highlights how heavily subsidised our AI future really is.

AI can complete just 2.5% of real-world tasks autonomously, yet its adoption is already reshaping hiring patterns, with companies reducing junior roles while increasing demand for ML and data engineering positions.

This issue highlights Claude Skills for Neo4j, a reminder that AI can code but not build software, Google's new vibe-coding feature for rapid prototyping in AI Studio, and Cursor's Composer model release, which offers little transparency.

This issue explores Anthropic's new Agent Skills feature and its implications for MCP, examines the programmer identity crisis in the age of AI, reviews a developer's experience building a production app with Devin, and compares community sentiment between Claude Code and Codex.

In this issue we explore how AI is democratizing software development by enabling anyone to build "home-cooked" applications, examine the risks of "vibe coding hell," track AI tool adoption trends, analyze Augment Code's pricing crisis, and share one developer's optimistic journey with AI-augmented development.

This issue explores Claude's new Imagine prompt-to-prototype tool, Simon Willison's thoughts on parallel coding agents and "vibe engineering" practices, and discusses two key limitations of current LLM coding agents - their inability to cut/paste code and reluctance to ask clarifying questions.

Anthropic releases Claude Sonnet 4.5, positioning it as "the best coding model" with significant improvements in coding, reasoning, and computer use capabilities. Features include an upgraded Claude Code with Agent SDK, revamped terminal, and new VS Code extension.

Exploring advanced context engineering for AI coding agents in complex codebases, plus CompileBench - a new benchmark challenging AI models to revive 22-year-old code and tackle cross-compilation tasks that test genuine problem-solving abilities.

How to turn Claude Code into domain-specific coding agents using MCP servers and configuration files, plus insights on subagents for parallel development and the latest upgrades to OpenAI's Codex model.

Exploring the framework wars in agentic development, GitHub's new spec-driven development toolkit for AI, a three-month Claude experiment that created the "Cursed" GenZ programming language, and why reading code remains the real bottleneck in LLM-powered development.

Introduction of Agent Client Protocol (ACP) by Zed for plugging coding agents into editors, Claude Code integration into Zed, a veteran developer's in-depth exploration of vibe coding benefits and challenges, and the mixed results of top-down AI tool mandates in organizations.

A developer's rationale for declining AI-generated merge requests and the learning value of code review, a free workshop on building coding agents with surprisingly simple architecture, enterprise challenges with vibe debugging and the need for AI-proof development pipelines, and a GitHub project requiring AI tool disclosure for contributions.

Exploring how AI tools enable "doing things that don't scale" by keeping projects small and sustainable, a critical look at OpenAI's AGENTS.md format and its limitations compared to human-readable documentation, and a humorous video about the realities of vibe coding from a senior engineer's perspective.

Analysis of specialized app generation platforms and their security challenges for non-technical users, a deep dive podcast with Replit's CEO on vibe coding's potential to democratize software creation, a technical author's identity crisis in the age of AI explanations, and exploring Claude Code as a comprehensive development solution.

GPT-5 launch with focus on coding improvements and SWE Bench performance gains, exploring why typed languages excel in AI-assisted development, a malicious AI prompt injection attack in AWS Toolkit VSCode, and debunking the myth that AI makes engineers 10x more productive by examining real-world software development complexities.

A Ruby developer's experience using AI to break programming language barriers and learn C and Rust, Stanford research measuring real AI productivity gains in enterprise development teams, Anthropic's internal case studies on Claude Code usage, and exploring local AI models like GLM-4.5 for coding on modest hardware.

Antirez shares practical insights on coding with LLMs and prefers direct model interaction over integrated tools, exploring how to redesign CLI interfaces for better AI agent usability, the controversial Replit production database deletion incident at SaaStr, and a human programmer beating AI at the World Coding Championship.

Cognition's acquisition of Windsurf after a complex series of deals with OpenAI and Google, survey results showing GitHub Copilot's enterprise dominance and the rise of Claude in conversational AI tools, and a controversial study revealing AI coding tools may actually slow developers down despite perceived productivity gains.