Live Experiment · May 2026

My First Experiment with Unity AI

A live session where Shahar built a 2D game using Unity AI Assistant, Claude Code, and Rider — testing which tool wins.

Main Points & Conclusions

  • 1

    An informal live experiment — Shahar explored Unity AI Assistant in real time with viewers, no fixed plan

  • 2

    Setup required opening Unity 6, Rider, Warp terminal, and Gemini in parallel; Unity AI signup asked for billing details

  • 3

    Game concept chosen with viewers: a 2D magnet/planet puzzle game (hyper-casual) using Kenney assets

  • 4

    Dual-tool strategy: Claude (via Rider/Claude Code) for architecture and code, Unity AI Assistant for scene/hierarchy

  • 5

    Unity AI Assistant was very slow and required frequent manual confirmations for every action (file saves, screen captures)

  • 6

    Unity AI wrote low-quality code: OnTriggerEnter with CompareTag, no namespaces, poor performance patterns

  • 7

    Claude produced better code and managed git; MCP for Unity was installed via Claude Code — one line in package.json

  • 8

    Main conclusion: Unity AI Assistant is disappointing — useful only for minor tasks, not autonomous scene building

  • 9

    Better stack for Unity AI dev: Claude Code + Rider + Warp; Gemini and Codex also show strong code architecture

  • 10

    End result: a basic, partially working game (magnetic ball, planets, levels) — unpolished. Blog post planned.

Summary with Timestamps

0:00

Opening — informal experiment intro, blog post planned

0:54

Viewer poll: 2D or 3D? → 2D chosen

1:35

First opening of Unity AI Assistant

2:37

Gemini brainstorm: 10 hyper-casual 2D puzzle ideas

5:10

Unity AI Assistant package install + service signup

12:49

Dual-tool strategy explained: Claude + Unity AI

17:20

Unity opens; Rider set as script editor

21:03

Warp terminal intro — managing multiple agents

22:31

Project pushed to git, Unity AI connected

24:14

Unity AI starts coding — constant approval prompts begin

29:54

First frustration expressed: too slow, poor UX

38:32

Key question: why use Unity AI if Claude does it better?

50:30

MCP for Unity demo — one-line install via Claude Code

53:12

Unity AI installs MCP but scene won't run

1:02:29

Switching to domain-based commits; CLAUDE.md initialized

1:04:50

Play mode enabled manually — game partially works

1:10:04

Level layout looks reasonable; object scales corrected

1:12:02

Key insight: Claude + custom MCP would have been better

1:19:15

Final verdict: Unity AI writes code but can't test/run scenes autonomously

1:25:46

Unity AI succeeds with very precise instructions — but that's not practical

1:28:33

Session end — disappointment expressed, blog post planned

Q&A from the Session

Want to Learn Game Dev with AI?

Vibe Coding 101 teaches you to build Unity games with AI — from zero to a finished product, using the Director vs. Typist method.

Learn About the Course →