
Participants must be 16 years of age or older.
Only individuals who complete the official registration form will be granted access to the hackathon platform.
The hackathon is fully online. All team activities, including collaboration, workshops, mentoring, and project submissions, must take place using the designated platforms.
Teams may consist of 1 to 4 members. All members must be officially registered. Collaboration outside official channels is allowed only for coordination among registered teammates.
To qualify for cash prizes or interview opportunities, projects must follow the requirements for each prize category. Each award is tied to specific sponsor tools, and your submission must meet those requirements to be eligible.
Projects that do not use the required sponsor technologies for their respective categories are not eligible for those sponsor-specific prizes.
Refer to the Resources section for guides and documentation.
Make sure to check out the resources section to learn more about these tools.
Participants must use the Cline CLI, the command-line interface for autonomous AI coding agents. You should build new capabilities on top of the CLI that improve the software development experience, and your project should demonstrate complete, working automation tools built through the CLI.
Your project must use Kestra's built-in AI Agent to summarise data from other systems, with bonus consideration if the agent can also make decisions based on the summarised data.
Your submission must use the Oumi open-source library, specifically Oumi's Reinforcement Learning fine-tuning features (more info). You may also choose to use Data Synthesis, LLM-as-a-Judge, or any examples provided in the Oumi notebooks, as these are optional but encouraged.
Your project must be deployed on Vercel. Any standard Vercel deployment qualifies.
Your repository should demonstrate the use of CodeRabbit for PR reviews, code quality suggestions, documentation improvements, and overall open-source best practices. CodeRabbit activity should be clearly visible in your workflow.
Each submission must include:
A public repo with visible commit history.
A clear explanation of the project, setup instructions, and usage details.
A mandatory 2-minute demo showcasing the project.
Optional for most tracks but earns extra credit.
Deployment is mandatory when competing for prizes that require Vercel.