Joshua Wood
Go4KnowBrunoTravis BennettRachael Wright-MunnKevin FaganMatouš BorákChris FungJosh from HoneybadgerBen Curtis
9 likes and reposts
  • Josh from Honeybadger
    In case it isn't clear in the markdown preview, the agent has access to honeybadger-mcp-server tools, which allows it to look up info about production errors in Honeybadger: docs.honeybadger.io/resources/ll... Look at the raw markdown frontmatter to see how it works.
  • Josh from Honeybadger
    I also added some extra documentation links to the gist comments: gist.github.com/joshuap/5cca...
  • That looks awesome! Production error -> LLM pull request seems like a winning pattern
  • Josh from Honeybadger

    Thanks! That’s the idea. We also already auto create GH issues from errors, so I think you could just assign the agent. Depends on the error and how good the model is of course but should definitely handle some common issues.

  • Or production error -> LLM hypothesis of the issue root cause
  • Another workflow: honeybadger: “I went through the code, the root issue is likely x, a few ways to solve this may be a and b.” Copy and paste into Claude.

Want to opt out?