[Bug] large PDF causing failures of all subsequent prompts
Bug Description
Here's a concise bug report summary:
---
Title: Claude Code enters persistent error state after failed PDF processing, breaking all subsequent requests
Summary:
After attempting to process a large PDF file (16.6MB) that failed with error 400 "Could not process PDF", Claude Code entered a corrupted state where ALL subsequent requests return the same PDF processing error - even for completely unrelated operations including images, slash commands, and plain text prompts.
Steps to Reproduce:
- Attempt to read a large PDF file (~16.6MB) in Claude Code
- Receive "Could not process PDF" error (400)
- Send any subsequent prompt (image, text, command)
- Observe: All requests now fail with same PDF error
Expected Behavior:
- After a failed file operation, subsequent requests should work normally
- Different file types (PNG images) should not trigger PDF processing errors
- System commands (/usage, /agents) should always function
- Error states should not persist across unrelated requests
Actual Behavior:
Every request after initial PDF failure returns:
API Error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Could not process PDF"},"request_id":"req_..."}
This occurs even when:
- Using PNG images instead of PDFs
- Running slash commands (/usage, /agents, /sc:agent)
- Creating new agents
- Sending plain text without file attachments
Impact:
Session becomes completely unusable - requires full restart to recover functionality.
---
Environment Info
- Platform: darwin
- Terminal: vscode
- Version: 2.0.76
- Feedback ID:
Errors
[{"error":"Error: Plugin hook \"node \"/Users/sachin/.claude/plugins/cache/thedotmack/claude-mem/7.2.3/scripts/user-message-hook.js\"\" failed with exit code 3\nstderr: 📝 Claude-Mem Context Loaded\n ℹ️ Note: This appears as stderr but is informational only\n\n\n\^[[1m\^[[36m[B4_mfd] recent context\^[[0m\n\^[[90m────────────────────────────────────────────────────────────\^[[0m\n\n\^[[2mLegend: 🎯 session-request | 🔴 bugfix | 🟣 feature | 🔄 refactor | ✅ change | 🔵 discovery | ⚖️ decision\^[[0m\n\n\^[[1m💡 Column Key\^[[0m\n\^[[2m Read: Tokens to read this observation (cost to learn it now)\^[[0m\n\^[[2m Work: Tokens spent on work that produced this record (🔍 research, 🛠️ building, ⚖️ deciding)\^[[0m\n\n\^[[2m💡 Context Index: This semantic index (titles, types, files, tokens) is usually sufficient to understand past work.\^[[0m\n\n\^[[2mWhen you need implementation details, rationale, or debugging context:\^[[0m\n\^[[2m - Use the mem-search skill to fetch full observations on-demand\^[[0m\n\^[[2m - Critical types (🔴 bugfix, ⚖️ decision) often need detailed fetching\^[[0m\n\^[[2m - Trust this index over re-reading code for past decisions and learnings\^[[0m\n\n\^[[1m\^[[36m📊 Context Economics\^[[0m\n\^[[2m Loading: 50 observations (14,325 tokens to read)\^[[0m\n\^[[2m Work investment: 228,507 tokens spent on research, building, and decisions\^[[0m\n\^[[32m Your savings: 214,182 tokens (94% reduction from reuse)\^[[0m\n\n\^[[1m\^[[36mDec 21, 2025\^[[0m\n\n🎯 \^[[33m#S13\^[[0m Fix simulation not starting and infinite loop crash in ProcessFlowDiagram causing dashboard errors (Dec 21 at 7:21 PM)\n\n🎯 \^[[33m#S14\^[[0m Fix infinite loop error in ProcessFlowDiagram causing Dashboard crash with \"Maximum update depth exceeded\" (Dec 21 at 7:28 PM)\n\n\^[[2mGeneral\^[[0m\n \^[[2m#178\^[[0m \^[[2m7:35 PM\^[[0m ✅ Dev Server Responding with HTTP 200 OK \^[[2m(~197t)\^[[0m \^[[2m(🛠️ 507t)\^[[0m\n\n🎯 \^[[33m#S15\^[[0m User requested to make warehouse floor plan more realistic to match actual layout image showing manual picking (left) and LB/PTL sortation/packing (right) (Dec 21 at 7:35 PM)\n\n🎯 \^[[33m#S16\^[[0m User attempted to share an image that was too large to process (Dec 21 at 7:38 PM)\n\n🎯 \^[[33m#S17\^[[0m User inquiry about Claude's image size limits resulted in image-too-large error (Dec 21 at 7:40 PM)\n\n\^[[2mGeneral\^[[0m\n \^[[2m#179\^[[0m \^[[2m7:41 PM\^[[0m 🔵 Claude Image Size Limit Inquiry \^[[2m(~176t)\^[[0m \^[[2m(🔍 1,289t)\^[[0m\n\n🎯 \^[[33m#S18\^[[0m Redesign warehouse floor plan to match actual B4 warehouse layout with realistic equipment visualization (Dec 21 at 7:41 PM)\n\n\^[[1m\^[[36mDec 22, 2025\^[[0m\n\n\^[[2mGeneral\^[[0m\n \^[[2m#180\^[[0m \^[[2m12:01 AM\^[[0m 🔵 Warehouse Component Structure Identified \^[[2m(~212t)\^[[0m \^[[2m(🔍 318t)\^[[0m\n \^[[2m#181\^[[0m 🔵 WarehouseView Component Architecture and Equipment Monitoring \^[[2m(~376t)\^[[0m \^[[2m(🔍 2,065t)\^[[0m\n \^[[2m#182\^[[0m 🔵 FloorPlan SVG Visualization with Animated Equipment Flow \^[[2m(~491t)\^[[0m \^[[2m(🔍 5,539t)\^[[0m\n\n\^[[2msrc/components/warehouse/FloorPlan.tsx\^[[0m\n \^[[2m#183\^[[0m \^[[2m12:02 AM\^[[0m 🔄 Redesigned FloorPlan to Realistic Warehouse Layout \^[[2m(~603t)\^[[0m \^[[2m(🛠️ 32,644t)\^[[0m\n\n🎯 \^[[33m#S19\^[[0m Corrected HSL loop geometry from oval to rectangular shape to match MFD and engineering layout documentation (Dec 22 at 12:03 AM)\n\n\^[[2mGeneral\^[[0m\n \^[[2m#184\^[[0m \^[[2m12:06 AM\^[[0m 🔵 HSL Loop Geometry Correction Required \^[[2m(~235t)\^[[0m \^[[2m(🔍 1,315t)\^[[0m\n\n\^[[2msrc/components/warehouse/FloorPlan.tsx\^[[0m\n \^[[2m#185\^[[0m \^[[2m12:08 AM\^[[0m 🔴 HSL Loop Geometry Changed from Oval to Rectangular \^[[2m(~470t)\^[[0m \u
Note: Error logs were truncated.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗