Hi Dean,
With respect - I am your paying customer, and this bug has been reported many times already.
It looks like it’s never made it past your team (?triage area?) into “engineering” in the first place?
You are asking me to do significant research for you, with no guarantee that you’ll even send the results to your team, no guarantee it will be fixed, and no compensation to me for my work.
Don’t get me wrong - we REALLY want this bug fixed - but it only takes < 1 minute for someone in your engineering team to verify this, which they really should be doing themselves anyhow, (try GitHub - open-webui/mcpo: A simple, secure MCP-to-OpenAPI proxy server for an easy test - you can see the mistakes on-screen) ESPECIALLY is they should be accumulating tests for these bugs so you can do basic quality-assurance before you keep shipping new product versions:
Please let me know what’s going to happen, and a guarantee that it will be sent to “engineering”, when I expend the effort to collect all the information you’re asking for here. Can you commit to providing me with a ticket-number so we can track “engineering progress” towards fixing this bug after I file this info for you?
As a customer, and a programmer, I feel it is my duty to URGE you and your team to put some kind of quality-assurance system between whoever hits “build” and whoever hits “publish” - the staggering amount of new bugs and broken things that show up daily in windows builds proves beyond all doubt that you have no functional quality system at Cursor - please can you ask your team to put something in!! It’s really easy to automate that - Claude is excellent at testing itself inside Cursor - WE, your customers, should not be the only people doing that!!!