AI Psychosis: Why Companies Are Wasting Millions on Meaningless AI Workflows in 2026

What Happened: The Essay That Went Viral

On May 16, 2026, Mitchell Hashimoto — the creator of Terraform and co-founder of HashiCorp — published a blog post that detonated across the tech industry. Titled "I believe there are entire companies right now under AI psychosis," the essay racked up over 1,500 points on Hacker News and generated 800+ comments in hours. His argument was deceptively simple: companies are building meaningless AI workflows because they're terrified of being left behind, not because the workflows solve real problems.

Hashimoto's core analogy struck a nerve. He compared AI to having an infinite number of interns — incredibly valuable if you know exactly what to delegate, but actively dangerous if you don't. The more capable AI becomes, he argued, the wider the gap grows between people who use it with clear intent and those who throw tasks at it hoping something sticks.

This isn't just a hot take from a tech luminary. It's a warning that anyone using AI tools — from solo developers to enterprise teams — needs to hear. And it maps directly onto patterns we see every day in the AI tool directory here at aitrove.ai.

What Is "AI Psychosis"?

Hashimoto defines AI psychosis as a organizational state where companies adopt AI tools reflexively rather than deliberately. The symptoms are recognizable:

💡 Key Insight: Hashimoto argues that as AI gets more capable, "AI will only amplify the gap between those who know what they want and those who don't." The tools aren't the problem. The lack of clear objectives is.

The timing of this essay is significant. It comes just days after a report that Amazon workers, pressured to increase their AI usage metrics, were literally inventing fake tasks to justify using AI tools. That's AI psychosis in its purest form: employees gaming a system designed to measure the wrong thing.

Meaningful vs. Meaningless AI Usage

Not all AI adoption is created equal. Here's the distinction Hashimoto draws — and one that's critical for anyone browsing AI tools on our platform:

✅ Meaningful AI Usage

  • Using AI coding assistants to handle boilerplate while you focus on architecture
  • Deploying AI agents to monitor production logs and alert on anomalies
  • Using AI to generate test cases for well-defined specifications
  • Automating document processing with clear input/output requirements

❌ Meaningless AI Usage

  • Forcing every team to "use AI somehow" with no clear problem to solve
  • Building AI chatbots for internal docs nobody reads
  • Using AI to write emails that AI then summarizes for someone else
  • Creating "AI-powered" features that are just API calls with extra steps

The pattern is clear: meaningful AI usage starts with a well-defined problem and applies AI as the most efficient solution. Meaningless usage starts with "we should use AI" and then goes looking for problems to justify it.

The Productivity Theater Epidemic

Hashimoto's essay tapped into a frustration that's been brewing across the tech industry. Microsoft's 2026 Global AI Diffusion Report found that 17.8% of the world's working-age population now uses AI — but that adoption metric tells us nothing about whether the usage is productive. Frontier firms use 3.5x more AI per employee than average, according to OpenAI's B2B Signals report, but the gap between "using AI" and "benefiting from AI" is enormous.

The productivity theater manifests in ways that are easy to spot once you know what to look for:

The common thread: these organizations are optimizing for the appearance of AI adoption rather than the substance of AI-driven improvement.

The Right Way to Use AI Tools in 2026

So what does Hashimoto recommend? His advice, echoed by experienced AI practitioners across the industry, boils down to a few principles:

1. Start with the Problem, Not the Tool

Before choosing any AI tool, articulate the specific problem you're solving. "We need to respond to customer support tickets faster" is a problem. "We need to use more AI in customer support" is not. The former leads you to the right tool; the latter leads to AI psychosis.

2. Measure Outcomes, Not Usage

Track whether your AI tools are making work better, not just more frequent. If you're using an AI code assistant, measure bug rates, code review turnaround, and developer satisfaction — not lines of AI-generated code.

3. Know What You Want Before You Delegate

This is Hashimoto's central point. AI is like infinite interns — they're only useful if you can give them clear, specific instructions. If you can't articulate what you want, no AI tool will figure it out for you. Spend time understanding your own requirements before shopping for tools.

4. One Good Tool Beats Ten Mediocre Integrations

The best AI setups we see from users on aitrove.ai aren't the ones using twenty tools. They're the ones who picked two or three tools that genuinely fit their workflow and learned to use them deeply. A developer who's expert at Cursor will outperform someone juggling five AI coding tools they barely understand.

Which AI Tools Actually Move the Needle?

Based on the patterns we see across 300+ AI tools on aitrove.ai, the tools that deliver genuine productivity gains share a few characteristics:

Key Takeaways for AI Tool Users

Hashimoto's "AI psychosis" concept is a wake-up call for anyone evaluating, purchasing, or deploying AI tools. Here's what to remember:

The AI tool landscape in 2026 is genuinely incredible — there are tools for coding, writing, design, research, and automation that would have seemed impossible two years ago. But the tools are only as good as the humans directing them. As Hashimoto put it: the gap isn't between companies that use AI and companies that don't. It's between companies that know what they want and companies that don't.

Find the Right AI Tools for the Right Problems

Explore 300+ AI tools on aitrove.ai — filter by use case, compare features, and choose tools that solve your actual problems.

Browse All Tools →