go scan 🔍

Introducing an integration with @vercel Now you can give your agents read-only access to your Vercel deployments, functions, observability and more.

today we're open-sourcing Responder: github.com/superloglabs/resp…. triage your Sentry and Datadog alerts in Slack, fix real issues and cut the noise. we want to cut toil and stress and let you get back to building. join us!

new: see the Superlog investigation right in Slack

we just launched Responder on @ProductHunt! (link's in the first comment 👇) quick story: every observability tool is great at exactly one thing, telling you something broke. then it hands you a wall of logs and wishes you luck. we got tired of that. so we built Responder. now live on Product Hunt. an upvote and a comment would be super useful!

Today, Superlog needs your support. We're launching Responder on ProductHunt: producthunt.com/products/sup… Install Responder, our bug-fixing harness, on top of Datadog and Sentry and build your bug-fixing agents. Please upvote on ProductHunt and give Responder a try!

Hey everyone, we just shipped Superlog Responder. Our bug-fixing framework, now on top of Sentry/Datadog. TL;DR: Some of you wanted our >90% PR-acceptance framework but not another observability tool to install. We got it. Responder plugs into your existing Sentry/Datadog Slack channel, triages every alert, and replies with root cause + a mergeable PR. 100 free investigations to start + 50 free/month, forever. The Problem Everyone is trying to build their own bug-fixing agent internally. The idea is obvious: point an agent at your alerts, let it fix the bugs. So people vibe-code a version over a weekend. But this is what actually happens: - the MCPs never authorize cleanly outside a local Claude Code setup, so the agent can't reliably reach your own services (DB, PostHog, etc.) without weird workarounds - it doesn't auto-trigger the moment a bug appears, so you're still the one noticing and kicking it off - it escalates everything (and token consumption explodes), or nothing, because there's no logic for when to pull in a human vs. handle it silently - it goes quiet while it works, so nobody in Slack knows what it's doing or whether to trust it - it has nowhere to actually reproduce the bug, fix it, and QA the fix, so the PR is a guess A few days later, the prototype gets abandoned, and you're back to copy-pasting stack traces into Claude. To solve this, we took the exact framework behind Superlog's bug-fixing agent (which normally runs on Superlog's telemetry), and pointed it at the stack you already run. That's Responder. lnkd.in/ehRWgHRD The Solution No new telemetry. You plug Responder into what you already have: - connect it to your Sentry/Datadog Slack channel - get your bugs fixed On every alert, Responder investigates with full context, filters out the noise, and for real issues replies in the thread with the root cause, the evidence, and a mergeable PR (if it's worth it). Prompts, memory, repo, and accesses are fully customizable, so you're building your debugging agent, not renting ours.

triage and fix incidents in Slack automatically with responder.superlog.sh we're launching early access to the bug-fixing harness we use at @superlogYC. add @datadoghq, @SlackHQ and configure your agents. full sandbox, root cause analysis, severity assessment - triggered immediately on new errors.

at superlog.sh, we've just shipped an integration with @sentry. connect Sentry -> your Superlog bug agent fixes every new issue. noise gets labeled. every PR review improves accuracy and creates new agent memories. try Superlog!

move fast. break things. superlog fixes them. we just 10x'd the free tier on superlog.sh one click to send telemetry from Vercel, Railway, Render, AWS, GCP + more. we instantly start investigating every error and hand you a PR with the fix. ship recklessly. we've got the cleanup.

superlog.sh just 10x'd the free tier. we want you to ship more, more reliably. send your telemetry in one click from Vercel, Railway, Render, AWS, GCP and more. we investigate every error and give you a PR with a fix. no more noise, no more investigating.

✨we just shipped 3 new graphs to superlog.sh powered by dither-kit by @tripwiredotsh and @grimcodes

your debugging agents need read-only access to your database. now you can add your database MCP as a custom tool to your superlog.sh agent!

how do you keep logs up-to-date? our users asked us to help them keep their code observable. so we shipped Observability Review: a PR review bot that tells you if you missed error logs, performance metrics, or span/log attributes in your PRs. check it out at superlog.sh!

a month ago we open-sourced @superlogYC. a few days ago it hit 1,000 stars on @github. it's observability that's meant not to be opened: a wizard instruments your code, error noise collapse into one incident, and an agent ships a PR to fix it. didn't expect this a month in. thank you to everyone who starred it, filed an issue, or told us exactly what was broken. still just getting started!!

published our first Superchangelog superlog.sh/blog/quieter-inc… we completely reworked how our agents work. they now produce way less noisy PRs, obey by our AGENTS.md, can reply to you on Slack, and can work on many PRs until they pass review.

Superlog - AI-native observability that fixes bugs (@superlogyc) Cossmology Profile: dub.sh/voeiqyP Key People: Nicolò Magnante (@nicolomagnante), Arseniy Shishaev (@arseniycodes) #Observability #OpenSource #OSS #COSS

introducing slack q&a for superlog.sh now you can chat with Superlog in Slack and investigate incidents, handle support issues and help your teammates!

new integration at superlog.sh - this time with @render. we use Render API to install a log sink and an OpenTelemetry destination for metrics. using @render? go to superlog.sh now and sign up! we read all feedback.

That’s super