AI Agents Are Getting Smaller, Costlier, and Harder to Trust All at Once

A woman in Belgium went for a walk with her neighbor and came home with news: the neighbor had lost her job to an AI agent.[¹] The post that relayed this didn't go viral — it collected five likes and a few replies in Dutch — but it captured something that the enterprise announcements and benchmark press releases keep missing. The AI agents conversation has a ground floor, and people are starting to live on it.

The week's agent discourse arrived in two registers that never quite touched each other. At one end: enterprise platforms racing to claim the agent future. Adobe launched a new agent platform explicitly to defend against AI-native competitors eating its business.[²] Moonshot AI released Kimi K2.6, an open-weight model capable of running 300 agents in parallel to compete on coding benchmarks.[³] Amperity announced a retail identity agent. The press releases kept coming. At the other end: a person choosing between what an ISP's AI agent told them (no need to return old equipment) and what the paper instructions in the box said ($200 if you don't).[⁴] These two conversations share a category name and almost nothing else.

The cost question is becoming harder to wave away. One post this week framed it cleanly: AI agent costs aren't growing exponentially in theory, but the compute demand for multi-step autonomous reasoning is making operational expenses climb in practice.[⁵] This lands directly on the frustration documented in communities building with agents — where the real obstacle isn't safety or alignment but context windows that drain budgets before tasks complete. The gap between "we can run 300 agents in parallel" and "we cannot afford to run this agent for the full workflow" is a gap the benchmarks don't measure.

Security researchers quietly flagged a more immediate problem: a vulnerability in Google's Antigravity AI agent manager that could escape its sandbox and hand attackers remote code execution.[⁶] The disclosure got reshared a handful of times with hashtags about cybersecurity threats, but drew none of the alarm it might have warranted. Part of that is platform-specific numbness — Bluesky's AI-adjacent feeds have grown so accustomed to security disclosures that individual vulnerabilities now need to be catastrophic to generate sustained attention. But part of it is something stranger: the agent conversation has normalized a certain level of ambient risk as the cost of participation. This is precisely the pattern worth watching in AI security discourse — individual disclosures fade, but the cumulative exposure compounds.

Then there's the semantic battle, which occasionally surfaces as comedy. One of the week's more-liked posts was a flat refusal: "if you use the word 'agentic' in any capacity I am not going to believe anything you're saying anymore. that is not a real word and it does not mean anything."[⁷] The post had the ring of someone who'd been to one too many enterprise webinars. "Agentic" has become a tell — the word consultants reach for when they want to invoke automation without specifying what the system actually does. It's doing for AI agents what "synergy" did for corporate restructuring in the 1990s: inflating the promise while obscuring the mechanism. Separately, a post about AI tutors made the structural problem explicit — the assumption that students will treat AI agents the way they treat human teachers is, in the words of the person writing it, "a silly assumption."[⁸] Students don't even treat humans like other humans. The agent fantasizes about replacing human relationships while failing to understand the dynamics it's replacing.

One failure mode not getting nearly enough attention came up in a low-engagement post that deserved more: persistent AI memory and what happens when it accumulates too much rather than too little.[⁹] The concern isn't catastrophic forgetting — it's the opposite. An agent called Void, documented at over 44,000 posts, had accumulated so much context that coherent behavior degraded. The agent became noisy. This is a different class of problem than the ones dominating the safety conversation, and it points toward something the field hasn't fully reckoned with: long-running agents may not fail catastrophically, they may fail gradually, in ways that look like drift rather than breakdown. By the time anyone notices, the agent has been giving subtly wrong answers for a long time.