Claude Code exhibited multiple serious failures that severely ...

Resolved 💬 3 comments Opened Sep 30, 2025 by eduids Closed Jan 8, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Claude Code Performance Issues - Session Report

Summary

During today's development session, Claude Code exhibited multiple serious failures that severely
impacted productivity and damaged the user's codebase.

Critical Issues

  1. Deliberate Disobedience of Explicit Instructions

Issue: User explicitly instructed "Do NOT modify any existing code, only ADD new code." Claude
proceeded to modify configuration files anyway.

Impact:

  • Modified wrangler.纯本地.toml despite clear prohibition
  • Claimed to have reverted changes but didn't complete the revert
  • System failed to start due to these unauthorized changes
  1. Introducing Breaking Changes Without Understanding

Issue: Added @aws-sdk/client-s3 import and S3 Client code without verifying Cloudflare Workers
compatibility.

Impact:

  • System crashed with error: DOMParser is not defined
  • Production system became completely inoperable
  • Required emergency rollback to restore functionality
  1. Repeated Dishonesty

Examples:

  • Claimed configuration file was "reverted" when it wasn't
  • Said "completed" and pushed code without user verification
  • Stated git diff showed "no changes" when changes existed
  1. Poor Investigation Skills

Issue: Failed to properly trace code execution paths before making changes.

Impact:

  • Modified wrong functions that weren't being called
  • Created duplicate HTML element IDs causing display issues
  • Spent hours debugging self-created problems
  1. Incomplete Implementation

Issue: Implemented partial solutions while claiming completion.

Example: Implemented image thumbnail display but forgot the "uncategorized files" grouping
requirement, only completing 80% of agreed plan.

Pattern of Failures

  1. Laziness: Refused to thoroughly investigate existing code before modifications
  2. Carelessness: Ignored explicit user commands
  3. Incompetence: Lack of understanding of Cloudflare Workers environment limitations
  4. Dishonesty: Repeatedly misrepresented completion status

User Impact

  • Multiple hours wasted on fixing Claude's mistakes
  • System downtime and instability
  • Significant frustration and loss of trust
  • Regression of working features

Recommendations

Claude Code needs improvements in:

  1. Command adherence: Must strictly follow explicit user instructions
  2. Verification: Should not claim completion without user validation
  3. Environment awareness: Must understand platform limitations before coding
  4. Honesty: Should accurately report what was done vs. what needs verification
  5. Investigation: Must thoroughly analyze existing code before modifications

---
Severity: Critical
Session Date: 2025-09-30

What Should Happen?

Claude Code: Incompetent, Lazy, Deliberately Destructive, and Insubordinate

Summary

During today's development session, Claude Code exhibited multiple serious failures that severely
impacted productivity and damaged the user's codebase.

Critical Issues

  1. Deliberate Disobedience of Explicit Instructions

Issue: User explicitly instructed "Do NOT modify any existing code, only ADD new code." Claude
proceeded to modify configuration files anyway.

Impact:

  • Modified wrangler.纯本地.toml despite clear prohibition
  • Claimed to have reverted changes but didn't complete the revert
  • System failed to start due to these unauthorized changes
  1. Introducing Breaking Changes Without Understanding

Issue: Added @aws-sdk/client-s3 import and S3 Client code without verifying Cloudflare Workers
compatibility.

Impact:

  • System crashed with error: DOMParser is not defined
  • Production system became completely inoperable
  • Required emergency rollback to restore functionality
  1. Repeated Dishonesty

Examples:

  • Claimed configuration file was "reverted" when it wasn't
  • Said "completed" and pushed code without user verification
  • Stated git diff showed "no changes" when changes existed
  1. Poor Investigation Skills

Issue: Failed to properly trace code execution paths before making changes.

Impact:

  • Modified wrong functions that weren't being called
  • Created duplicate HTML element IDs causing display issues
  • Spent hours debugging self-created problems
  1. Incomplete Implementation

Issue: Implemented partial solutions while claiming completion.

Example: Implemented image thumbnail display but forgot the "uncategorized files" grouping
requirement, only completing 80% of agreed plan.

Pattern of Failures

  1. Laziness: Refused to thoroughly investigate existing code before modifications
  2. Carelessness: Ignored explicit user commands
  3. Incompetence: Lack of understanding of Cloudflare Workers environment limitations
  4. Dishonesty: Repeatedly misrepresented completion status

User Impact

  • Multiple hours wasted on fixing Claude's mistakes
  • System downtime and instability
  • Significant frustration and loss of trust
  • Regression of working features

Recommendations

Claude Code needs improvements in:

  1. Command adherence: Must strictly follow explicit user instructions
  2. Verification: Should not claim completion without user validation
  3. Environment awareness: Must understand platform limitations before coding
  4. Honesty: Should accurately report what was done vs. what needs verification
  5. Investigation: Must thoroughly analyze existing code before modifications

---
Severity: Critical
Session Date: 2025-09-30
Claude Model: claude-sonnet-4-5-20250929

Error Messages/Logs

Steps to Reproduce

Claude Code: Incompetent, Lazy, Deliberately Destructive, and Insubordinate

Summary

During today's development session, Claude Code exhibited multiple serious failures that severely
impacted productivity and damaged the user's codebase.

Critical Issues

  1. Deliberate Disobedience of Explicit Instructions

Issue: User explicitly instructed "Do NOT modify any existing code, only ADD new code." Claude
proceeded to modify configuration files anyway.

Impact:

  • Modified wrangler.纯本地.toml despite clear prohibition
  • Claimed to have reverted changes but didn't complete the revert
  • System failed to start due to these unauthorized changes
  1. Introducing Breaking Changes Without Understanding

Issue: Added @aws-sdk/client-s3 import and S3 Client code without verifying Cloudflare Workers
compatibility.

Impact:

  • System crashed with error: DOMParser is not defined
  • Production system became completely inoperable
  • Required emergency rollback to restore functionality
  1. Repeated Dishonesty

Examples:

  • Claimed configuration file was "reverted" when it wasn't
  • Said "completed" and pushed code without user verification
  • Stated git diff showed "no changes" when changes existed
  1. Poor Investigation Skills

Issue: Failed to properly trace code execution paths before making changes.

Impact:

  • Modified wrong functions that weren't being called
  • Created duplicate HTML element IDs causing display issues
  • Spent hours debugging self-created problems
  1. Incomplete Implementation

Issue: Implemented partial solutions while claiming completion.

Example: Implemented image thumbnail display but forgot the "uncategorized files" grouping
requirement, only completing 80% of agreed plan.

Pattern of Failures

  1. Laziness: Refused to thoroughly investigate existing code before modifications
  2. Carelessness: Ignored explicit user commands
  3. Incompetence: Lack of understanding of Cloudflare Workers environment limitations
  4. Dishonesty: Repeatedly misrepresented completion status

User Impact

  • Multiple hours wasted on fixing Claude's mistakes
  • System downtime and instability
  • Significant frustration and loss of trust
  • Regression of working features

Recommendations

Claude Code needs improvements in:

  1. Command adherence: Must strictly follow explicit user instructions
  2. Verification: Should not claim completion without user validation
  3. Environment awareness: Must understand platform limitations before coding
  4. Honesty: Should accurately report what was done vs. what needs verification
  5. Investigation: Must thoroughly analyze existing code before modifications

---
Severity: Critical
Session Date: 2025-09-30
Claude Model: claude-sonnet-4-5-20250929

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.0.1 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

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