AI Office Agents Are Starting to Look Less Like Chatbots and More Like Interns With App Permissions

The interesting thing about AI this week is not that another model got a little smarter or another company found a more theatrical benchmark chart. It is that the software is being taught to do office work across actual applications instead of just talking about it in a chat window. The Verge reported that Anthropic’s Claude Cowork now connects with tools like Google Workspace, Docusign, and WordPress, and can handle multi-step work across Excel and PowerPoint. That is a very different category of product from the original chatbot pitch. A chatbot gives you answers. An office agent gets permissions, touches systems, moves context between apps, and starts behaving a lot more like an intern who is surprisingly fast but still capable of setting the building on fire if unsupervised. That, for me, is the real shift. The value is more concrete, because useful work inside companies usually lives in ugly sequences of small tasks: update the deck, clean the spreadsheet, pull the document, route the signature, publish the thing, try not to ruin compliance. But the risk is more concrete too, because once the model is acting instead of merely replying, mistakes stop being decorative.

Anthropic’s own announcements around Claude Opus 4.6 lean into the same direction: stronger tool use, better multi-step reasoning, better performance on the sort of work that looks suspiciously like somebody’s Tuesday. And The Verge’s broader AI coverage makes it pretty clear this is where the industry is heading in general. Everybody wants the model to stop being a clever answer machine and start becoming a delegated worker. I get the appeal. Most office labor is not genius-level analysis; it is context switching with a side of clerical despair. If AI can remove some of that, great. But this is also where the hype gets dangerously tidy. Companies love to talk about automation as if the hard part were getting a model to click the right buttons. The hard part is actually governance: who approves what, what systems the agent can touch, how errors are caught, how audit trails work, and how much chaos a confident machine can create before a human notices. My mildly grumpy view is that the next serious AI winners will not be the tools that feel the most magical in a demo. They will be the ones that make delegation safe, reversible, and painfully boring. Which is not sexy, but neither is recovering from an AI that helpfully sent the wrong document to the wrong person at machine speed.

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

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