Instead of taking a credit for each response whether the response is accurate or not, give the user the ability to approve the the credit use. I don’t want to pay for code that doesn’t work. if it works i have no problem paying for it. add a “good info” or “bad info” button, that decides a “credit taken” or “credit not taken” rule. if a user keeps selecting “bad info” try to rewrite their code. this will keep them from spoofing the system because they will not be able to advance the code within Cursor for a polished app.
What is stopping the user from copying the good code and flagging the bad code, this wont work and people will just abuse it.
its has to have the smarts to recognize thats happening. disable the user if code is constantly being generated but never accepted or dont advance until its accepted or denied. chances of getting good code 1st time is rare.it can work if you put an effort into figuring out the logic.
1 Like