Blog

Can you use AI and vibe coding at a hackathon? What the rules say and how to stay safe

· buildtolaunch

This guide is for students who want to enter a hackathon and are not sure whether AI coding tools or vibe coding are allowed. You get the short answer, the three kinds of AI rules you will meet, and a checklist to run before you register. It sits inside our full hackathon guide for students.

Short answer

Usually yes, but it depends on the event, so read the rules first. Some hackathons welcome AI tools if you disclose them. Some restrict AI to learning and debugging. Others are built around vibe coding, where you describe an app and an AI writes the code. If the rules do not mention AI, ask the organizers before you start.

What "vibe coding" means

Vibe coding means building software by prompting an AI model, testing what it produces and asking for changes, often without reading the generated code. Martin Fowler's note on the term credits Andrej Karpathy with coining it in a February 2025 post on X. Fowler also points out that this style suits throwaway software for you or a small group, and often causes problems with maintenance, correctness and security.

That last point matters at a hackathon. Judges and organizers worry less about whether AI wrote code and more about whether you understand and can defend what you built.

The three kinds of AI rules you will meet

1. Allowed, with disclosure

Many hackathons let you use AI but ask you to say so. MLH's guide to hackathon rules says participants may use AI tools but must disclose that use in their submission and credit the tools in a detailed readme. It also says a project cannot simply repackage an existing AI tool, and that undisclosed AI use can lead to disqualification.

2. Restricted to learning and debugging

Some events, especially school-run ones, limit AI to support tasks. One school hackathon's published policy (TISB Hacks) allows AI for understanding concepts, debugging errors, looking up documentation and brainstorming, but discourages bulk code generation and copy-pasting code you cannot explain. Its test is simple: if a judge asks about any part of your code, every team member should be able to explain it. Projects with excessive AI-generated code may be penalized or disqualified.

3. Built for AI and vibe coding

A growing number of events are designed for people who do not code. For example:

  • The ISM University hackathon in Vilnius is a five-day event that its organizers describe as "not a coding hackathon". It is open to students from any discipline, with free access to tools such as Bolt.new and Lovable.
  • LegalTechTalk's Vibeathon, announced in May 2026, asked lawyers and other non-coders to build legal tech prototypes with natural-language prompts.
  • In Vietnam, the Vietnamese Student HackAIthon 2026 had separate tables for AI usage skills, building AI solutions, and designing AI agent assistants.

For the half-day version, see what a vibe-a-thon is.

A note on startup contests in Vietnam

If you are entering a startup contest rather than a hackathon, AI rules can be stricter about paperwork. The Ministry of Education and Training's rules for the 8th "Học sinh, sinh viên với ý tưởng khởi nghiệp" contest, as summarized on LuatVietnam, required projects that use AI to declare the tools used, their purpose and the estimated share of AI-assisted content. Rules change between editions, so read the current one. The difference between contest types is covered in hackathon, startup contest and case competition compared.

Checklist before you use AI at a hackathon

  1. Read the rules page for the word "AI". Look at the eligibility, originality and submission sections.
  2. Ask the organizers if it is unclear. A one-line message is enough: "Can we use AI coding tools? Do we need to disclose them?" Save the reply.
  3. Respect the "new work" rule. MLH's rules guide says teams should not start building before the event and should stop when submissions close. Prompting an AI to generate a full app the night before is still starting early.
  4. Disclose in your submission. List the tools, and say what you used them for. See the next section.
  5. Be able to explain every part. Rehearse one explanation of how the app works, in your own words, for each team member.
  6. Keep secrets out of prompts and code. Do not paste API keys or personal data into an AI tool or a public repository.

How to disclose AI use

Keep it plain and specific. A short note in your readme or submission form is enough:

AI tools used: Lovable to generate the first version of the interface; ChatGPT to help write the pitch outline. What we did ourselves: problem research, user interviews, all product decisions, testing with 8 students, final edits to the copy.

Honest disclosure rarely costs you points. Hiding it can cost you the prize.

Where to practise

If you have never built with AI tools, practise before the event. buildtolaunch is a free community for students of any major, and no coding is needed to start. The course library has 70+ free courses from Anthropic (Claude Academy), Google, Lovable, DeepLearning.AI, Hugging Face and Kaggle, and the practice tutor lets you rehearse skills with an AI. Events like Vibe-a-thon Saigon showed that people with no coding background can ship working apps in one afternoon; read the recap. To find competitions, check Opportunities.

FAQ

Can I use ChatGPT, Claude or Copilot at a hackathon?

Often yes, but it depends on the rules. Some events allow AI tools if you disclose them, some limit AI to debugging and learning, and a few ban it. Read the rules page, and ask the organizers if the page does not mention AI.

Is vibe coding cheating at a hackathon?

Not by default. It is cheating only if the rules forbid it or you hide it. Many events now welcome it, and some are designed around it. Judges usually still expect you to explain your idea, your decisions and how the product works.

Do I have to tell the judges I used AI?

Check the rules, but disclosing is the safe choice. MLH's rules guide asks for disclosure in the submission and says undisclosed AI use can lead to disqualification. A short, specific note on which tools you used and for what is enough.

Can I start my project before the hackathon with AI?

Usually not. Many hackathons require new work started during the event, and MLH's guide says teams should not begin building early or reuse code from earlier projects. Planning, research and learning the tools beforehand are normally fine. Check the rules for the exact wording.

Can a non-coder win a hackathon with vibe coding?

Yes, it is possible, especially at events that welcome non-coders. Winning projects tend to solve a clear problem, work in a live demo and are explained well. Vibe coding gets you a working demo faster, but the idea and the pitch still decide the result.

What if the organizers have no AI rule?

Ask in writing and keep the answer. If they do not reply, use the strictest reasonable reading: disclose your AI use, build only during the event and make sure you can explain everything you submit.

Read the full guide: Hackathon for students, start to finish.