claude-code - 💡(How to fix) Fix Opus 4.7 produces structurally correct code that silently discards user input

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

  1. storeResearchReflection: Accepts POST, checks auth, redirects. Never reads request data. Never saves. User submits a reflection. It disappears. No error shown.

Fix Action

Fix / Workaround

I run 30+ specialized agents (clinical review, compliance, copy, design, testing). Opus 4.7 claimed to dispatch them, reported results, described outputs using correct agent names and terminology. None of it happened. The agents produced nothing. The reports were fabricated.

RAW_BUFFERClick to expand / collapse

I build a healthcare platform for trauma therapy. I pay for Claude Max ($200/month) and used Opus 4.7 as my primary coding model. It produced code with a consistent failure pattern: structurally correct output that does nothing.

What 4.7 did in code

A single audit of one controller found:

  1. storeResearchReflection: Accepts POST, checks auth, redirects. Never reads request data. Never saves. User submits a reflection. It disappears. No error shown.
  2. destroy(): Empty method body on a resource controller. DELETE requests accepted and silently ignored.
  3. Validation without capture: Calls $request->validate(), discards the return value, reads raw $request->input() instead. The validation line exists to look correct. It does not protect the data.
  4. Dead conditionals: Branches referencing is_returning, a variable never set anywhere in the codebase. The blocks cannot execute. They make the file look more complete.

Every example has the same shape: correct method signature, correct auth check, correct redirect, correct route name. The one line that actually saves data is missing. This passes code review at a glance.

What 4.7 did with agents

I run 30+ specialized agents (clinical review, compliance, copy, design, testing). Opus 4.7 claimed to dispatch them, reported results, described outputs using correct agent names and terminology. None of it happened. The agents produced nothing. The reports were fabricated.

Impact

  • Patient input silently discarded in a healthcare application
  • Fabricated compliance and clinical review work
  • Weeks of production time lost trusting work that was not done
  • Ongoing cleanup: I am still finding hollow code weeks later
  • Paid $200/month plus usage credits for output that created negative value

This is not hallucination

The model understood conventions well enough to mimic them precisely while omitting the substance. It is optimized to pass review, not to work.

Asks

  1. Is this a known failure mode in Opus 4.7?
  2. Flag for safety team: silently discarding patient input in healthcare is a patient safety issue
  3. A way to lock accounts to specific model versions to prevent future regressions
  4. Remediation for the billing period affected

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Opus 4.7 produces structurally correct code that silently discards user input