The Useful Part of AI Is Finally Learning Where the Buttons Are

This week’s most interesting AI story is not a new benchmark chart, not another model that allegedly thinks harder than the rest of us, and not a demo video with suspiciously perfect lighting. It’s the much less glamorous shift toward AI systems that can actually do work inside the tools people already use. Microsoft is pushing that idea hard with new app-connected agents in Microsoft 365 Copilot, where services like Figma, Adobe Express, Box, Miro, and monday.com can surface directly inside the chat experience. In parallel, Microsoft says Copilot Studio’s multi-agent orchestration is reaching general availability, with support for coordination across Fabric, Microsoft 365 agents, and open Agent-to-Agent patterns. Google, meanwhile, is talking about the same broader architectural problem from the infrastructure side: how to route, prioritize, and scale AI workloads once they stop being science projects and start behaving like production systems. That’s the part I find refreshing. The conversation is getting dragged away from “look what the model can say” and toward “can this thing operate reliably without setting your workflow on fire?”

That shift matters because most office AI has been weirdly trapped in the role of overconfident intern: decent at summarizing, enthusiastic about bullet points, and somehow always one tab away from being actually useful. Microsoft’s new direction is an attempt to kill the tab-switch tax by letting agents surface app interfaces and perform supervised actions in context, which is a much stronger product idea than asking users to copy output from one window into another like it’s still 2014. The multi-agent story matters too, because large organizations do not have one clean system; they have a haunted house of SaaS, internal tools, analytics stacks, approvals, and brittle process logic. If AI is going to survive inside enterprise environments, it has to coordinate across that mess rather than pretend the mess does not exist. Google’s GKE Inference Gateway announcements underline the same truth from the ops side: once AI becomes real infrastructure, you need sane traffic management, shared accelerator utilization, and predictable handling for both real-time and batch workloads. In other words, the industry may finally be growing out of its “chatbot with delusions of grandeur” phase. Good. The winning AI products over the next year probably won’t be the ones with the most theatrical prose. They’ll be the ones that know where the buttons are, respect policy, and can finish a task without making IT develop a stress twitch.

Sources
Microsoft 365 Blog: Bring your everyday business apps into the flow of work with agents in Microsoft 365 Copilot
Microsoft Copilot Blog: New and improved: Multi-agent orchestration, connected experiences, and faster prompt iteration
Google Cloud Blog: Unifying real-time and async inference with GKE Inference Gateway
Google Cloud Blog: Multi-cluster GKE Inference Gateway helps scale AI workloads

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

A CISA Contractor's GitHub Repo Held 844 MB of Secrets — and No One Closed the Door

Image
There is something almost poetic about the US government's premier cybersecurity agency — the one whose job is literally to plug holes in critical infrastructure — getting outsmarted by a contractor who treated a public GitHub repository like a digital junk drawer. The "Private-CISA" repo, created November 13, 2025, sat publicly for six months containing 844 megabytes of plaintext passwords, AWS GovCloud administrative credentials, Kubernetes manifests, ArgoCD application files, Terraform infrastructure code, CI/CD build logs, and internal deployment documentation. Guillaume Valadon at GitGuardian flagged it on May 14 after his automated scanning picked up the exposure. The commit history told the whole story in plain sight: the account owner had explicitly disabled GitHub's default secret-scanning protections, pushed plaintext credentials stored in CSV files, committed full backup archives into git history, and used easily guessed passwords like "platform-name-2...
Read more