Convex's avatar
Convex
3 months ago

Inside the Y Combinator Browser Use Agents Hackathon with Convex

A woman on the internet once said she'd rather go through 36 hours of labor than move apartments again. One team at the Y Combinator Browser Use Web Agents Hackathon built their whole weekend around that line. It's as good a starting point as any for what happened in San Francisco: a room full of developers pointing AI agents at the parts of life that are technically solvable but nobody wants to do.

We sent our DX engineer Micky (RasMic) to the hackathon, hosted by the Browser Use team (founders Gregor Žunič and Magnus Müller, with founding engineer Reagan Hsu). The brief was simple. Hand people Convex, Claude, Codex, and a browser-automation library, then see what they build. What came back wasn't a tidy list of demos. It was a room full of people who'd all landed on the same infrastructure decision, independently, for the same reason. They didn't have time to think about their backend, so they picked the one that meant they didn't have to.

The moving problem

The team building around that "36 hours of labor" line had a real, specific complaint. Moving is miserable, and most of the misery is coordination overhead: contacting movers, chasing quotes, tracking who said what. Their pitch was to let AI agents do that coordination instead of a person.

The architecture was OpenClaw writing to a Convex database. That database held the contacts and interactions across every small exchange the agents had to track: movers, listings, logistics, all of it. As one team member put it, "we need to be able to store the contacts of all these different small interactions between all the agents that we have." The real-time piece mattered too. Most competing teams weren't building with anything reactive, and that's the kind of default advantage a synchronized backend hands you when you're not the one building the sync layer by hand.

Winning by not thinking about the backend

The line that came up more than any other, from multiple teams independently, was about setup time. One repeat YC hackathon winner (his team took first place overall at a previous YC hackathon in August) put it plainly: "the way you guys set up a front end with the Convex API and database already set up for you is amazing, and that makes it so that you can spin up a hackathon project or a side project in literally five seconds."

That's not a small thing at a 24-hour hackathon. The honest allocation of your time there is closer to "twenty hours of building and four of arguing about whether Claude or Codex should own the harder parts of the stack" than to any leisurely architecture review. One developer's framing of that debate stuck: "Claude is your adventurer. Codex is your reliable companion. He's the one that's actually going to build the infra architecture, make sure it's reliable and elegant." Their team used both. Claude for the unknown parts of the problem, Codex for making the known parts solid. That's a more specific answer than "we used AI," and probably a better one than picking a single tool.

Another developer went further. The win itself, he said, came out of a hackathon loop: he'd won first place at an earlier YC hackathon using Convex, and the project was good enough that it turned into his job. "I got my Convex job because I won a hackathon. I used Convex fully. And they liked the project, so maybe if you're looking for a job, a hackathon's the way to do it."

Finding a place to live for free

A second team built a tool that stores your email addresses across sites, then searches for housing based on your actual budget. The demo line was blunt: tell it you don't have a place to move and your budget is zero dollars, and it will still tell you the best corner to live on. It's a joke. It's also a real demonstration of what agentic search is supposed to be good at: working an underspecified, unpleasant constraint problem a person would otherwise do by hand across a dozen open tabs.

What's worth noting about that team's build isn't the app, it's how little of it was hand-written. "Three prompts," one of them said. Their teammate, self-described as "not even a coder" and a civil engineer by training, had a working app anyway. The team's workflow skipped typing code in favor of talking to a coding agent through Whisper and letting it write. Whether or not that's the future of software, it's clearly workable enough to win a demo slot at a YC hackathon in 2026.

Automated meeting prep, and a naming problem

Not every idea at the hackathon was about moving or housing. One recurring pattern showed up across several unrelated conversations: using an AI agent to do the unglamorous research you'd do before a meeting anyway, if you had time. "Before a meeting you want to research who the person is, but you never do it because of time, so you prompt an AI: every day at 6am ping me on Slack my schedule with server context."

There was also a smaller, funnier thread running through the day. Several people separately observed that nobody has settled on a name for this category of software yet: agents, agentic apps, web agents, take your pick. Not knowing what to call the thing they were building didn't stop nine teams from demoing it in front of a judging panel by evening.

The winning demo

The first-place team came from a place most hackathon origin stories don't. Not "we saw a market gap," but "we were both really interested in the data space" and a few days spent asking what the next frontier for agents actually was. The idea that stuck: agents playing against agents. It drew loosely on the generative agents research going back over a decade, applied to the browser instead of a simulated town. "At first I thought we're just trying to win this, but then I started thinking it might be crazy enough to win," one of the builders said. That's a more honest description of how good hackathon ideas arrive than most retrospectives admit.

Their account of using Convex under time pressure was specific rather than promotional. One team member, previously an AWS user who'd also worked with Supabase, called Convex "unbelievably fast" to get running. He credited it working smoothly with Claude Code for speeding up the build, and said the team liked it enough that they blew through the free tier and had to ask for more. That's a real constraint hitting a real product decision, not a talking point.

The team had pitched the idea to Lucas from Anthropic beforehand, who told them it sounded good but was "a research rabbit hole" and that they probably shouldn't attempt it in the time they had. They built it anyway, and it won.

What the room actually agreed on

Strip away the specific apps and there's a pattern underneath all of them. Nobody at this vibe-coding hackathon spent their limited hours deciding how to store data, wire up real-time updates, or provision a database. They spent it on the part of the problem that was actually new: coordinating agents, parsing browser state, deciding what a web agent should be allowed to do on your behalf. The backend question was answered before the clock started. That's the real argument for why a database that gets out of the way matters more at a hackathon than almost anywhere else: the honest cost of infrastructure isn't what it does wrong, it's the hours it takes from you even when it works.

As one participant summed up the mood of the whole event, only half-joking: "We used to think other people would build this, OpenAI or Anthropic would figure it out, so it wasn't worth building. But what's actually in your heart? You should just think, how hard could it be, and start."

Build in minutes, scale forever.

Convex is the backend platform with everything you need to build your full-stack AI project. Cloud functions, a database, file storage, scheduling, workflow, vector search, and realtime updates fit together seamlessly.

Get started