Developer Reports a Claude Code and Unity 6 Autonomous Workflow
In a five-week experiment, an anonymous game developer used Claude Code with Opus 5.5 and Unity 6 to write most C# code, inspect and modify scenes, capture screenshots, and run gameplay checks through MCP. The workflow also combined Tripo AI and SmartMesh P2 for image-to-3D assets, Blender and MCP for model cleanup, separate Claude sessions for design, programming, and art, and task cards for automated implementation and validation. The developer said prototyping that previously took days or weeks could take roughly a day, while creative direction and repeated playtesting remained hands-on; these efficiency claims are self-reported.
The report provides a concrete example of combining coding agents, editor control, 3D asset tools, and external checks within an unattended game-development loop, while showing that human creative decisions and playtesting remained central.
| The game revolves around driving machinery into dense fields, clearing crops and spending the earnings on upgrades and new land. A relaxed, deliberately unrealistic farming game focused on satisfying harvesting and increasingly oversized equipment. The stack The automated part Plans, design ideas and playtesting feedback became a backlog of task cards. Dedicated Claude sessions handled design, programming and art, each with separate instructions and a Git branch. A runner script picked up one card at a time, assigned a time and spending limit, and kept development moving while unattended — including overnight. Completed tasks went through checks outside the agent’s own assessment: building the game headlessly, running tests, driving the tractor to check handling and capturing screenshots. Changes were merged only after passing those checks. Failed tasks waited for manual review. Morning reviews turned the results into another round of feedback and new task cards, creating a repeatable cycle of implementation, testing and refinement. Prototyping that previously took days or weeks could now happen in roughly a day. The starting point was a rough playable version, followed by iteration on the core gameplay loop, controls and camera. Creative direction remained hands-on. Harvesting mechanics, crops, vehicle movement, machinery design and environment layouts still required repeated playtesting and adjustments. submitted by /u/Delicious-Shower8401 [link] [comments] |
#Claude Code#Opus 5.5#Unity 6#Tripo AI#SmartMesh P2#Blender#Model Context Protocol