1 min lesson
Honesty beats a confident bluff
For each case in "Honesty beats a confident bluff", name the signal and the response you would use.
Step 1 of 2
Honesty beats a confident bluff
Cursor's behavior shifts as models and the product ship weekly, so you will routinely answer tickets where you don't yet know the cause. Bluffing a fix that doesn't hold is the fastest way to lose a developer's trust and they will catch it within one reply.
State the confirmed facts plainly.
"This is a known regression in 1.2 indexing on large monorepos."
Name the open question and how you're chasing it.
"I'm reproducing on a Windows + WSL setup to confirm it's not proxy-specific."
Say so, with a timeline, not a guess dressed as a fact.
"I don't have a root cause yet; I'll have an update by EOD Thursday."
Give them something to do now while the real fix lands.
"Reindex to restore it: quit Cursor, delete .cursor/index in the workspace and relaunch."