llms.txt
+174 −111
− For developers who ship code with Claude Code, Cursor or another coding agent, Runheed is error tracking your agent can read. Unlike pasting stack traces into chat, it gives the agent every occurrence with its stack trace, breadcrumbs and the session that wrote the code, and lets the agent mark the error resolved once the fix ships.− - Install: `npm install https://runheed.com/dl/runheed-0.1.0.tgz` (Node), `pip install https://runheed.com/dl/runheed-0.1.0-py3-none-any.whl` (Python), local MCP server `npx -y https://runheed.com/dl/runheed-mcp-0.1.0.tgz`− - [Error: read ECONNRESET](https://runheed.com/errors/econnreset): Node.js− - [Error: listen EADDRINUSE: address already in use :::3000](https://runheed.com/errors/eaddrinuse): Node.js− - [TypeError: Cannot read properties of undefined (reading 'x')](https://runheed.com/errors/cannot-read-properties-of-undefined): Node.js− - [[UnhandledPromiseRejection: This error originated either by throwing inside of an async function ...](https://runheed.com/errors/unhandled-promise-rejection): Node.js− - [FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory](https://runheed.com/errors/heap-out-of-memory): Node.js− - [Error [ERR_REQUIRE_ESM]: require() of ES Module ... not supported.](https://runheed.com/errors/err-require-esm): Node.js− - [Error: connect ECONNREFUSED 127.0.0.1:5432](https://runheed.com/errors/econnrefused): Node.js− - [Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client](https://runheed.com/errors/err-http-headers-sent): Node.js− - [RangeError: Maximum call stack size exceeded](https://runheed.com/errors/maximum-call-stack-size-exceeded): Node.js− - [TypeError: fetch failed](https://runheed.com/errors/fetch-failed): Node.js− - [SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON](https://runheed.com/errors/unexpected-token-json): Node.js− - [Error: ENOENT: no such file or directory, open '/app/config.json'](https://runheed.com/errors/enoent-no-such-file-or-directory): Node.js− - [Access to fetch at 'https://api.example.com/orders' from origin 'https://app.example.com' has bee...](https://runheed.com/errors/blocked-by-cors-policy): Node.js− - [TypeError: items is not iterable](https://runheed.com/errors/is-not-iterable): Node.js− - [Error: connect ETIMEDOUT 10.0.4.12:5432](https://runheed.com/errors/etimedout): Node.js− - [SyntaxError: Unexpected end of JSON input](https://runheed.com/errors/unexpected-end-of-json-input): Node.js− - [TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined](https://runheed.com/errors/err-invalid-arg-type): Node.js− - [TypeError: Cannot destructure property 'id' of 'undefined' as it is undefined.](https://runheed.com/errors/cannot-destructure-property-of-undefined): Node.js− - [Error: EACCES: permission denied, open '/app/data/cache.json'](https://runheed.com/errors/eacces-permission-denied): Node.js− - [TypeError: Converting circular structure to JSON](https://runheed.com/errors/converting-circular-structure-to-json): Node.js− - [AxiosError: Request failed with status code 401](https://runheed.com/errors/axioserror-request-failed-with-status-code): Node.js− - [PrismaClientKnownRequestError: Unique constraint failed on the fields: (`email`)](https://runheed.com/errors/prisma-p2002-unique-constraint-failed): Node.js− - [Error: EMFILE: too many open files, open '/app/uploads/0412.jpg'](https://runheed.com/errors/emfile-too-many-open-files): Node.js− - [ZodError: [ { "code": "invalid_type", "expected": "string", "received": "undefined", "path": [ "e...](https://runheed.com/errors/zoderror-validation-failed): Node.js− - [TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for /app/src/index.ts](https://runheed.com/errors/err-unknown-file-extension-ts): Node.js− - [Error: write EPIPE](https://runheed.com/errors/epipe-broken-pipe): Node.js− - [PrismaClientInitializationError: Can't reach database server at `db.example.com:5432`](https://runheed.com/errors/prisma-cant-reach-database-server): Node.js− - [MongoServerError: E11000 duplicate key error collection: app.users index: email_1 dup key: { emai...](https://runheed.com/errors/mongo-e11000-duplicate-key): Node.js− - [[ioredis] Unhandled error event: Error: connect ECONNREFUSED 127.0.0.1:6379](https://runheed.com/errors/redis-econnrefused-6379): Node.js− - [Error: error:0308010C:digital envelope routines::unsupported](https://runheed.com/errors/err-ossl-evp-unsupported): Node.js− - [MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added...](https://runheed.com/errors/maxlistenersexceededwarning): Node.js− - [TypeError: Client is not a constructor](https://runheed.com/errors/is-not-a-constructor): Node.js− - [Error: self-signed certificate in certificate chain](https://runheed.com/errors/self-signed-certificate-in-certificate-chain): Node.js− - [RangeError: Invalid time value](https://runheed.com/errors/invalid-time-value): Node.js− - [TypeError: Cannot convert undefined or null to object](https://runheed.com/errors/cannot-convert-undefined-or-null-to-object): Node.js− - [CredentialsProviderError: Could not load credentials from any providers](https://runheed.com/errors/aws-could-not-load-credentials): Node.js− - [Error: Could not load the "sharp" module using the linux-x64 runtime](https://runheed.com/errors/could-not-load-sharp-module): Node.js− - [Hydration failed because the server rendered HTML didn't match the client. As a result this tree ...](https://runheed.com/errors/hydration-mismatch): Next.js+ For developers who ship code with Claude Code, Cursor or another coding agent, Runheed is error tracking your agent can read. Unlike pasting stack traces into chat, it gives the agent every occurrence with its stack trace, breadcrumbs and, when you set it, the session that wrote the code, and lets the agent mark the error resolved once the fix ships. If the error comes back, the agent sees the note from its own last fix.+ Great Work LLC runs Runheed on its own products (BankBridge, CallForMe, Taskhold, Rookiefeed, Listvane and toolgate report their production errors to it).+ - Each plan starts with a 7-day trial: card taken up front in Stripe Checkout, nothing charged until day 7, cancel before then and nothing is charged. A workspace in its trial has the full plan.+ - Demo MCP server on invented sample errors, no account or key, nothing saved: https://runheed.com/api/mcp/demo (setup: https://runheed.com/demo#try)+ - Install: `npm install https://runheed.com/dl/runheed-0.1.7.tgz` (Node), `pip install https://runheed.com/dl/runheed-0.1.7-py3-none-any.whl` (Python), local MCP server `npx -y https://runheed.com/dl/runheed-mcp-0.1.7.tgz`+ - [Runheed + Kiro](https://runheed.com/connect/kiro)+ - [Runheed + Lovable](https://runheed.com/connect/lovable)+ - [Runheed + Replit](https://runheed.com/connect/replit)+ - [Runheed + Bolt](https://runheed.com/connect/bolt)+ - [Fastify error tracking for Claude Code and Cursor](https://runheed.com/for/fastify)+ - [Bun error tracking for Claude Code and Cursor](https://runheed.com/for/bun)+ - [Deno Deploy error tracking for Claude Code](https://runheed.com/for/deno-deploy)+ - [Render error tracking for Claude Code and Cursor](https://runheed.com/for/render)+ - [Railway error tracking for Claude Code and Cursor](https://runheed.com/for/railway)+ - [Go error tracking for Claude Code and Cursor](https://runheed.com/for/go)+ - [Ruby error tracking for Claude Code and Cursor](https://runheed.com/for/ruby)+ - [PHP error tracking for Claude Code and Cursor](https://runheed.com/for/php)+ - [.NET error tracking for Claude Code and Cursor](https://runheed.com/for/dotnet)+ - [Java error tracking for Claude Code and Cursor](https://runheed.com/for/java)+ - [React error tracking for Claude Code and Cursor](https://runheed.com/for/react)+ - [Why does my Node error handler fail or crash the server in Next.js?](https://runheed.com/guides/node-error-handlers-next-js-traps): Four things catch out code that works in plain Node. A namespace import of process has no on method. Next.js keeps your unhandledRejection listeners in its own list, so listenerCount looks wrong, and exiting on that kills a server Next meant to keep up. An early return in instrumentation.ts still sends your Node imports to the Edge build. And Next bundles a packa+ - [Why is my Python error reporting missing errors, doubling them or leaking secrets?](https://runheed.com/guides/python-error-reporting-traps): Five mistakes come up again and again in Python error reporting. Copying request headers sends Authorization and Cookie values to your tracker. Flask's errorhandler(Exception) also catches 404s and can turn them into 500s. A framework hook and a logging handler each report the same exception. Patching Thread.run misses every subclass that overrides run.+ - [Why does my error tracker show one bug as hundreds of different errors?](https://runheed.com/guides/error-grouping-fingerprints): Error trackers group repeats of a bug by a fingerprint, usually built from the error type, the message and where it was thrown. If the message holds a value that changes each time, like a user ID, an email, a timestamp or a duration, every occurrence gets a new fingerprint. You get a new-error alert per user and a list nobody can read. If the fingerprint includes t+ - [Why does NextResponse.redirect send users to localhost behind nginx?](https://runheed.com/guides/nextjs-redirect-localhost-behind-proxy): Under next start, a route handler's request.url is built from the address Next itself listens on, not from the Host header your proxy forwards. It does take the scheme from X-Forwarded-Proto, so behind nginx it reads https://localhost:3000/... and any redirect built with new URL(path, request.url) sends the user there. Build absolute URLs from a public orig+ - [Can Claude Code read my production logs?](https://runheed.com/guides/can-claude-code-read-production-logs): Yes, once you give it a route. Claude Code reads files and runs commands on the machine it runs on, so production logs reach it through a shell command you approve or through an MCP server. It can't see them by default. For exceptions, an error tracker over MCP such as Runheed gives it grouped errors with no server credentials.+ - [Can an AI agent fix production bugs by itself?](https://runheed.com/guides/can-ai-agent-fix-production-bugs): For a bug with a clear stack trace, code it can read and a test it can run, yes, up to a pull request. An agent can read the error, find the cause, write the fix and open the pull request with nobody watching. It fails when the cause is outside the code, and it should not decide what ships.+ - [How do I give Cursor access to production errors?](https://runheed.com/guides/give-cursor-access-to-production-errors): Connect an error tracker's MCP server. With Runheed, add its URL to .cursor/mcp.json and sign in, and Cursor's agent can list, read and resolve the exceptions your app reports. A project rule then tells it to check those errors before it debugs. Cursor gets no access to your servers.+ - [Does Sentry have an MCP server, and what can it do?](https://runheed.com/guides/does-sentry-have-an-mcp-server): Yes. Sentry runs a hosted MCP server at https://mcp.sentry.dev/mcp with OAuth sign-in, and publishes a stdio package, @sentry/mcp-server, for self-hosted Sentry. Coding agents can use it to search issues, errors, logs and traces, ask Seer for analysis and, if you grant the triage skill, resolve and assign issues.+ - [How do I add error tracking to a Lovable, Replit or Bolt app?](https://runheed.com/guides/add-error-tracking-lovable-replit-bolt): Report errors from your app's server code, then connect the tracker to the builder's agent. On Lovable, and on Bolt with Supabase, that means one shared file in your Edge Functions. On Replit, it means the Runheed Node.js or Python SDK. Errors in the browser are captured when the frontend reports through @sentry/react with the project's Sentry SDK DSN (/for/react)+ - [What is an error tracking MCP server?](https://runheed.com/guides/what-is-error-tracking-mcp-server): An error tracking MCP server lets an AI coding agent read production errors directly. It exposes an error tracker's data as tools over the Model Context Protocol, so Claude Code, Cursor or ChatGPT can list errors, read stack traces and often mark them resolved, with nothing pasted into the chat and no access to your servers.+ - [What does error tracking cost at 50k, 250k and 1M events a month?](https://runheed.com/guides/error-tracking-pricing-compared): At 50,000 errors a month the entry plans cost $20 to $29. At about 250,000 they cost $65 to $79, and at 1 million $176 to $225, depending on vendor and billing. Price alone separates them less than retention, what happens when you go over, and whether your coding agent can read and resolve the errors. Runheed is flat: $29, $79 and $199 a month, and events over the li+ - [Keep your Sentry SDK and send its errors to your coding agent](https://runheed.com/guides/use-sentry-sdk-with-runheed): Set your existing Sentry SDK's DSN to your Runheed project's Sentry SDK DSN, shaped https://<key>@runheed.com/<number>. No other code changes: exceptions, messages, stack frames, breadcrumbs, user, tags, release and environment arrive in Runheed, and your coding agent reads them over MCP.+ - [Give an agent running on Vercel your production errors (Vercel Connect)](https://runheed.com/guides/vercel-connect-production-errors): Create a Vercel Connect connector for runheed.com (Runheed publishes OAuth discovery and dynamic client registration, so Connect registers its own client), link it to your project, then pass connectAuthProvider to the AI SDK MCP client pointed at https://runheed.com/api/mcp. The agent gets all twelve Runheed tools, and no Runheed key lives in your environment + Each guide has a markdown version for agents at the same URL plus .md (or send Accept: text/markdown).+ - [Error: read ECONNRESET](https://runheed.com/errors/econnreset.md): Node.js+ - [Error: listen EADDRINUSE: address already in use :::3000](https://runheed.com/errors/eaddrinuse.md): Node.js+ - [TypeError: Cannot read properties of undefined (reading 'x')](https://runheed.com/errors/cannot-read-properties-of-undefined.md): Node.js+ - [[UnhandledPromiseRejection: This error originated either by throwing inside of an async function ...](https://runheed.com/errors/unhandled-promise-rejection.md): Node.js+ - [FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory](https://runheed.com/errors/heap-out-of-memory.md): Node.js+ - [Error [ERR_REQUIRE_ESM]: require() of ES Module ... not supported.](https://runheed.com/errors/err-require-esm.md): Node.js
Showing the first 40 of each.