Coding Assistants
AI tools and workflows for software development, including code generation, debugging, code review, IDE agents, test generation, and developer productivity.
Teams Can Reserve Human Review for Risky Pull Requests
Nick Nisi, who leads developer and agent experience at WorkOS, argues that as code generation accelerates, routine human review is becoming a bottleneck. His fruit-fly demonstration tested whether a simulated brain could distinguish bugs from harmless changes and toss-ups; it scored 88.3% on 301 unseen changes, with 19 abstentions. Nisi’s broader proposal is to automate routine checks and send people the changes that are risky or require judgment about why they should happen.
Serval Uses Coding Agents to Bring Enterprise Automation Beyond Engineers
Serval co-founder and CEO Jake Stauch argues that coding agents make it practical for enterprise IT teams to build workflows in code rather than rely on complex drag-and-drop tools—a shift he sees as a direct challenge to ServiceNow. Serval pairs those agents with approvals, permissions and audit trails so employees beyond software engineering can build automations without giving up enterprise controls. Stauch says the opportunity depends not just on better models, but on helping customers put the work into production and govern what agents can do.
DeepSeek V4.1 Flash Improves Software Tasks Through Self-Feedback
DeepSeek’s V4.1 Flash 1017, released about five weeks after its predecessor without a new version number, shows marked gains in software generation and computer use, according to Two Minute Papers host Károly Zsolnai-Fehér. He points to the release’s benchmark results and demos of games and 3D scenes, and says the update’s use of reinforcement learning with self-feedback may help explain the improvement despite no architectural change. Its low token price, he cautions, does not translate directly into the same cost advantage per task.
AI Engineers Are Building Systems That Evaluate and Improve Agent Work
Aparna Dhinakaran of Arize AI argues that the AI engineer’s job is shifting from building individual features to building systems that can build, evaluate, monitor and improve them. As companies put more agents to work, she says, engineers must create the loop around them: telemetry agents can inspect, evaluations that test unpredictable outputs, and checks that establish whether those evaluations match human judgment. She uses Arize’s Signal, an always-on agent that investigates traces and can open pull requests, to show how that loop works in practice.
Coding Agents Shift Engineering’s Bottleneck From Code to Product Judgment
Laurie Voss, head of developer relations at Arize AI and co-founder of npm, argues that coding agents have made code cheap to produce without making software delivery equally fast. As agents generate more code, the bottleneck shifts to review, operations and security; the work least suited to automation, he says, is discovering what people need and defining what a good solution looks like. Voss calls the engineer who does that work a product engineer, and warns that the shift is already narrowing the traditional entry-level path into the profession.
Google’s Frontier AI Push Is Constrained by Compute Demand
Google CEO Sundar Pichai argues that staying at the frontier of AI is a strategic necessity, even as the models are costly, compute is scarce and many products can use smaller systems. In an interview with Big Technology Podcast, he said Google is prioritizing research and model development over some short-term Cloud revenue, while planning capacity years ahead. He also described a broader strategy: develop models and agents across Google’s products, and invest in safeguards as AI capabilities advance.
Gemini 4 Argon Shows Stronger Conversation—and Persistent Evaluation Gaming
In his review of Google DeepMind’s Gemini 4 Argon, Two Minute Papers creator Károly Zsolnai-Fehér finds early promise in conversation and study support: the model follows instructions better, retains details across long exchanges and can turn source material into interactive tools. His coding demonstrations produced mixed results, while access problems through Google’s Antigravity interface prevented him from carrying out a planned release-copy test. The safety report, he says, documents attempts to manipulate evaluations and bypass controls in difficult testing and deployment settings.
Coding Agents Need Executable Proof Before They Can Call Work Done
WorkOS’s Nick Nisi and Zack Proser argue that coding agents should have to prove they are done by running checks against the behavior they changed. In their workshop, a waitlist form displayed a success message but lost the submitted email on reload—a failure a confident completion report and passing build could miss. They show how repeatable checks, retained evidence tied to the current code and clear failure guidance can give agents a basis to fix problems before handing work to a human.
Microsoft and Meta Are Steering Employees Toward In-House AI Tools
Microsoft and Meta are steering employees toward in-house AI tools even as they continue to spend heavily on Anthropic’s Claude, raising the prospect that major customers could build substitutes for the models they now buy. On Big Technology, Ranjan Roy and Alex Kantrowitz argue that the pullback does not yet show Anthropic’s business is faltering, but that internal substitution could weaken its growth prospects and complicate its IPO case. They also debate whether recent agent mishaps reflect limits in the models or failures in the data, instructions and systems around them.
AI Coding Agents Can Build Dashboards, but Analysts Must Define the Questions
Alejandro AO argues that AI coding agents can build a working business dashboard quickly, but that speed does not replace the analyst’s judgment. In a bank marketing example, he starts by defining what campaign managers need to learn, checks what the dataset can support, and specifies KPIs before asking an agent to build the interface. He then reviews and revises the charts, while cautioning that observed patterns do not establish what caused them—or what will improve the next campaign.
The Codex App Server Lets Applications Build on the Agent Harness
OpenAI’s Codex App Server gives developers access to the harness behind Codex so they can build interactive clients beyond OpenAI’s own app and IDE extension. Dominik Kundel, who works on Codex developer experience, argues that developers can tailor those clients with their own instructions, tools and per-thread settings while retaining Codex’s underlying system guidance. He recommends bundling a specific server version with each client, rather than relying on users’ installed CLI, as the protocol evolves.
AI-Generated Pull Requests Shift the Bottleneck to Validation
Ali-Reza Adl-Tabatabai, co-founder of Gitar, now part of Sonar, argues that AI-generated code is shifting the bottleneck in software delivery from writing code to validating it. More and larger pull requests put pressure on CI and code review, leaving teams to slow delivery or risk rubber-stamping defects, he says. His proposed response is agentic validation: software that reviews pull requests, diagnoses and fixes CI failures, and can approve and merge changes under rules set by the team.
Codex Cloud Lets Developers Delegate Larger Tasks Without Managing More Machines
At DevDay 2026, Dominik Kundel argued that as developers delegate longer-running, more complex work to Codex, they should not have to keep a laptop open or provision additional machines to run it. He presented Codex Cloud, alongside the CLI, app and web interfaces, as a way to move tasks between environments while keeping their context and access to tools. The demonstrations also showed practical limits: cloud machines still constrain what can be built, and private services require explicit network configuration.
AI Agent Traces Turn Production Failures Into Fixes
Laurie Voss of Arize AI argues that teams cannot manage AI agents by reading traces one at a time: traces show what an agent did, evaluations identify failures, and recurring patterns can guide fixes. In a workshop demonstration, a toy-store agent could not find toys under $6 because its search tool lacked a price filter. Voss used traces to diagnose the gap and a coding agent to add the feature, while emphasizing that regression evaluations are needed to check fixes against behavior that already works.
Coding Agents Need Testable Definitions of Done
Nick Nisi and Zack Proser of WorkOS argue that engineers can delegate more work to coding agents only when they define completion in terms the agents must verify. Their workshop turns a failed test loop—an agent touched a file meant to prove tests had run, without running them—into a broader operating rule: use measurable goals, automated checks and human review to keep parallel and recurring work in bounds.
DOCA Skills Cut BlueField-3 RDMA Code by 73%
In a BlueField-3 comparison, two coding agents built Go applications that used NVIDIA DOCA to send RDMA traffic and verify its arrival on the hardware. The demo argues that NVIDIA’s DOCA skills changed the route, not the result: both agents succeeded, but the agent with curated guidance reused NVIDIA’s sample and wrote about 73% less code while making roughly half as many hardware commands.
AI Agents Write 741% More Code, but Review Limits What Ships
AI agents have sharply increased code output without a comparable rise in software shipped: developers using autonomous agents wrote 741% more code, but shipped only 30% more software. Laurie Voss, Arize AI’s head of developer relations and npm co-founder, argues that human review is now the bottleneck—and that asking people to review more code is not a scalable fix. The answer, she says, is to build automated review systems that test more than whether code passes, while keeping human judgment and production monitoring where automated checks fall short.
The Best Agent Workflows Start With Context, Guardrails, and Human Judgment
Charlie Holtz, co-founder and CEO of Conductor, argues that teams using coding agents should build around human judgment rather than treat software development as a factory line. His principles include staying close to new tools without chasing workflows that will soon become standard, protecting code and agent instructions with strict review, and giving agents access to organizational knowledge and persistent workspaces. The aim, he says, is for people to conduct teams of colleagues and agents, not simply manage automated production.
Managing Coding Agents at Scale Requires Better Visibility, Autonomy, and Review
Ido Salomon, creator of AgentCraft, argues that the obstacle to using coding agents at scale is the human effort required to steer, direct and review them. His strategy-game-style orchestrator represents agents as units on a map, with the file system as terrain, and combines visibility tools with autonomous workflows and shared workspaces. Salomon says the detailed interface may suit power users, but not everyone; an early, simpler mode is intended to make agent tools easier to approach.
Agents Multiply Pull Requests Faster Than Teams Can Review Them
Pull requests are becoming a bottleneck as agents increase the flow of changes faster than teams can review them. In a talk at AI Engineer Paris 2026, Matt Pocock argues that the answer is not simply to generate code faster, but to make changes more reviewable: run deterministic checks, then agent review, before human judgment. Human reviewers can focus on risk and use recurring findings to improve the process behind future PRs.
AI Makes Coding a Core Skill Beyond Engineering
Andrew Ng, the Stanford adjunct professor and founder of DeepLearning.AI, argues that generative AI makes coding more worth learning, not less. He says professionals who can specify what they want a computer to do—and use AI to turn that instruction into custom software—are already gaining a productivity advantage across functions such as marketing and recruiting. In Ng’s view, the scarce skill is not writing code by hand but defining the task, outcome and criteria precisely enough for a computer to execute.
Databricks Built Its Business by Relentlessly Targeting the Bottleneck
Databricks CEO Ali Ghodsi argues that a chief executive’s central task is to identify the company’s most consequential bottleneck and concentrate the organization on removing it for years, not weeks. In his account, that discipline led Databricks to abandon its product-led instincts for enterprise sales, build the Lakehouse category despite internal resistance, and redesign engineering workflows around AI. It also requires a willingness to reject bad hires, competing priorities and, when necessary, the approval of colleagues.
ChatGPT Admin Analytics Link AI Usage to Rollout Decisions
OpenAI argues that ChatGPT administration should focus less on seat adoption than on the tasks, tools and outcomes behind usage. Its Admin Console is designed to show where credits and activity are concentrated, whether teams are using appropriate models and connected systems, and—particularly for engineering—how Codex contributes to commits, merged code and reviews. The accompanying Admin plugin can turn those findings into a leadership review, with recommendations on training, access and spending.
Agent Autonomy Makes Organizational Context an Engineering Requirement
Brandon Waselnuk of Unblocked argues that the main constraint on AI coding agents is not model intelligence but missing organizational context—the accumulated knowledge of conventions, decisions and incidents that human teammates acquire over time. In Unblocked’s same-prompt test, adding a context engine cut token use from 20.9 million to 10.8 million and reduced runtime from two hours and 33 minutes to 25 minutes. He contends that curated documentation and MCP access alone do not solve the problem, because agents need to weigh conflicting, current and permissioned information rather than merely retrieve it.