The first vibe coding game...
It goes on your tile and the leaderboard, and it is how friends find you, so no two players can share one. Keep the generated name or write your own.
No account. No password. Ever.
The first vibe coding game...
The model or tool doing the work. It goes on your tile for everyone to judge.
Optional, and skippable - you can always paste HTML by hand. With a key you get to prompt your model inside the game.
Optional. It is what the open lobbies list will call you.
Six characters, from whoever opened the lobby.
The model or tool doing the work. It goes on your tile for everyone to judge.
Nothing is scored here, but the sandbox needs to know what to talk to.
Optional, and skippable - you can always paste HTML by hand. With a key you get to prompt your model inside the game.
Optional, and skippable - you can always paste HTML by hand. With a key you get to prompt your model inside the game.
Drop in on a battle in progress. You take no seat, cast no vote and nobody has to make room for you.
Every voter rates every other player on the same four things:
Each criterion is averaged across everyone who rated you, and the four averages are added together. That puts the maximum at 20.00. Averaging first means a player rated by fewer people is not punished for it.
total = avg(requirements) + avg(functionality) + avg(aesthetic) + avg(approach)
A DNF still appears on the board and can still be voted on. It just tends not to do well.
Every finished battle goes on the record. Rank the room four different ways - the fastest learner, the biggest spender, the most wins, the best eye.
The other argument: which model actually wins, across everyone who declared it.
Add a provider key and vibewars asks that provider which models you can actually reach, then offers exactly those when you pick your weapon. Without a key you can still declare any model from the list - it just is not verified.
localStorage and sent only to the provider that
issued them.People who build software with language models, in a room, competitively, on purpose. Not a passive scroll - a lobby of four to six people running the same brief against the same clock, picking a model, arguing about the constraints, watching each other's builds render live. Whoever they reach for when they need something built with an LLM, they already had it open for the length of a battle.
An icon, your app's name, and a one-line description. Five slots total, one column.
Five slots, booked by the calendar month, always for the month ahead. A slot is yours for that whole month and renews only if you want it to, so the board turns over rather than locking newcomers out.
Pick the position you want and send the enquiry. Rates depend on the slot and the length of the booking, so they are agreed directly rather than posted.
Slots are claimed in the open against the repository, so the whole roster is public and auditable.
A party game for people who build things with language models. Everyone gets the same brief and the same clock, so the only variable left is you and whatever you are driving.
node e2e-test.js drives a whole battle with real WebSocket clients and checks
the lifecycle end to end.MIT licensed. Issues and pull requests welcome - the challenge pool in particular is meant to be extended, and adding a topic is just another entry in one array.