Your agent knows what to fix first
By Jake Marsh ·
Ask your agent how a project is doing and runheed_get_project_health now names the unresolved error with the most events in the last 24 hours, by ID. It also lists any error that came back after it was marked fixed, with the note it was resolved with.
New-error and came-back emails now say where the error happened: the route (without its query string), the first line in your own code, and the environment. The dashboard error list shows the same route and top frame under each message.
The demo shows a sample error that came back after a fix, if you want to see how that reads before connecting your own project.
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
- Errors arrive with what caused them November 6, 2026