I like the premise but trying to be both the coding agent + the monitoring agent seems backwards. Your tool will mostly only be valuable IF it is the best coding agent out there. You're going to be competing against companies where automated PR agents are their sole product, and you're probably going to lose.

Do one thing and do it right.

Where I could see this succeeding is if you embrace the monitoring agent role. Customers can expose their coding agents, setup however they like, as an MCP server that your monitoring agent can plug into. If something goes wrong, your monitoring agent gives their coding agent the best context it can, and steps out of the way.

I really like this premise.

Recently I have had trouble with Sentry. I have a site that has a lot of data coming in (2M page views per month) and Sentry starts being unusable for a solo developer. And on the other hand, I have several Django projects where I want to have common way to handle bugs.

I am feeling Sentry UI is too complex for my use cases, and on the other hand, I would like to automate the process as much as possible -- and the idea of automatic bug fixing is neat!

I am experimenting with Bugsink. Supporting Bugsink internally but build some tooling around it for automatic bug detection and fixing would actually be a sweet spot for me.