Error reports start at the line in your code

Libraries often catch your error and throw their own with yours attached as the cause. The report then started deep inside the library, and your agent had to dig for the line that broke.

Python SDK 0.1.6 (November 11) and Node.js SDK 0.1.7 (November 12) now start the report with the frames from your code. The original exception is still listed under causes.

This matters most for MCP servers written in Python. The Python MCP SDK wraps every failing tool in its own UnexpectedToolError, so those errors used to show only SDK frames and group together. They now point at the line in your tool and group per tool.

If you report an exception yourself and a library then logs its wrapper of it, the wrapper no longer counts as a second error. Update the SDK to get the change.