From a short brief to a verified, playable game
GameCrew is an autonomous AI game studio that turns plain-English direction into real engine projects, custom 3D art and sound, and browser-playable builds — for desktop, phone touch and WebXR VR — verified by automated playtests before you open them.
Four stages, each grounded in real tools
- 1. Pitch, look & gameplay directionWrite a few sentences. Within two minutes, GameCrew drafts a structured pitch, offers visual moodboards and distinct gameplay takes, maps desktop, gamepad, mobile touch and optional VR controls, and draws coherent concept art.
- 2. 3D models, rigging & mastered audioGameCrew searches open-licence libraries (Poly Haven, Kenney, AmbientCG) first, generates bespoke 3D characters and props where needed, rigs humanoid animations, builds PBR materials, and masters sound effects and looping music.
- 3. Automated playtest & browser verificationEvery version compiles in its engine, runs automated edit-mode and play-mode tests that simulate gameplay, boots its web build in headless Chrome, checks console logs and WebXR VR sessions, and captures multi-angle screenshots.
- 4. Share links, live tuning & full exportEvery verified version gets an instant desktop, mobile and VR browser link. Pin feedback directly onto screenshots, tune gameplay numbers in seconds, connect an MCP assistant, or download the full project source.
Four real engines — pick yours or let the pitch recommend
Rich 3D worlds, stylized lighting & desktop exports
Universal Render Pipeline projects with C# gameplay scripts, physics, rigged humanoid FBX animation, custom shaders, downloadable Unity 6 project archives, standalone desktop players, WebGL builds and WebXR headset play.
Open-source 2D/3D scenes & browser VR
Clean .tscn scene trees and GDScript gameplay on the MIT-licensed Godot 4 engine, with fast headless verification, WebXR headset support, HTML5 web exports and zero engine licensing friction.
Fast browser-first 3D & instant WebXR VR
TypeScript 3D web games with three-mesh-bvh triangle-mesh physics, WebP/meshopt-compressed glTF models, responsive phone touch controls and WebXR headset play.
Deterministic TypeScript web engine
GameCrew’s compact deterministic TypeScript engine with declarative JSONC areas and witnessed gameplay scenarios that verify in under a second and boot instantly on phones and desktops.
See the side-by-side Unity 6 vs Godot 4 vs Three.js vs Pulse & WebXR comparison matrix →
Iterating after v1: screenshot notes, live tuning & MCP
Every change produces a new numbered, verified version (v2, v3, …) while preserving earlier builds so you can compare any two versions side by side. You can direct changes in three ways:
- Screenshot & in-game pinned notes: click any preview screenshot — or press
F8while playing a build — to pin notes directly onto specific objects, UI elements or camera moments, then send the batch as one build request. - Zero-cost live tuning sliders: numeric gameplay constants exposed in
tuning.json(speed, gravity, spawn rates, difficulty) update live via sliders in seconds without waiting for a full rebuild. - MCP coding assistants: connect Claude Code, Cursor or VS Code over the Model Context Protocol to inspect files, trigger 3D & audio asset tools or run sandboxed engine verification from your own editor.
Why automated verification matters
Code generation alone leaves broken scenes, silent runtime exceptions, or unplayable camera angles. Before GameCrew marks any version ready, the studio compiles the project, runs scene-graph transform checks, executes automated play-mode tests against the live scene, boots the exported web build in headless Chrome (and an emulated WebXR headset for VR games), verifies zero uncaught errors, and checks multi-angle contact sheets so broken builds are fixed before they reach you.
Your code, your assets, your game
Games you make on GameCrew belong to you (see terms and trust and data). Download any version’s full project folder and web build at any time, or publish them anywhere.
Questions about the pipeline
How do you update or tune a game after the first version is built?
You can describe changes in plain English, pin feedback notes directly onto screenshots or inside a running shared game, adjust live gameplay tuning sliders at zero AI cost, compare screenshots across versions side by side, or roll back to any earlier git-tagged version.
Can I connect Claude Code, Cursor, or another MCP assistant to GameCrew?
Yes. Creators can generate a scoped access token on the studio Usage page and connect any MCP-compatible coding assistant to inspect the project map, edit scripts and scenes, look up offline engine APIs, and run sandboxed engine verification.
Where do GameCrew’s 3D models, textures, and audio come from?
GameCrew generates bespoke concept art, 3D meshes, humanoid rigs and animation clips, seamless PBR normal and roughness maps, sound effects, and looping music, alongside a curated CC0 and CC BY open-licence asset library that automatically tracks creator attribution credits.
What happens when a build hits a compile error or fails a gameplay test?
GameCrew’s verification harness captures exact compiler diagnostics, scene transform issues, failed playtest assertions, and headless browser errors, feeding them back to the build agents so broken code or unplayable cameras are fixed before you see the version.
Read the Breakline Unity 6 build log — real timings, test counts, and browser boot metrics from three typed words to v3.
Ready to try GameCrew?
Draft a free game pitch in two minutes or join the alpha waitlist.