Code Explainer & Debugger

Code Explainer & Debugger reads your program the way a patient teaching assistant would. Paste the code and say what it should do or what goes wrong, and you get a walkthrough of what each part actually does, the line where behaviour diverges from intent, and an explanation of the error message in plain words. When there is a bug, it shows the smallest change that fixes it and explains why, so you understand the mistake rather than just replacing the file. It also explains unfamiliar syntax, traces a loop by hand with a sample input, and can describe what a function returns for a given argument.

Include the full error message and the input that triggers the problem; 'it does not work' is much harder to help with than 'it prints 0 when I enter 5'. Paste enough surrounding code that the tutor can see where variables come from. Say which language and version you are using if it is not obvious, and mention any library the assignment requires. Before applying the fix, try to predict what it will be from the explanation of the bug. Then run the code yourself; a suggested fix is a hypothesis until your tests pass, and running it is how you find out whether the diagnosis was right.

If you want to understand a language feature in general, such as recursion or pointers, ask Explain a Concept. If you have not written anything yet and want the approach without the code, ask for a hint. For a written explanation of an algorithm in an essay or report, Essay Feedback can review it. Most courses have rules about how much AI help is allowed on programming assignments; know yours, and be able to explain any code you hand in, because the explanation is what an instructor will ask for.