Games made with AI: how they come to exist
Many of the games in this directory were made by people who prompted an AI assistant instead of writing every line of code by hand. The practice has a name, vibe coding, and it has produced a wave of small browser games. This guide explains where the term comes from, how such games are put together, what they feel like to play and how to size one up in two minutes.
Where the term comes from
The phrase "vibe coding" was popularized by Andrej Karpathy in February 2025. In his description, you tell a coding assistant what you want, accept what it writes and keep iterating, without reading all of the code line by line.
The idea caught on quickly in the game community, because a game is an ideal first project: results appear on screen immediately, and you know at once whether the idea works. SpaceRunner's own page calls the game a vibe coded space game by a non-coder, and Dank Duel's page title calls it a vibe coded meme themed fighting game.
From prompt to playable page
The recipe is simple to describe. Someone writes what they want in plain language, the assistant produces code, the person tests it and asks for changes, and the loop repeats until the game feels right. Some authors say how they did it: the listing for MANY ROADS says it was built with Claude Code in 10 days, and WordTwiq's says it was made with GPT 6 Astra in Codex. The loop is the whole method, and it explains why a first playable version can appear so quickly.
Hosting is usually cheap. The addresses in the directory show many games on free-tier platforms: Vercel (Rock Water Skipping, Websailing), Netlify (SpaceRunner) and Render (Meshbreakers). Web graphics libraries do the 3D work, and Three.js is named for The Agency and SnowGlider.
Jams give the movement a calendar. Dank Duel says it was built for Vibe Jam 2025, and Flight Simulator 2025 is listed under the handle @levelsio. We know nothing more about those events than that.
What it means for the player
The strength of this approach is speed. One person can try an odd idea in a weekend, such as a game about skipping rocks, one about drawing countries from memory or a shadow puzzle, that a studio would never greenlight. That is why the directory holds such a wide range of premises.
The same speed explains the rough edges. Expect games that are quick to start, with no installer and often no account, but whose polish varies from one project to the next.
The limits to expect
Quality is uneven. Bugs happen, balance can be off and a game may stop short of a finished feel; MANY ROADS calls itself an alpha demo. Multiplayer games depend on a server, and a server run by one person can disappear or sit empty. Some pages carry ads, and mobile support is not always carefully tuned.
Maintenance is the biggest unknown. A game built in a few days may not be updated for months, and free hosting plans can change. That is a reason to check the page before you recommend a game to a friend.
How to judge one in two minutes
Start with loading time: a good small game opens fast. Then see whether the controls are explained, either on screen or in a short tutorial. Play until you reach a game over screen, and check that the game lets you restart cleanly. If you plan to play on a phone, open it on the phone, since desktop-only games are not always labeled.
For a multiplayer game, look for other players, since an empty lobby is useful information. Finally, see whether the page tells you who made it and where to follow updates. If most of these checks pass, the game is probably worth your next ten minutes, and if several fail, you have lost very little.