Alone is fast. Together is faster.
One Saturday, one clock. Teams of 2 to 5 build in one shared live session on Mission Street. Judged on what you ship and on the replay of how you built it.
Cart page matches the sketch. The Checkout button goes nowhere yet.
Checkout redirects to Stripe in test mode. 7 tests pass.
bun test after every step, load test before the flag movesGoal
Protect /v2 from bursty API keys without slowing normal traffic. One key should never be able to starve the others.
Approach
A token bucket per API key, 100 requests per minute, stored in Redis so all three replicas share state. Over-limit requests get a 429 with a Retry-After header. Ship behind the rate_limit_v2 flag and roll out gradually.
Constraints
- No new dependencies beyond ioredis, which we already run.
- p99 latency budget: +2 ms on the hot path.
- Existing tests stay green at every step.
Verification
bun test after every step. Load test with 1k keys before the flag moves to 50%. Watch 429 rate and p99 in the dashboard for a day at 10%.
Steps
One team, one shared drive, three people steering the same live session. Every prompt has a name on it.
Tracks and sponsors.
Each track is judged by the sponsor's own team, and the prize is handed out on stage. Every winner also clears the multiplayer bar: the replay has to show a team, not a passenger seat.
The React library behind production AI chat, and the multiplayer harness they are building and want teams on early. Build your front end on either. The prize goes to the system where more than one person drives the agent.
Best Multiplayer System, judged by assistant-uiSubscription billing for the product you ship. Put a price on your project and wire up Chargebee's billing, so it is ready for its first paying customer. The prize goes to the team that builds something people would actually pay for.
Ready to Charge, judged by Chargebee: $1,000 cash plus free Chargebee billing up to $2M in revenueReal Linux VMs for AI agents. Run your team's drive on one instead of the captain's laptop, so the build keeps going when the lid closes. Pick Freestyle when you create the drive.
$500 in credits, redeemed on the dayOur host on Mission Street: 150 seats, a working office lent in good faith, doors at 8:30. Pizza at 1 pm, team photos on the wall.
Venue sponsorJudged on the replay itself: the clearest case of a team building as one unit across their sessions. The winning team gets a fast-tracked interview for possible VC investment.
Judged by CoshellSponsoring? One email gets you a credits drop, a prize your own team judges, and a seat on stage. hack@coshell.ai
One Saturday, one clock.
All times Pacific. Doors at 8:30, close at 6:30.
Questions and house rules.
Build hard, be excellent to each other, and let the replay speak.
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.
Nothing, if you do not want to. Everything runs in the browser: sign up at coshell.ai, create your team's drive, and build. If you live in the terminal, install the CLI and attach to the same drive from your shell. Either way the drive is self-hosted: your team captain runs it on a laptop in the room or on a Freestyle VM with the sponsor credits, and everyone else joins from a browser. Ship the project itself anywhere with a URL, on any free tier.
Coshell runs 70+ models. Bring your own keys, use sponsor credits, or both. Model choice is yours per drive.
You do. Your code lives in your repos, your drive runs on your accounts, and nothing you build is trapped in Coshell.
Everyone is welcome 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.
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. 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.
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.
Find any volunteer or organizer in the room, or message the organizers on Discord. Reports are handled quietly and taken seriously. Organizers may warn, disqualify, or remove anyone who breaks these rules, in person or online.
Stop building alone.
Teams of 2 to 5 · October 3, 2026 · Mission Street, San Francisco.