When your code throws an error and you can't see why, pasting the error message and code into Claude can quickly surface the cause and a fix. This guide covers how to debug in a plain claude.ai chat — without tools like Claude Code — using error logs and stack traces. (Claude's suggestions aren't always correct, so always confirm a fix by running and testing the code yourself.)
1. What to include when debugging
A good diagnosis comes from good information. Give these three together and Claude pinpoints the cause far more accurately.
- The full error / log: don't trim it. The line in the stack trace that points to "where it happened" matters most.
- The failing code: the part the error points to and its surroundings, plus related functions and config.
- Context and expected behavior: language and version (e.g., Python 3.12), the runtime, and what it "should" do.
2. Examples of good debugging questions
"Running the Python code below throws this error. Tell me the cause and how to fix it. [full error] [code] Context: Python 3.12, input is a CSV file."
- "First explain in plain terms what this error message means."
- "List likely causes, most probable first."
- "Give the full fixed code and explain what you changed and why."
3. When the cause isn't obvious
If the message alone doesn't reveal it, you can narrow down together with Claude.
- Add logging: "Where should I add logs to see where the value goes wrong?"
- Minimal reproduction: "Write the smallest code that reproduces this." (isolates the cause)
- Test a hypothesis: "I suspect this part — what should I print to confirm?"
4. Learning to read errors and stack traces
Beyond fixes, you can build the skill of reading errors yourself.
- "Walk through this stack trace line by line from the top."
- "Why do common errors like 'undefined is not a function' or NullPointerException usually happen?"
Things to watch for
- Verify every fix: Claude's edit isn't always right. Run the fixed code and check the result.
- Strip sensitive data: if API keys, passwords, or real customer data appear in code or logs, remove or mask them before pasting.
- Long context lowers accuracy: giving only the relevant part is more accurate than dumping a huge codebase.
- Don't take it on faith: understand why the fix works before applying it. Pasting without understanding breeds the next bug.
FAQ
Q. Do I need to give all my code?
No. The part related to the error, its surroundings, and the context are enough. Too much code actually clouds the diagnosis.
Q. Can Claude fix code directly in my terminal?
Yes — that's the domain of Claude Code (the CLI agent). → Claude Code use cases (debug, refactor)
Q. The "Claude Code" tool itself throws an error.
That's a different problem. → Reading Claude Code error messages
For developer use in general, see Claude use cases by role.