the multiplayer
coding hackathon
Alone is fast. Together is faster. Build together.
registration opens on luma soon · 70 seats in the room, the internet is uncapped
agent: created server/routes/booking.ts, 4 files changed
ada@lagos > take the payment branch from here, stripe test mode
agent: wired checkout session, tests passing (7/7)
sam@london > polish the landing copy while they finish, then deploy
agent: deployed preview · 47 min to submissions
mika@sf >
one team, could be in three time zones, building in the same live session
how it works
no setup morning. just build.
In the room at Convex SF, or from anywhere on earth. Same day, same clock, same judging.
Form your team
2 to 5 people. Come with a team, or find one at the morning team-formation session.
Build in one drive
Your whole team works in one shared drive, steering live agent sessions together. Run one or run five in parallel.
Ship + show the replay
Submit the deployed project, the repo, and your session replay. The replay is the receipt.
tracks + sponsors
the sticker sheet
Each track is judged by the sponsor's own team, prize handed out on stage. Every winner also clears the multiplayer bar: the replay has to show a team, not a passenger seat.
Convex
The backend your team does not have to babysit. Codes for every team that picks the track.
→ credits + prize, judged by convexRender
Run your team's drive on Render, ship your project on Render. Best build takes the track.
→ credits + prize, judged by renderNorthflank
The runtime platform for AI-native companies, at its first hackathon. Make it count.
→ credits + prize, judged by northflankThe fridge
In-room teams run on it all day, and 1 pm is official Olipop + pizza hour: mid-build photos, can in hand. Remote teams: the internet does not carry cold soda yet.
→ no judging, just vibes + the photo wallBest Built Together
Judged on the replay itself: the clearest case of a team building as one unit across their sessions, wherever on earth they sat.
→ judged by convex + coshell+ your sticker here
Sponsoring? One email: a credits drop, a prize your team judges, a seat on stage.
one saturday, one clock
schedule (all times pacific)
Your submission includes the session replay, so judges scroll through exactly how your team built. Who prompted what, when, and how the plan evolved. A brilliant demo built by one person while four watched does not win anything at this event, in the room or on the internet.
before you register
your questions
your questions
Does it cost anything?
No. Coshell drives are free to self-host, sponsors cover the credits, and the pizza is on us. You bring a team and a laptop.
What do we need installed?
Nothing, if you do not want to. Everything runs in the browser: sign up at coshell.ai, create your team's drive, build. If you live in the terminal, install the CLI with curl -fsSL https://coshell.ai/install | bash (on Windows, via WSL) and attach to the same drive from your shell. Either way the drive itself is self-hosted: a laptop works, and so does a one-click deploy on Render or Northflank using the credits sponsors bring.
Can our team be partly remote?
Yes, and it is the best flex at this event. A team registers once and members join the same drive from wherever they are. Only the people physically coming need an SF seat.
What about timezones?
One clock for everyone: build runs 10:30 am to 6 pm Pacific. That is evening in Europe and very late in Asia. We know. The most-timezones award exists precisely to honor your sacrifice.
Which AI models can we use?
Coshell supports 70+ models. Bring your own keys, use sponsor credits, or both. Model choice is yours per drive.
Who owns what we build?
You do. Your code lives in your repos, your drive runs on your accounts, and nothing you build is trapped in Coshell.
How do you stop one person doing all the work?
We do not have to. Every prompt in the replay has a name on it, and judges read the replay. Teams that build together win. That is the entire event.
house rules
Build hard, be excellent to each other, and let the replay speak. These apply everywhere the event happens: the room, the Discord, the stream, and inside every shared session.
Be excellent to each other
Everyone is welcome here regardless of who they are, where they are from, or how long they have been writing software. Harassment, discrimination, hate speech, sexualized content, and personal attacks have no place at this event, online or in the room. Neither does heckling demos. Cheer instead.
Respect the shared spaces
The venue is a working office lent to us in good faith: treat it better than you found it. In Discord and in sessions, keep it constructive. Spam, self-promotion outside the showcase channel, and drive-by negativity get one warning.
Play the game straight
Work happens inside the event window, by the people on your roster, in your team's own drive with your own accounts and keys. The replay is the audit trail and judges read it. Pre-built projects, ghost contributors, and replay tampering disqualify the team. Open source libraries, templates, and your agents doing the heavy lifting are all fair game. That is the point.
Respect people's content
Photos and clips happen all day, in the room and from the photo wall. Registration includes consent for event photography; if you need to be off camera, tell a volunteer at check-in and we will make it work. Do not record or share someone else's session without asking them.
If something is wrong, say so
Find any volunteer or organizer in the room, or message the organizers directly on Discord. Reports are handled quietly and taken seriously. Organizers may warn, disqualify, or remove anyone who breaks these rules, in person or online, with no refund of the nothing you paid.