.NET and ASP.NET Core error tracking your coding agent can read
Updated 2026-11-13
Runheed accepts events from Sentry SDKs, so a .NET app reports through the Sentry NuGet package: point its DSN at your Runheed project and your coding agent reads each exception over MCP from Claude Code, Cursor or any MCP client. Tested with Sentry 7.0 on .NET 9. ASP.NET Core apps add Sentry.AspNetCore, which uses it underneath.
Set it up
1.Add the package (Sentry.AspNetCore for a web app).
terminalbashdotnet add package Sentry # ASP.NET Core: dotnet add package Sentry.AspNetCore2.Initialize it with the project's Sentry SDK DSN (Projects page, or ask your agent: runheed_list_projects).
Program.cscsharp// RUNHEED_SENTRY_DSN=https://<key>@runheed.com/<number> // ASP.NET Core: var builder = WebApplication.CreateBuilder(args); builder.WebHost.UseSentry(o => { o.Dsn = Environment.GetEnvironmentVariable("RUNHEED_SENTRY_DSN"); o.Release = Environment.GetEnvironmentVariable("GIT_SHA"); }); // Console apps and workers: // using (SentrySdk.Init(o => o.Dsn = Environment.GetEnvironmentVariable("RUNHEED_SENTRY_DSN"))) { ... } // Anywhere you catch an exception you still want to see: try { Billing.ParseInvoiceTotal(input); } catch (Exception e) { SentrySdk.CaptureException(e); }3.Connect your agent, then sign in when it asks (other clients: /connect).
terminalbashclaude mcp add --transport http runheed https://runheed.com/api/mcp
The npm and PyPI releases are not out yet, so these commands install the same package files straight from runheed.com. Nothing else changes when the registry versions ship.
What it catches
- Exceptions you report with SentrySdk.CaptureException(e)
- Unhandled exceptions in ASP.NET Core requests, through Sentry.AspNetCore
- Release and environment from the options
What it does not do
- Tracing and profiling are accepted and dropped: Runheed tracks errors only
Then ask your agent
> what broke in production since the last deploy? fix the top one and resolve it with the commit hash
Connect Runheed first: Claude Code, Cursor or another client. Then see how the agent fixes and resolves an error.