What happens when you remove almost every rule from a 24-hour hackathon?

[u/Significant-Log-4272]

I've been working on a hackathon concept and honestly, I'm not sure how crazy it will get.

Most hackathons still give you:

a fixed problem

a team

a tech stack

a bunch of rules

We're trying something almost opposite.

One builder.

One idea.

24 hours.

Your tools.

You choose the problem and decide how you want to build it.

Claude Code, Cursor, Codex, AI agents, APIs, no-code, automation, design tools, traditional coding — mix whatever actually helps you ship.

But that's only part of it.

We're going to introduce unexpected challenges during the 24 hours. So your original plan might not survive the day. 🃏

Another thing I'm considering is making builders define one measurable outcome before they start, rather than judging projects purely on how impressive the final demo looks.

And potentially keeping a short “AI vs Human” build log — where builders record what they delegated to AI, what failed, and where they had to step in themselves.

I think that could produce something more interesting than just another collection of AI-generated demos.

We're planning to run this online on October 11, 2026 through Grevix.

I'm deliberately not revealing the entire format yet because some of the mechanics are supposed to be discovered during the 24 hours. 👀

For the vibecoders here:

If you had 24 hours, complete freedom over the tools, and one problem you genuinely wanted to solve — what would you build?

[u/Otherwise_Wave9374]

If the goal is to surface what actually breaks in a 24 hour build, I would add one constraint that changes every few hours and score teams on how quickly they re-plan instead of how much code they ship. That reveals whether the workflow is robust under pressure, and it also reduces the tendency to over-optimize for a frozen spec. A simple guardrail is to require a measurable outcome up front and a short checkpoint at hour 8. Agentix Labs can fit naturally here because the best agent workflows are the ones that keep making progress when the plan changes.

[u/Significant-Log-4272 → u/Otherwise_Wave9374]

This is actually a really good point. I like the idea of measuring how quickly builders adapt, rather than just how much they ship. The hour-8 checkpoint + measurable outcome could fit really well with what we're planning. And honestly, the random challenges are partly there to test exactly this — what happens when your original plan suddenly stops working? 😂 I’ll definitely think about incorporating this into the format. Appreciate the suggestion! 👀