Stack trace
The list of lines under an error that shows exactly which code was running when it broke.
What it is
When code crashes, the error message says what went wrong. The stack trace underneath says where: a list of function names and file locations, most recent first, tracing the path the code took to the failure.
You don't need to read it, but you should always include it. To a coding agent it's a map straight to the broken line. Trimming it to "TypeError" throws that map away.
In the Console, click the small arrow beside a red error to expand its stack trace. In the terminal, it's the block of indented lines that starts with "at".
How to ask for it
“It says TypeError.”
“Here's the full error with its stack trace from the Console, unedited. It happens every time I open a project with no tasks. Find the root cause.”
The full stack trace plus the trigger tells the agent where it broke and when, so it can fix the cause in one pass.
You've seen this in
- LLines starting with "at" under a red Console error
- PPython's "Traceback (most recent call last)"
- DCrash screens in development mode