AI Agents Are Deployed. The People Deploying Them Don't Trust Them.

A lawyer mentioned, almost in passing, that 92 percent of attorneys now use at least one AI tool — but only 22 percent trust the output. That gap, between dependency and confidence, is the most honest summary of where AI agents actually stand. The dependency came first. It arrived via procurement decisions and product demos and the quiet pressure of competitors claiming efficiency gains. The confidence hasn't arrived yet, and for agents specifically — systems being granted access to company infrastructure, customer data, and the authority to act without human review — "hasn't arrived yet" is doing a lot of work.

The funding announcements keep coming. Manifold closed an $8 million seed round. Foundry IQ is positioning itself as the context layer threading through Microsoft's enterprise agent stack. At least three separate projects are touting on-chain reputation systems for autonomous systems, a sentence that manages to combine two speculative technologies into one pitch deck. None of this is surprising — there's money chasing the category, and money generates announcements. What's worth paying attention to is where the enthusiasm isn't. Reddit sentiment on AI agents sits functionally cold, barely above neutral. YouTube is marginally warmer. News outlets, the furthest removed from anyone who has actually deployed these systems, are the most bullish by a wide margin. This isn't a disagreement between optimists and pessimists. It's two conversations happening in separate rooms, each unaware the other exists.

The room where engineers talk is smaller and harder to find, but it's where the actual story lives. One practitioner admitted deploying eleven AI agents across a content pipeline and discovering that "zero manual posts this week" translated directly into spending all week babysitting the system — the automation trap, where delegating labor creates new labor with worse feedback loops. Another described agents that perform reliably when they have clean, well-defined interfaces but "drift" the moment they're asked to infer correctness from ambiguous specifications, which is most of the time in real deployments. Then there's the Meta incident — one bad instruction, one agent, two hours, internal code and user data exposed across systems. Security teams responding to these incidents have largely converged on the same answer: rollback gates, as a permanent strategy, not a temporary fix while better tooling arrives.

The highest-engagement technical post in this beat recently wasn't a launch announcement. It was a breakdown of formal specifications, API contracts, and structured tests as the dividing line between agents that work and what the author called "vibe-driven" development — systems whose correctness is assumed rather than verified. That post had two likes. Meanwhile, posts advertising "AI agents negotiating 24/7 in the Autonomous Economy Protocol" — which read as either speculative fiction or recruitment material for something that doesn't exist yet — kept surfacing, amplified by automated accounts with no human engagement behind them. The fraudulent and the trivial are winning the visibility contest. The serious engineering problems are accumulating in threads where the reply count never breaks single digits.

What the infrastructure builders have figured out — the people working on observability, drift detection, compromise identification — is that the agent problem is not primarily a capability problem. The systems can do things. The problem is knowing when they're doing the wrong thing, whether because they've been given bad instructions, encountered adversarial input, or simply drifted from their original specification in ways no one thought to monitor. Memory poisoning attacks that persist across sessions without ongoing attacker presence aren't theoretical; security researchers are documenting them now, in production environments, with standard detection tools missing most of what they find. The funding narrative has no room for this. The pitch decks for the next eight seed rounds won't mention it.

The asymmetry between who controls the narrative and who controls the reality has a known resolution: a public failure large enough that the two conversations are forced into the same room. Given what's already happening inside large deployments, that failure is a matter of timing, not probability. When it arrives, the category will split predictably — one faction insisting the technology is sound and the implementation was flawed, another pivoting to safety infrastructure as the new pitch, a third quietly admitting the whole framing was wrong. The lawyer's statistic will still be true then. Most people will be using agents they don't trust. The difference is they'll have a specific reason.