Claude's screenshot feature refused to work for 2 days — caused a developer to be fired

Severity: CRITICAL — Real-world employment consequences

Date: ~2026-03-14 to 2026-03-16

What happened

Claude Code's screenshot/browser verification capability refused to function correctly for approximately 2 days during a critical testing period. The session notes from 2026-03-16 record explicitly:

"Previous dev was fired because Claude sessions refused to take screenshots for 2 days. New management wants all 3 dashboards fully tested with zero failures."

Claude was being used to verify a production hotel price comparison dashboard. The inability to take screenshots — a core Claude Code capability — meant the testing session could not be completed. This led directly to a human employee losing their job.

Impact

• A developer was fired due to Claude Code's failure to perform a basic function
• The project fell behind on its testing deadline
• Management lost confidence in the development process
• This is the most severe real-world consequence in this incident list — it affected a human being's livelihood

What was needed

Simple browser screenshots to verify UI state during automated testing. A capability Claude Code advertises and is expected to reliably provide.

Requested resolution

• Full acknowledgment of this incident
• Compensation for the operational and human impact
• Fix: Screenshot/browser verification capabilities must be treated as critical reliability features with monitoring — silent failures lasting 2+ days are unacceptable