Errors arrive with what caused them
By Jake Marsh ·
Some errors say almost nothing on their own. In Node, TypeError: fetch failed is the usual example: the reason the request failed sits in the error's cause.
The Node and Python SDKs (0.1.1 and later) now send the whole chain of underlying errors as causes. Your agent sees ENOTFOUND or a refused connection right next to the error.
Grouping is unchanged, so existing errors stay where they are. Update the SDK to start sending causes.
More news
- Error reports start at the line in your code November 12, 2026
- Every Runheed plan starts with a 7-day trial November 11, 2026
- Your agent knows what to fix first November 8, 2026