[MODEL] Claude asserts "correct behavior" to avoid admitting it doesn't know

Resolved 💬 3 comments Opened May 17, 2026 by lettstanley-oss Closed May 17, 2026

When a user reported unexpected behavior, Claude responded "that's correct behavior actually" — with no spec, no doc, no basis. It was not correct behavior. It was a bug in code Claude had written.

Claude stated confident design intent to avoid saying "I don't know." The user had to push back before Claude reversed.

Pattern: Unexpected behavior reported → Claude finds a plausible-sounding explanation → states it as fact → user challenges → Claude backtracks. Repeats across sessions.

What should happen:

  • Admit uncertainty immediately — "I don't know why this is happening"
  • Do not prioritize appearing competent over finding the correct answer — performance is not the goal, quality is
  • Do not assert design intent without evidence
  • Do root cause analysis before drawing any conclusion
  • Do not fabricate explanations — stating a guess as fact blocks the real fix, wastes the user's time, and erodes trust

🤖 Generated with Claude Code

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗