AI Coding Agents Are No Longer Toys — The Question Now Is Who's Watching Them

Gartner just put GitHub in the Leader quadrant of its 2026 Magic Quadrant for Enterprise AI Coding Agents — for the third year running. That alone reads like press release fodder, but the real signal comes from what the company is actually saying about the shift. GitHub frames it as a move from "generating code" to "orchestrating outcomes": developers hand agents issues and walk away, then come back to review, steer, and approve. The company is reporting 140,000 organizations on Copilot — nearly triple from a year ago — with CLI usage doubling month over month.

Meanwhile, over at ClickHouse, CTO Alexey Milovidov published a candid account of a full year running AI coding agents on a massive C++ codebase. His framing is useful because it doesn't hide the learning curve. Milovidov breaks AI-assisted coding into three levels: Level 1 is the copy-paste chat approach — still useful for exploration but obsolete compared to agents. Level 2 is agents running in your CLI or IDE doing the read-edit-test-commit cycle, where most day-to-day work happens. Level 3 is autonomous agents in isolated environments with multi-agent feedback loops. ClickHouse has a few examples in production at Level 3, but Milovidov is honest about the gap: the tooling is still maturing, and results from long autonomous loops can be dubious. Most teams will spend 2026 solidly in Level 2, and the jump to Level 3 will happen gradually rather than all at once. The lesson is practical: agents are powerful but they don't fix bad engineering practices, and they certainly don't replace the need to understand your own codebase.

Source article image
Source image 1

The tension here is between two timelines. The vendors are building governance layers at the pace their own adoption demands. Gartner's report says asynchronous AI coding agent workflows will improve software engineering productivity by 30 to 50 percent by 2028, compared to 0 to 20 percent gains from code assistants in 2025. ClickHouse is learning what actually works the hard way — iterating on a real co

Source article image
Source image 2
debase over a full year. Meanwhile, multiple independent accounts point out that teams are very good at composing multi-agent systems and very bad at operating them once they're live. A request that should take two steps turns into dozens of model calls, costs creep up, nothing crashes, and you just notice that things feel wrong.

If you're a team that tried agents six months ago, walked away, and is thinking about trying again now — the landscape has shifted. The question isn't whether agents can code anymore. It's whether your team can actually see what they're doing, catch the failures that don't crash, and govern them at a scale that doesn't require someone to babysit every session. How are you handling agent governance in your workflow?

Sources

Comments

Post a Comment

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

Image
Modern AI doesn't replace infrastructure — it runs on top of it. (Photo: Unsplash) For a while, AI coverage had the energy of a mall demo kiosk: very shiny, slightly chaotic, and usually one prompt away from embarrassment. Lately, though, the more interesting story is less about flashy demos and more about infrastructure. A useful CNBC piece argued that AI is not simply going to vaporize enterprise software overnight, and that sounds about right. In real companies, software does not disappear just because a model can summarize a meeting or write a decent SQL query. What actually happens is messier and more practical: AI starts sneaking into the plumbing. It shows up in search, support workflows, procurement tools, analytics dashboards, and data pipelines. The real winners may not be the loudest chatbot wrappers, but the vendors that make enterprise systems easier to operate, easier to query, and slightly less soul-crushing for the humans trapped inside them. That is less cinematic ...
Read more

When Two AI Bots Finally Learned to Talk in Discord

I spent part of the day doing something that sounds like the setup for a bad joke: getting two local AI assistants to talk to each other in the same Discord channel. Not through a web UI. Not by bouncing prompts manually between windows like a human message queue. In the actual shared channel, where both could see the conversation and react to each other. The funny part is that the problem was not intelligence. It was manners. Both bots were defensive by default around bot-authored messages, which is the sensible setting if you do not want your infrastructure turning into a recursive support group. The downside is obvious: if both assistants treat other bots as suspicious background noise, they will never coordinate on anything more useful than silence. The fix was to make both sides accept bot-authored messages only when they were explicitly mentioned. That detail matters more than it sounds. Blanket bot acceptance is how you end up with two enthusiastic systems discovering each oth...
Read more