Paladin – An AI trigger to fix your sh*t production bugs
Everyone hates production bugs. Users get frustrated. Engineers get paged. Development gets delayed. But what if many of those bugs could be fixed automatically? Enter Paladin, a tool I built that automatically sends you a pull request to fix bugs shortly after they occur. A little over a month ago, I posted my hacky but effective AI setup for fixing production bugs to Reddit (https://redd.it/1jibmtc). 300+ devs messaged me or commented wanting to try it out, so I’ve been spending the past weeks refining it into Paladin, and excited to release it today! How it works: Paladin…
What it does
In the maker’s words, at launch
Everyone hates production bugs. Users get frustrated. Engineers get paged. Development gets delayed. But what if many of those bugs could be fixed automatically? Enter Paladin, a tool I built that automatically sends you a pull request to fix bugs shortly after they occur. A little over a month ago, I posted my hacky but effective AI setup for fixing production bugs to Reddit (https://redd.it/1jibmtc). 300+ devs messaged me or commented wanting to try it out, so I’ve been spending the past weeks refining it into Paladin, and excited to release it today! How it works: Paladin hooks into your application’s error handling with an SDK, triggering a “run” when an exception is thrown. During the run, Paladin pulls your code on Github and uses LLMs to fix the error, sending you the fix as a PR over Slack in ~90 seconds. Here’s a two minute demo: https://youtu.be/0bm8nq99Nrw. In early testing, Paladin solves over 55% of real production errors on the first try and makes useful progress on many others. It’s able to do well by supplying deep context to the LLMs: the stack trace, execution state, repo code, and more. When it works well, it allows you to fix bugs more quickly, meaning less downtime for users and saved engineering time. Eliminating context switching has been an unexpected win for me, because I work best in long, focused stretches. When a bug hits affecting real users, I have to drop everything mid-feature to stash changes, debug, and mentally shift contexts, and then try to return. I’ve found PR reviews and tweaks to be much less disruptive. Getting started (Free, no card required) 1. Sign up at https://app.paladin.run/signup 2. Follow instructions to connect your Github and Slack (or just email) 3. Choose and install the correct SDK into your app 4. Configure to send errors to Paladin 5. Done! Paladin supports React, React Native, Laravel, Flutter, Django, Node, Next, Vanilla Javascript, Express, FastAPI, PHP, Vanilla Python, Nest, Vue, Android, iOS, Rails, Flask, and many more thanks to Sentry’s MIT licensed client SDKs (your errors do not go to Sentry, they are just used to capture errors). If you have a client and server, I’d start with your server. Notes on privacy, performance, and future plans below: Paladin will never abuse repo access for any type of training or sharing, and only pulls it for making fixes. An LLM provider (Google/Anthropic/OpenAI) processes part of your code, so if you can’t use tools like Cursor/Windsurf, you probably can’t use Paladin. On performance, my personal set is admittedly very limited, but I think the performance makes sense to me given current bests on benchmarks like Aider Polyglot and SWE-bench Verified. I’d expect these numbers to get much better as models progress. I’d also expect Paladin to fall short where current frontier LLMs do: uncommon frameworks, libraries or languages. In the future, I am planning on having two usage options: - Free: if you bring your own OpenRouter API key - Paid: if Paladin pays for the model costs Really looking forward to hearing feedback and ideas!
Does the same job
all alternatives →- MAMeatshields – An in-browser turn-based strategy game2017 · ▲113
A few months ago (82 days to be exact!) I posted a link on HN to my game, Meatshields. A bunch of you commented and played my game and gave me some wonderful feedback. Over the last few months I've been playing with many of you and implementing the best of everybody's suggestions. So, thank you, HN for all your help! I feel this is an extreme overhaul I couldn't have done without your input. Since then, I have: Dramatically improved our hosting platform (So it HOPEFULLY won't go down this time (oops.)), Added two new units, Rebalanced all existing units, Added many more maps, Improved the…
- WBWe built an AI to review your pull requests2025 · infinitcode.ai · ▲53
Hey HN, We’re two developers (co-founders) with a team of 20 who got tired of spending hours reviewing PRs, so we built Infinitcode.ai, an AI-powered code reviewer that: - *Summarizes PRs in plain English*: No more deciphering 1,000-line diff jungles - *Catches more than bugs*: Security holes, performance pitfalls, code smells, even typos (yes, we’ll flag “vurnerabilities” and vulnerabilities) - *Zero onboarding*: Works instantly—no “let me learn your codebase for weeks” nonsense. Why we’re posting: We’re in alpha and need brutal honesty. Roast our tool, mock our UI, or tell us why AI will…
- ABAutomated bug fixing powered by LLMs2023 · resolvd.ai · ▲9
Hey everyone, My friend and I built a simple bug fixing app that listens for alerts/issues from Sentry, contextualizes it against your codebase, and any other data sources you wish to connect (right now we support Notion, Google Docs, and Slack), and deploys an ai agent to write a PR for review in Github or Gitlab to solve the bug. Our current demo shows the end-to-end process for a trivial bug fix, but we have been testing it with open source python repos like http-pie, comparing how our agent solves a bug compared to a human engineer and it gets fairly close. We are working on adding…
- TITilth – I spent tokens so my agents would stop wasting them (~4k Rust)Feb 2026 · github.com · ▲10
I'm an "ideas person" who messes around with AI on a low budget. I got tired of watching my tokens vanish and context windows filling up while agents fumbled around trying to find the right thing. Agents don't flail like they used to with shell tools, but there are still weak/blind spots and back-and-forth episodes — especially when using tools in combination/sequence. So I built "tilth" today. Or rather, AI built it — every line is Opus 4.6. I spent a lot of my precious tokens getting it to "not shit" (at least several of the different vendors' AI overlords assure me it's not…
- IMI'm building an AI tool that turns Design Systems into React components2024 · robustlaunch.com · ▲8
Hi HN! Solo developer here. 10 days ago, I started building this after spending countless hours copying/pasting marketing sections and fighting to keep them consistent with our design system. I wondered: "What if AI could understand our design system and generate React components that actually match it?" Current progress (10 days in): - Can generate hero sections that follow your design tokens - Uses your actual component variants and styles - Works with Next.js, Tailwind, shadcn/ui It's very early days, but I'm excited to share it with other devs who: - Are tired of rebuilding…
More ai this month
the category →
I trained a 125M-parameter transformer to autocomplete piano performances in real time (~108 notes/sec on an iPhone 15). The idea is basically GitHub Copilot or Tabnine, except instead of prompting it with code, you prompt it by playing a few notes on a MIDI piano. The model then continues what you played, entirely on-device. The app is free if anyone wants to try it. Happy to answer questions about the model, training, Core ML, or the many things that didn't work.
AI · 17d ago · simedw.com
Astute▲585Automate your B2B brand going viral, with new media creators
AI · 18d ago · company-app.joinastute.com
Hey HN, Henry from Cactus here! We previously released Cactus Needle, a 14MB agentic LLM for tool call, device use, and structured extraction for phones, wearables, smart homes, small robots and microcontrollers. We got really great feedback here, and have now incorporated the suggestions to release Needle 2. The whole model is a single 14MB binary that runs a full session in 28MB of RAM; 45m parameters at 2bit compression. Needle hits 500 tokens/sec decode speed on a Raspberry Pi 5, sits between 400-1,500 tokens/sec on VR devices like Meta Quest 3S and Apple Vision Pro, and ranges…
AI · 27d ago · cactuscompute.com
Launched alongside, May 2025
the whole month →
- C9
Life & fun · 2025 · felixrieseberg.github.io
