Your first bug hunt.
Pick a challenge, open the project, and follow the evidence.
Read before you edit.
Start with the brief and source files. Look for the intended behavior, then use the tests to narrow down where the actual behavior differs.
Ask useful questions.
Ask the AI assistant to explain unfamiliar code, trace an input, or question an assumption. Its role is to guide your reasoning. Explicit hints are also available; their point costs are shown before you unlock them.
Run, revise, submit.
Edits save automatically while you work. Wait for saves to finish, run the tests, and revise your fix. When you submit, Kameleo grades that snapshot and saves a debrief with test results, hint usage, your code changes, and chat history.
What affects the score?
Your score depends on tests passed and points spent on hints. Running tests and talking to the assistant do not themselves deduct hint points. A score is feedback on this challenge, not a measure of your ability as a developer.
If something fails to load
The prototype backend can take a moment to wake up. If grading is unavailable, your saved code remains available to retry. Check for an unsaved-edit warning before leaving the page.