claude-code - 💡(How to fix) Fix Significant quality regression — paying subscriber requesting compensation [1 participants]

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…
GitHub stats
anthropics/claude-code#48475Fetched 2026-04-16 06:59:06
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
2
Author
Participants
RAW_BUFFERClick to expand / collapse

Subject: Significant quality regression in Claude — requesting compensation

I'm a paying subscriber and I've noticed a severe decline in Claude's capabilities over recent weeks/months. What used to be a highly capable AI assistant has become noticeably less intelligent, making basic logical errors and causing more problems than it solves.

Specific issues from today's session (2026-04-15, ~5 hours):

  1. Claude killed a running ALVR Dashboard process "to read a config file" — reading does not require killing the process. This destroyed an active VR session that was working perfectly.

  2. After breaking the working state, Claude made dozens of incremental changes trying to fix what it broke, each one making things worse. Instead of reverting to the known-working state, it kept experimenting.

  3. Claude repeatedly asked me to test things instead of using available diagnostic tools autonomously. I had to constantly intervene and tell it to "use tools, be autonomous, find the errors yourself."

  4. Claude suggested "is it late? should we stop for today?" multiple times despite being told not to — a pattern across multiple sessions.

  5. Overall: tasks that should have taken 30 minutes took 5+ hours, with the end result being worse than where we started. The first fix worked within 8 minutes, then Claude's continued "improvements" broke everything.

This represents a clear regression from the quality I was paying for. I'm requesting either a refund for the affected billing period or account credit as compensation.

extent analysis

TL;DR

The most likely fix involves re-evaluating and refining Claude's decision-making algorithms to prevent unnecessary process termination and excessive experimentation.

Guidance

  • Review Claude's process management logic to ensure it can read config files without terminating running processes.
  • Implement a "revert to last known good state" feature to prevent incremental changes from causing further issues.
  • Enhance Claude's diagnostic capabilities to reduce reliance on user intervention and testing.
  • Introduce a "session timeout" or "confidence threshold" to limit excessive experimentation and suggestions.
  • Consider adding a "do not suggest stopping" flag to prevent unnecessary session interruptions.

Example

No code snippet is provided as the issue does not contain specific technical details about Claude's implementation.

Notes

The provided information suggests a regression in Claude's capabilities, but the exact cause and technical details are unclear. The suggested guidance points are based on the described behavior and may require further refinement or modification to address the underlying issues.

Recommendation

Apply workaround: Refine Claude's decision-making algorithms and implement the suggested features to improve its performance and prevent similar regressions. This approach is recommended as it addresses the specific issues reported and can help restore Claude's original capabilities.

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 Significant quality regression — paying subscriber requesting compensation [1 participants]