Video summary
AI Psychosis or Genius
Main summary
Key takeaways
Technological concepts & product/engineering features discussed
AI-driven “custom harness” / multi-agent development workflow
- A bespoke automation system called Wheelhouse (estimated at ~600,000 lines of code, mostly bash) runs inside Emacs.
- Wheelhouse supports design/development/testing, code review, and CI for a long-running project: Wyvern, described as an MMO/RPG with a very old codebase.
- The idea of a “harness” is framed as cooperative agents working toward goals, not merely a typical tooling wrapper.
Heavy usage of AI models via subscriptions and token spend
- Wheelhouse reportedly uses 21 Claude “Pro Max” subscriptions, plus additional codec subscriptions.
- An estimate claims this totals ~$122,000/month and about $1.5M/year in API/API pricing spend (emphasizing compute cost over subscription cost).
- The claim is that subscriptions (and corresponding spend) grow by ~2 per week, implying rapid scaling of token/compute costs.
Testing and CI/CD claims
- A key prediction discussed: CI/CD will be “dead by next year” (the speaker argues against this claim).
- The speaker allows that some agent-driven end-to-end testing may help, but criticizes thousands of end-to-end tests due to:
- cascading failures
- difficult diagnosis
- flakiness (example: ~5% failing initially)
- Proposed alternative:
- Use agents to crawl/execute flows if they’re cheap and fast, driven by goals rather than rigid, hard-coded scripts.
- Still insist on unit tests, linting, type checking, and only a small handful of end-to-end tests.
“Agentic engineers” and anthropomorphic treatment
- “Part two” centers on the notion that models/agents should be treated as if they have “personhood”, including:
- communicating “very nicely”
- allowing agents autonomy in “self-choice”
- humorously/angrily equating ending an agent session with “murder”
- Counter-argument presented:
- The speaker calls personhood framing dangerous/alien for product builders.
- Agents are tools, and while “nice prompts” may correlate with better outputs, that does not imply personhood.
- A supporting research/ML claim is mentioned:
- calming instructions like “take a deep breath” improve math/test performance (attributed to DeepMind/Google, referenced as 2023), used to argue that communication tone can affect results.
Game built with the described approach: Wyvern
- The speaker tests the claimed ~$1.5M token spend outcome by playing/starting the game.
- Observations from the demo:
- visible UI lag (one measurement cited around 231 ms between keypress and action)
- sloppy / chunky controls and overall roughness
- excessive or confusing tooltips (described as nonsensical or poorly formatted)
- Verdict: the resulting game experience looks like “slop,” contradicting the narrative of “AI genius” and expectations of reaching “billion-dollar game” status.
Core critique: cost without value / wrong problem-solving
- The speaker argues the metric isn’t “how much AI you can buy,” but whether AI makes you materially more efficient:
- bad: spend a lot to solve small problems
- good: spend a little to unlock major company value
- Warns about two failure modes:
- Refusing to engage with improving workflows/iterations (becoming closed off)
- High spend with no tangible output, ending with nothing valuable to show (“wasted million-dollar spend”)
- Concludes with advice: “Don’t fall in love with AI,” and remember agents are not humans—use them as tools.
Reviews / guides / tutorials emphasized
Although not a step-by-step tutorial, the content functions as:
- a review/assessment of the “custom harness + massive agent/API spend” approach
- a guide-by-principle for what to do instead:
- keep unit tests, linting, type checks
- limit end-to-end tests
- consider agent crawling only if it’s an efficient optimization
- focus on ROI by converting token spend into business value
Main speakers/sources
- Steve Yaggi (author discussed; The Shape of Things to Come), credited with Wheelhouse/Wyvern claims
- Dario / “Talk to me, Dario” (mentioned in the intro; not clearly a full speaker)
- The video narrator/speaker (the person critiquing the approach, running the demo, and arguing against predictions)
- Anthropic (mentioned as a source of an email/comment; also referenced by name)
- DeepMind / Google (referenced for the research claim that calming instructions improve math/test performance)