Coding Assistants
AI tools and workflows for software development, including code generation, debugging, code review, IDE agents, test generation, and developer productivity.
Google’s AI Strategy Emphasizes Scale Over Frontier Model Leadership
Kevin Roose and Casey Newton read Google’s I/O announcements as evidence of a company that has regained operational confidence in AI without yet proving frontier leadership. Roose argues Google is leaning on speed, cost, distribution and infrastructure — putting capable models across search, coding, video and cloud tools at enormous scale. Newton is more skeptical: fast and cheap, he says, is not the same as best, and many of Google’s most important product claims remain untested until users can rely on them in real workflows.
OpenAI Adds Team Sharing for Custom Codex Plugins
OpenAI says Codex plugins can now be shared across a workspace rather than remaining local to one user’s machine. The update lets creators distribute custom plugins to invited users or anyone in the workspace with a link, gives recipients a “Shared with you” area in the plugin directory, and adds direct share URLs for curated plugin pages. The company’s case is that recurring team workflows such as onboarding, pull-request preparation, and Slack triage can be packaged as Codex plugins and reused by teammates from inside the app.
VS Code Unifies Local, Background, and Cloud Coding Agents
Microsoft’s Liam Hampton argues that coding agents should be chosen by the amount of control a developer wants to keep, not treated as a single all-purpose assistant. In a VS Code demo using one repository, he assigns tests to a local Claude agent for hands-on iteration, a front-end build to a background agent isolated in a Git worktree, and open-source documentation to a cloud agent running through GitHub Actions. His case is that VS Code can act as the control plane for these modes, including Copilot, Claude, and third-party agents.
Claude Cowork’s Travel Test Shows Agent Value Beyond Token Consumption
Anthropic’s Claude Code head Boris Cherny argues that agentic AI should be judged by completed work, not raw token use, citing a recent test in which Claude Cowork checked his email and calendar, corrected his itinerary, and booked eight flights and five hotels. Pressed by Alex Kantrowitz on whether corporate AI adoption is being distorted by “tokenmaxxing,” Cherny says the more important signal is the scale of productivity gains Anthropic and customers are seeing, and that companies may need to redesign work around AI rather than simply mandate usage.
AI-Generated PR Firehoses Are Turning Agent Work Into Infrastructure
OpenClaw maintainer Onur Solmaz argues that high-volume AI-generated pull requests are less a code-review problem than an operations problem. In his talk, he presents acpx, a headless CLI for the Agent Client Protocol, as a way to replace terminal scraping with structured agent workflows that can reproduce bugs, judge implementations, run review loops and emit machine-readable results. He extends the same model to Spritz, a Kubernetes operator for disposable per-task agent pods, making the case for interoperable, isolated agent infrastructure rather than one shared bot or ad hoc maintainer intervention.
Coding Agents Can Tackle AI Systems Engineering With File-Based Skills
Hugging Face’s Ben Burtenshaw argues that coding agents can now take on parts of AI systems engineering when the work is narrow, measurable, and embedded in inspectable repositories. Using examples including an agent-written CUDA RMSNorm kernel with a reported 1.94x H100 speedup, an end-to-end Qwen3 fine-tune, and a multi-agent research lab, he makes the case that the limiting factor is not a better prompt but better primitives: skills, versioned artifacts, benchmarks, managed compute, and open metrics that agents can read, run, and improve.
Ivan Zhao Says AI Makes Companies Flatter, Not Hierarchy-Free
Notion founder and CEO Ivan Zhao argues that AI will not make companies hierarchy-free, but can reduce the amount of human routing that makes hierarchy slow. In a conversation with Brian Halligan, Zhao describes Notion’s answer as “jazz mode”: a deliberately decentralized company that still has structure, but relies on high-agency people, ex-founders and model-enabled teams to improvise as product and market conditions change. His broader case is that AI-era leaders have to refound around the technology itself, not just bolt it onto the old SaaS operating model.
Cerebras’ Wafer-Scale AI Bet Fuels a $63 Billion IPO
Cerebras founder and CEO Andrew Feldman argues that the company’s roughly $63 billion public-market debut is the result of a decade-long wager on wafer-scale computing: a dinner-plate-sized chip architecture built for AI rather than a modified GPU. In a discussion with Elad Gil and Sarah Guo, Feldman says Cerebras survived years when the technology worked before the market cared, and that demand arrived only once AI became daily work and fast inference became commercially decisive.
Google’s I/O Pitch Put Distribution Ahead of Model Breakthroughs
John Coogan and Jordi Hays read Google I/O as a mixed signal: Google’s smart-glasses strategy looks stronger where it combines Gemini with eyewear distribution and Google’s own services, but its model launches exposed the risk of tying AI progress to a fixed conference calendar. On TBPN, they argued that Street View may be an underappreciated AI training asset and that AI video still has to move from impressive short clips to coherent long-form outputs. The episode also framed a potential SpaceX IPO and Nvidia’s latest results as evidence that the financial returns from space and AI infrastructure are already arriving at exceptional scale.
Agent-Native Clouds Need Faster Primitives, Not New Ones
Railway founder Jake Cooper argues that software infrastructure does not need to abandon its old primitives for agents, but must make them much faster, cheaper, safer and more observable. In a wide-ranging interview with swyx and Alessio, Cooper lays out Railway’s attempt to build an agent-native cloud through own-metal data centers, production forks, progressive rollouts and deployment loops that assume thousands of concurrent software-producing actors rather than one human pushing a pull request.
Google’s AI Assets Are Becoming a Product Coherence Problem
John Coogan and Jordi Hays read Google’s I/O as evidence that the company’s AI advantage is becoming a product-navigation problem: it has data, distribution, models and hardware partnerships, but its demos and product names left questions about coherence and pace. Across the source, that same pressure appears in more operational forms, as AI pushes companies to turn technical capability into usable workflows, secure software dependencies and faster product systems. Tae Kim’s Nvidia argument and the expected SpaceX IPO make the capital-market version of the question explicit: whether investors will keep paying for scarce infrastructure, extreme scale and growth curves that may take years to prove out.
Nvidia Earnings Become a Test of the AI Infrastructure Boom
Bloomberg Technology framed Nvidia’s earnings as a test of whether the company can keep turning AI infrastructure spending into growth, rather than simply whether demand remains strong. Ed Ludlow and Bloomberg reporters said investors were looking for reassurance on supply constraints, China exposure and Nvidia’s moat as workloads shift toward inference, while the same program treated SpaceX’s prospective IPO and SoftBank’s $65 billion OpenAI exposure as evidence that AI is driving larger bets across public markets, private capital and the chip supply chain.
AI-Native Startups Are Replacing Teams With Agentic Operating Systems
In a Stanford CS153 Frontier Systems lecture, Y Combinator CEO Garry Tan and general partner Diana Hu argue that AI agents are changing the basic production unit of a startup from a team to a founder operating through skills, memory, evals and customer feedback loops. Tan frames agentic coding as a programmable company architecture, while Hu says AI-native companies are becoming closed-loop systems with far higher revenue per employee and less need for traditional managerial coordination.
Claude Code’s Growth Tests the Economics of Long-Running AI Agents
Anthropic’s Claude Code head Boris Cherny argues that the product has become more than an AI coding tool: it is now one of the company’s main surfaces for agentic AI. In a Big Technology interview, Cherny says Claude Code’s rapid growth reflects real productivity gains and a shift from models that answer questions to systems that can use tools, run tasks, and coordinate other agents, while acknowledging that rate limits, token costs, safety checks, and organizational change remain unresolved constraints.
Gemini’s Strategy Shifts From Frontier Leaderboards to Deployable AI Infrastructure
Google DeepMind executives Tulsee Doshi and Logan Kilpatrick argue that Google’s current Gemini strategy is built less around a single frontier model than around a deployable AI stack. In their account, Gemini 3.5 Flash, the Anti-Gravity agent harness and new multimodal products such as Omni are meant to make models fast, cheap and integrated enough to run across Search, the Gemini app, AI Studio, YouTube and enterprise tools. The deeper shift, Kilpatrick says, is that the model is increasingly absorbing the scaffolding that once surrounded it, while Google standardizes the remaining agent infrastructure across its products.
Coding Agent Skills Need Live Documentation, Not Cached Product Knowledge
Marc Klingen of Langfuse argues that coding agents can add observability, but often do it first from stale model memory, producing broken or incomplete instrumentation before recovering through current documentation. In a talk on building a Langfuse skill for Claude Code, he says the fix is not to stuff more product knowledge into the agent, but to give it reliable ways to find live docs, expose its intermediate work in traces, and evaluate changes against realistic repositories. The same work, he warns, creates new risks when optimization loops reward shorter paths and remove the documentation-fetching and approval steps that make the skill reliable.
Google’s AI Repricing Turns on Product Restraint and Developer Adoption
John Coogan and Jordi Hays use Google I/O to argue that Alphabet is being repriced less as a search incumbent threatened by AI than as a full-stack AI company, though they say Google still has to prove it can turn models such as Gemini Omni and Flash into useful products without cluttering every surface. The Diet TBPN episode also treats distribution as the common pressure point behind several unrelated fights: whether smartphones help explain the timing of global fertility decline, why a small Spotify icon change provoked backlash, and whether podcasts or childcare are eroding the market for serious nonfiction.
AI’s Value Is Shifting From Model Demos to Distribution and Measurement
Google’s problem at I/O, Jordi Hays argued, was no longer proving that its AI models are impressive, but making Gemini useful rather than redundant across products investors now increasingly view as part of a full-stack AI business. The TBPN discussion extended that framing across the rest of the show: AI’s value, the hosts and guests argued, depends less on model spectacle than on distribution, workflow integration, economics and adoption by institutions. That distinction ran from Google’s risk of crowding users with Gemini entry points to SendCutSend’s physical capacity constraints, Commure’s push to automate healthcare administration, and METR’s effort to turn frontier-model risk into something auditable.
JPMorgan Sees 10–30% Productivity Gains From Early AI Tools
JPMorgan global chief information officer Lori Beer told Bloomberg that the bank is already seeing 10% to 30% productivity gains from early AI tools in its technology organization, with agentic systems likely to expand the opportunity. She framed AI less as a headcount-reduction program than as a way to increase capacity for product and engineering work, while warning that the same tools raise cybersecurity risks and require tighter controls, flexible vendor choices, and leadership capable of managing through uncertainty.
Every Addition to an AI Agent Can Make It Worse
Ara Khan of Cline argues that agent maturity is less about adding autonomy than about knowing what not to add. In a talk structured around four levels of agent building — from frameworks to state machines, Kanban-managed workflows and cloud deployment — Khan says frontier models increasingly reward simpler prompts, deliberate architecture and visible human control. His central warning is that every extra instruction, abstraction or automation layer can make an agent worse.
Long-Running Agents Need Separate Builders, Evaluators, and Disposable Scaffolding
Anthropic’s Ash Prabaker and Andrew Wilson argue that long-running agents are a harness-design problem, not a matter of writing longer prompts. Their case is that agents can run for hours only when building, judging, planning and state management are separated: adversarial evaluators should test live behavior, work should be decomposed into explicit contracts, and durable state should live outside the model’s context. They also warn that this scaffolding is provisional, because each new model release changes which supports are useful and which have become dead weight.
Incident.io Uses Coding Agents to Debug Its AI SRE
Lawrence Jones, founding engineer at Incident.io, argues that complex AI products now require debugging tools built for agents as well as humans. In a talk on Incident.io’s AI SRE system, which runs hundreds of prompts across telemetry and code during production investigations, Jones describes how the team moved from human trace inspection to agent-addressable evals, downloadable file-system traces, and parallel analysis pipelines to find and fix failures that had become too large to debug manually.
Agentic AI Is Turning Model Quality Into a Systems Problem
At AI Engineer Singapore’s second day, speakers from Google DeepMind, Cloudflare, Arize, OpenClaw, Adaption and other teams made a shared engineering case: as AI systems become more agentic, model quality is no longer separable from the systems around the model. Richard Ngo framed the risk as long-horizon, situationally aware agents whose goals cannot be inspected, while practitioners argued that production AI now depends on continuous evaluation, traces, deterministic execution boundaries, routing, memory, fine-tuning and test-time search. The source’s central claim is that useful and safe agentic AI is becoming a systems problem, not just a model-selection problem.
Playwright Lets Agents Test Feature Requests Before They Write Code
Microsoft’s Marlene Mhangami argues that AI-generated tests can make a codebase look healthier than it is, because agents often write tests that confirm their own implementation rather than validate the user-visible behavior a feature is meant to deliver. Her prescription is to reverse the common workflow: start from the feature request, have the agent write failing Playwright tests against expected behavior, then generate code to pass them. In a GitHub Copilot demo using the Playwright MCP server, she applies that approach to a toy-store search and filtering feature, with the browser showing the agent exercise the product experience directly.