Season 4 · Opens Oct 16 · $3,000 + $1,000 CLI bonus
Seven days to wire TestSprite into your repo so every pull request gets tested through the GitHub App. You keep what you wire up: a repo that goes on testing itself long after the hackathon ends.
Countdown
Oct 16 · final schedule confirmed in Discord
Prize pool
$3,000 for projects, plus a $1,000 bonus for CLI fixes. Separate pools.
Two ways to win
$3,000 · 5 winners
Best projects with TestSprite wired into the repo, so every pull request gets tested. Scored out of 100 by human judges.
$1,000 · allocated after close
Find something wrong with the open-source CLI and fix it. Open an issue, then open a PR that closes it. Entirely on GitHub, no forms.
The loop
Your coding agent ships code. Claude Code, Codex, Antigravity, whatever you build with.
You open a PR. The check runs on its own — no one has to remember.
Agent reads the failure bundle off the PR and fixes the root cause.
Push the fix. The check reruns itself, and the PR goes green.
Makeryour coding agentCheckerTestSprite 3.0
a loop you have to remember to run is a loop that stops running.
Start in 5 minutes
One account, one live URL, one connection to GitHub — then every pull request gets tested without anyone starting it. Existing projects welcome, no need to start from zero.
Free to start. Use the same email you'll submit with. Sign up free →
A deployed app anyone can open. Localhost doesn't count.
Agents explore the app and write the suite in the 3.0 portal. The PR check runs the tests you already have, so this comes first.
Install the GitHub App on your repo. From then on every PR gets tested on its own.
Install from Settings → GitHub App in the dashboard, pick your repos, done. Nothing is added to your repository. Results come back as a comment on the PR, and three per-repo switches decide the rest: Run on Pull Requests, Include Draft PRs, and Blocking PRs, which turns the result into a status check that holds the merge.
How to submit
Wire TestSprite to your repo, then open a PR. The check runs, TestSprite reports back on the PR, and that thread is the submission. Judges open the link and read the whole story off the PR, then check the suite itself in the portal.
Aim for a PR where the checks pass. A run that caught something first and went green after your fix is the best version of this, and it shows the loop actually works.
Two steps to submit — do both before the deadline
Your source, a README with the app and live URL, and at least one PR carrying a TestSprite check.
// code + what it does your-project/ ├── src/ // your app ├── .gitignore // no secrets in the repo └── README.md // required: app · live URL · what the suite covers
Your PR link, live URL, and TestSprite account. Demo video optional.
Prerequisites
Three things you hand in, two that have to be true for them to work.
A free TestSprite account. Use the same email you'll submit with, so judges can find your suite.
Source in a public repo, with a README covering the app, the live URL and what the suite covers. Commit history is the proof the app is yours.
Repo connected by the GitHub App, and at least one pull request carrying a TestSprite comment or status check. Tests should pass.
Tests run against your live app, no localhost. Deploy early, keep it live the whole build — the check has nothing to hit otherwise.
Built in the TestSprite 3.0 portal against your live app. The PR check runs this suite, so it has to exist first — a green PR proves it does.
Encouraged. Link it in Discord. Judges do watch them.
Judging criteria
Guest judges · Creator Picks
Five creators are joining Season 4 as guest judges and community supporters. They’ll review the projects and each select a standout project to recognize as their Creator Pick, along with a short quote about what impressed them.
Ömer Göçmen
Uğur Keşkekçi
Astro K Joseph
Poyraz
Jan MarshalCreator Picks are separate from the official competition scoring. Prize winners are determined by our judging panel using the official rubric, and Creator Picks do not affect the prize pool.
CLI Improvement Bonus · $1,000 pool · all 14 days · open to everyone
The whole workflow lives on GitHub. Open an issue, claim it, open a PR that closes it. Entries follow the same rules as any other contribution to the repo, so nothing about this is a special path. Tick one box in the PR template and you’re in.
npm install -g @testsprite/testsprite-cliDescribe the problem and assign the issue to yourself, so everyone can see what's already being worked on. PRs titled docs: skip this step.
Up to three open claimed issues at a time. A claim with no activity gets a warning at 48 hours and is released at 72, so nobody sits on work they aren't doing.
Your PR body needs Closes #123 pointing at your issue, the entry checkbox ticked, and your Discord username so we can reach you. Not on Discord? We'll reach you on the PR.
A bot confirms your entry in a comment. If it looks like an entry but the box is unticked, it asks rather than excludes you. Up to three bonus-eligible PRs per person; contribute as much as you like beyond that.
1## Season 4 CLI Improvement Bonus23- [ ] I'm entering this PR for the Season 4 CLI Improvement Bonus4567---89## What's broken1011## How you found it1213## Why it matters
The bars
A PR has to be merged and judged a genuine improvement. Those are separate bars, so a PR can land and still earn nothing.
Full CLI rules go live a week before Day 1, so there's time to read the codebase and find something real before the window opens.
The aspects
Each eligible PR is then read against four aspects, with a “meet” and an “exceed” for each. Up to two revision rounds on substance.
Feedback · Open all season · every surface
Your feedback shapes what we build next. A week of real builds on codebases we've never seen will surface things we've missed. If something in the 3.0 web portal, the CLI, or the MCP server got in your way, confused you, or you can see a better way to do it, tell us. Specific beats polite: what you tried, what happened, what you expected instead.
Share feedback in DiscordTest generation that missed the point, verdicts that were hard to read, anything you had to work around in 3.0.
Flags, output, docs, install. If it's a bug with a fix, open the issue and PR instead, and it can count toward the bonus.
Still supported. If a tool description misled your agent or a call failed silently, tell us — the portal and the CLI come first this season.
Credits for the good stuff. Feedback that changes what we build may earn extra TestSprite credits as a thank-you. It's not a guarantee and it isn't scored, it's how we'd like to say thanks for helping make the product better.
Execution timeline
Oct 2
Full rules go live, including the CLI bonus. Two weeks to read the codebase before the window opens.
Oct 16 · Day 1
Project Track begins: build, generate the suite, and connect the repo so your PRs get tested. The CLI issue and PR window opens the same day and runs the full 14 days.
Oct 22 · Day 7 · 11:59 PM PT
PR link + live URL + account email, posted in Discord by the deadline.
Oct 23 · Day 8
Runs Days 8–12; CLI bonus stays open through Oct 29.
Oct 29 · Day 14 · 11:59 PM PT
PRs must be open and out of draft to be counted.
Oct 30 — Nov 3
Agents screen, a human decides. The $1,000 CLI pool is allocated once, in a single batch.
Nov 6
Announced on X and Discord. Payouts from both pools.
All times Pacific · final schedule confirmed in Discord
Join
Announcements, countdowns, and winner reveals go out on X first.
Follow on XRules, submissions, polls, Q&A. Season 4 rules pinned in #hackathon-info.
Join Discord
One week to get your pull requests testing themselves. Find a CLI bug along the way? Fix it for the bonus. Follow on X and join Discord, where everything happens.