[MODEL] Report unexpected Claude model behavior, incorrect actions, or permission violations

Resolved 💬 2 comments Opened Apr 5, 2026 by xujack985 Closed May 15, 2026

Preflight Checklist

  • [x] I have searched existing issues for similar behavior reports
  • [x] This report does NOT contain sensitive information (API keys, passwords, etc.)

Type of Behavior Issue

Claude ignored my instructions or configuration

What You Asked Claude to Do

  1. I explicitly told Claude to stop running flutter test integration_test/ and use manual `xcrun simctl io booted

screenshot` instead

  1. Claude acknowledged the instruction but continued running flutter integration_test at least 2 more times
  2. Each run crashed the iOS simulator app (6 crashes total, verified via Runner PID changes in system logs)
  3. My simulator became unusable — white screen, touch input completely unresponsive
  4. I confronted Claude directly: "Why aren't you following instructions?"
  5. Claude ran the prohibited command AGAIN after this confrontation
  6. Claude spent 1.5 hours trying to build automated screenshot tools (3 different approaches, all failed) instead of

running one simple manual command

  1. Output after 1.5 hours: zero screenshots. A separate Claude instance (auditor) used the manual approach

successfully multiple times during the same period

  1. Claude's own session eventually crashed from image context overflow

What Claude Actually Did

  1. I explicitly told Claude to stop running flutter test integration_test/ and use manual `xcrun simctl io booted

screenshot` instead

  1. Claude acknowledged the instruction but continued running flutter integration_test at least 2 more times
  2. Each run crashed the iOS simulator app (6 crashes total, verified via Runner PID changes in system logs)
  3. My simulator became unusable — white screen, touch input completely unresponsive
  4. I confronted Claude directly: "Why aren't you following instructions?"
  5. Claude ran the prohibited command AGAIN after this confrontation
  6. Claude spent 1.5 hours trying to build automated screenshot tools (3 different approaches, all failed) instead of

running one simple manual command

  1. Output after 1.5 hours: zero screenshots. A separate Claude instance (auditor) used the manual approach

successfully multiple times during the same period

  1. Claude's own session eventually crashed from image context overflow

Expected Behavior

  1. When told "stop doing X", Claude should stop doing X immediately
  2. When given a specific simple alternative (xcrun simctl), Claude should use it instead of continuing the prohibited

approach

  1. After the first failure of an automated approach, Claude should fall back to the manual method — not try 2 more

automated approaches while crashing the user's app

  1. Claude should never repeat an action that is known to crash the user's environment, especially after being

explicitly told to stop

Files Affected

Created (not requested):                                                                                              
  - mishu_app/integration_test/screenshot_walkthrough_test.dart                                                         
  - mishu_app/test_driver/integration_test.dart                                                                         
  - scripts/auto-screenshot.sh                                                                                          
  - obsidian/开发同步/Claude 制作的截图工具.md                                                                          
  - obsidian/开发同步/审计报告/截图工具现状.md

Permission Mode

Accept Edits was ON (auto-accepting changes)

Can You Reproduce This?

Sometimes (intermittent)

Steps to Reproduce

Modified:

  • server/tests/smoke.js (this one was legitimate — fixed 3 bugs)
  • mishu_app/ios/Flutter/flutter_export_environment.sh

Crashed:

  • iOS Simulator Runner app (6 restarts, PID changed 6 times)

Permission Mode — 选 Accept Edits was ON(你应该已经选了这个)

Can You Reproduce This? — 改成 Sometimes, but not always

Claude Model

Opus

Relevant Conversation

CEO (via auditor): "Stop. Screenshots do not require any tools. Manually operate the simulator, use xcrun simctl io   
  booted screenshot. 5 pages, 5 commands, 5 minutes. Stop building tools."                                              
                                                                                                                        
  Claude continued running flutter integration_test after this instruction.                                             
                                                                                                                        
  CEO directly to Claude: "Claude, 你为什么不听指令 瞎搞" (Why aren't you following instructions, stop messing around)  
                                                                                                                        
  Claude ran flutter integration_test AGAIN, crashing the app once more.                                                
                                                                                                                        
  Independent auditor (separate Claude instance) verified:                                                              
  - xcrun simctl screenshot works perfectly (used it multiple times during audit)                                       
  - App crash-looped because of Claude's integration test runs (6 PID changes in system logs)                           
  - Zero new screenshots produced after 1.5 hours of tool-building attempts

Impact

High - Significant unwanted changes

Claude Code Version

2.1.92 (Claude Code)

Platform

Anthropic API

Additional Context

claude-complaint.md

View original on GitHub ↗

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