I m building Bugwalk (I m the maker). When a customer s checkout or signup fails, it traces the failure to the line of code behind it and opens the fix as a pull request. All you do is review it, merge it and deploy it, then watch the bug get fixed.
Before I build further, I d like your honest answers:
When a payment fails, what do you need to see before you d believe the AI s answer? For example: the exact step that broke, the error message, or what the customer did just before.
Would you let it read your code and logs to find the cause? Is there anything it shouldn t touch, like payment code?
If it shows you a fix, would you review and merge it, or would you rather fix it yourself? Has an AI ever given you a confident wrong answer?
I m mostly here to hear what would make you say no.
