InstantDB had Codex, Opus, and Gemini each try to build a multiplayer shooter.
InstantDB had Codex, Opus, and Gemini each try to build a multiplayer shooter.
Each model (Codex Max 5.1, Opus 4.5, Gemini 3 Pro) ran in its provider's CLI on a top-tier plan with default settings. They got about seven consecutive prompts. The first four built a local three.js shooter: map, enemies, gun, sounds. The last three made it multiplayer with Instant presence and topics, then added a database-backed map list. The humans mostly pasted errors back.
All three ended with a working multiplayer 3D shooter and no hand-written code. Opus won the frontend, Gemini the backend, and Codex landed in between. Opus got stuck on React useEffect bugs until the engineers read its code.
Gemini had fewer errors, possibly because it ran the build step repeatedly. Expect to paste errors back, and expect to read code yourself when an agent gets stuck.
Build a simple multiplayer first-person shooter inspired by [Counter-Strike] in the browser using [stack, e.g. JavaScript and a realtime backend]. Include movement, shooting, health, and [number] players in one room. Finished means I can open two browser tabs and play against myself, and you list what's still missing.
Score every demo request against your ICP, update HubSpot and ping the right rep in Slack within a minute of the form submit.
Every new Zendesk ticket gets a category, priority and sentiment tag plus a draft reply in an internal note before an agent opens it.
Copilot and Claude review each PR for bugs, missing tests and risky changes before a human looks, so reviewers can focus on design.