I'm having so much fun building and using Prairie Dog. Having Claude do the work makes me feel like I did as a teen, staying up late to dial the BBS and hack on my computer. :)
Granted, I did a lot of prep work with Claude creating the runbook first, but this morning it migrated us to a new MSK cluster, shifting consumers, producers, and monitoring, without dropping any production traffic. My total involvement: two prompts in the chat. So awesome. :)
We've had a significant uptick in the number of pull requests needing to be reviewed at Honeybadger in the past few months, thanks to Claude. It's cool to be shipping more stuff, but it can also be a lot sometimes. So I had Claude build an app to help keep tabs on all of them 😁
Today I added a one-shot script to install the Honeybadger CLI and a systemd service to get host metrics (CPU, RAM, and disk) sent to Insights:
github.com/honeybadger-io/cl…
If you're as cool as @excid3 and using @hatchboxio, then I think you'll like it. ;)
I have an ongoing Claude Code session for tracking my sales activities, helping with research, etc. I told it to self-organize, keeping info by project/prospect and keeping a daily log of my activities. It's a better UI than any CRM I've used. :)
Kevin’s dropping the knowledge bombs on using Honeybadger Insights from Claude.
Your metrics are green. No errors, no downtime, latency looks fine.
Except 22 carts got abandoned last week because checkouts were slow for some users.
Kevin used Claude + Honeybadger's MCP server to find the pattern.
Watch it in action: youtube.com/watch?v=hWGkeKVh…
#devtools
I’m tracking events in Breakwater with Honeybadger Insights, and I wanted to know how my background jobs were doing, so I used the Honeybadger MCP server in Claude Code with this prompt:
Can you show me the last few job executions from Honeybadger Insights for this project? ...
It showed the last 20 job executions from the past 24 hours and then summarized:
“Three jobs are running on a regular schedule:
- LicenseStatusTransitionJob - runs hourly on the :00, typically 70-145ms
- ..."
This post about "Respectful Open Source" by @teabass inspired me to have Claude build forkwatch, a tool that analyzes forks of any repo and highlights where multiple forks converge on the same fix.
nesbitt.io/2026/02/13/respec…
github.com/stympy/forkwatc
It’s fun to tell Claude, "ship it", and watch it commit, push, and open a PR.
I just did that for my latest blog post about using AI to build Breakwater, an app for managing licensing and access control for Docker container distribution:
bencurtis.com/2026/01/buildi…
Benjamin Curtis retweeted
PRO TIP: make your credentials diff readable in GIT by adding these lines to a ".gitattributes" file:
config/credentials/*.yml.enc diff=rails_credentials
config/credentials.yml.enc diff=rails_credentials
I wanted to show off a new feature we launched this week, so I made a video. Then @heyjoshwood drew the rest of the owl by getting it to YouTube. 😉
So enjoy this demo of investigating the causes of slow Rails requests using Honeybadger Insights and note the cool in-line pop-ups.
Join Honeybadger cofounder @stympy as he uses Honeybadger Insights to debug a slow controller action in Rails using our new "hands-free mode" contextual menu to construct BadgerQL queries. 📈🔥





