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 any of them free; start a round when you are ready.
- Challenges
- 201 challenges
- Repositories
- 11 repositories
- Graded rounds
- 62 graded rounds
Wrong path to test file when directory changed in fixture
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.
Stripe-style debugging practice
Debug across filesTrace a bug through an unfamiliar codebase, make a focused change and check that existing behavior still works.
- 100%1 round72hardDjango 3.0: "GROUP BY" clauses error with tricky field annotationdjango/djangowebormhard100% solved
- 100%2 rounds76hardUnroll the iterable for all/any calls to get better reportspytest-dev/pytesttestingtoolinghard100% solved
- —0 rounds—hardTrailing whitespace in DatasetGroupBy text representationpydata/xarraydataarrayshardnew
- —0 rounds—hardINTERNALERROR when exception in __repr__pytest-dev/pytesttestingtoolinghardnew
- —0 rounds—hardPytest 6: Dynamically adding xfail marker in test no longer ignores failurepytest-dev/pytesttestingtoolinghardnew
- 100%2 rounds85medium★Auto-reloading with StatReloader very slow on Windowsdjango/djangoperformanceutilsmedium100% solved
- —0 rounds—medium[Bug]: Setting norm with existing colorbar fails with 3.6.3matplotlib/matplotlibplottinggraphicsmediumnew
- —0 rounds—mediumDisplay fixture scope with `pytest --fixtures`pytest-dev/pytesttestingtoolingmediumnew
- —1 round—mediumDailyWrong path to test file when directory changed in fixturepytest-dev/pytesttestingtoolingmediumnew
- —0 rounds—mediumImprove handling of skip for module levelpytest-dev/pytesttestingtoolingmediumnew
- —0 rounds—medium★Exponent doesn't fully simplifysympy/sympysimplificationmathmediumnew
- —0 rounds—easy★Ignore missing variables in Dataset.droppydata/xarraydatasetapieasynew
- —0 rounds—easyto_unstacked_dataset broken for single-dim variablespydata/xarraydataarrayseasynew
- —0 rounds—easyFeature request: show units in dataset overviewpydata/xarraydataarrayseasynew
- —0 rounds—easyRewrite fails when first expression of file is a number and mistaken as docstringpytest-dev/pytesttestingtoolingeasynew
- —0 rounds—easyModule imported twice under import-mode=importlibpytest-dev/pytesttestingtoolingeasynew
- —0 rounds—easyImprove default logging formatpytest-dev/pytesttestingtoolingeasynew
- —0 rounds—easyHostname and timestamp properties in generated JUnit XML reportspytest-dev/pytesttestingtoolingeasynew
- —0 rounds—easypytest --collect-only needs a one char shortcut commandpytest-dev/pytesttestingtoolingeasynew
- —0 rounds—easyError message prints extra code line when using assert in python3.9pytest-dev/pytesttestingtoolingeasynew
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.