Pick a real bug. Ship the fix with AI.
Every challenge is a genuine GitHub issue from a major Python project, graded by the hidden tests from the fix that actually merged. Read the briefs here and create an account to start a round.
- Challenges
- 199 challenges
- Repositories
- 11 repositories
- Graded rounds
- 62 graded rounds
Multi-level FilteredRelation with select_related() may set wrong related object.
Queryset raises NotSupportedError when RHS has filterable=False attribute.
+300 XPCompete →
Track your progress
Sign in to see what you have solved, keep a streak, earn badges and XP, and climb the leaderboard.
Open a practice track
Data engineering and SQL practice
Check how queries group, filter and combine records, then practice writing SQL against a small dataset with missing and repeated events.
View track ↗- 100%1 round72hardDjango 3.0: "GROUP BY" clauses error with tricky field annotationdjango/djangowebormhard100% solved
- —0 rounds—hardUsing __isnull=True on a KeyTransform should not match JSON null on SQLite and Oracledjango/djangowebormhardnew
- 100%2 rounds75easyPolyFit is not robust to missing datamwaskom/seabornplottingstatseasy100% solved
- —0 rounds—easyFiltering on query result overrides GROUP BY of internal querydjango/djangowebormeasynew
- —0 rounds—easyQuerySet.none() on combined queries returns all results.django/djangowebormeasynew
- —0 rounds—easyto_unstacked_dataset broken for single-dim variablespydata/xarraydataarrayseasynew
Build from a brief
Delivery metrics in SQL ↗
Write a daily SQLite report that handles duplicate delivery scans, orders in flight and regions with zero shipments.
24-hour project window / about 2h suggested effort / paid plan
Bike-share trips ETL pipeline ↗
Generate messy trip exports, clean them with documented rules, and load an idempotent SQLite warehouse with a daily summary.
24-hour project window / about 4h suggested effort / paid plan
Household energy explorer (data visualisation) ↗
A front-end-only dashboard over a year of half-hourly smart-meter data: zoomable time series, heat map, tariffs and honest gaps.
24-hour project window / about 4h suggested effort / paid plan
From Start to score in four steps
- 1
Open your workspace
VS Code opens in a new tab with the repository, dependencies and tests ready. Read the instructions, then press Start inside the workspace to begin the timer.
- 2
Fix it with the agent
Standard rounds give you 60 minutes and up to 1M tokens; Speedrun gives you 20 minutes and Frugal lowers the token budget. Check your selected mode and allowance before starting. Paid rounds spend agent credit; free rounds do not.
- 3
Your work builds the report
The workspace records prompts, agent actions, edits, test runs and token use. It also records pastes and time away from the tab. It does not watch activity outside the workspace.
- 4
Submit and get scored
Hidden tests from the original fix check your patch. Graded rounds include a free score and test result. A paid plan adds the detailed breakdown, prompt coaching and replay. Eligible graded attempts also earn XP.
How the score is made
Your overall score is a weighted blend of six sub-scores. Solving the issue matters most, but how you drove the agent, checked your work and spent your tokens is what separates a good engineer with AI from a lucky one. Non-empty practice submissions can earn XP. Your best result on each task counts, with harder tasks and passing tests worth more.
- Outcome35%
Do the hidden tests pass, and does nothing that worked before break?
- Prompt quality15%
Specific, contextual instructions beat “fix it”.
- Token economy15%
Solving it without burning the budget.
- Verification15%
Running the tests yourself before you submit.
- Speed10%
Time to a working fix (only counts when it works).
- Recovery10%
Getting out of error loops instead of repeating them.