[BUG] Opus 4.7 "Could not process image" 400 error breaks session

Resolved 💬 3 comments Opened Apr 20, 2026 by tjdghksdl442-droid Closed Apr 24, 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?

Opus 4.7에서 이미지 붙이면 400 에러 뜨고 그 세션 영구 먹통됨.
4.6은 멀쩡함.

Error: 400 "Could not process image"
request_id: req_011CaEaoucmjcQnYFkVH1Zm3

환경:

  • Claude Code 2.1.104
  • macOS 15.7.4
  • Model: claude-opus-4-7

재현: 새 세션 시작 → 1시간 안에 발생 → 이후 모든 메시지 실패

<img width="863" height="243" alt="Image" src="https://github.com/user-attachments/assets/904f59f5-d429-43a5-9c73-abe17f218273" />

What Should Happen?

[한국어]
이미지 처리 실패 시에도 세션이 살아있어야 함. 실패한 이미지 하나 때문에 전체 세션이 먹통되면 안 됨. 4.6처럼 4.7도 이미지를 안정적으로 처리해야 함.

[English]
Image processing failures should not break the entire session. A single failed image should be removed from history or fall back to text. Opus 4.7 should handle images as reliably as 4.6.

Error Messages/Logs

API Error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Could not process image"},"request_id":"req_011CaEaoucmjcQnYFkVH1Zm3"}

Steps to Reproduce

[한국어]

  1. claude-opus-4-7 모델로 새 세션 시작
  2. 이미지 첨부해서 대화 진행
  3. 1시간 이내에 400 에러 발생
  4. 이후 그 세션의 모든 메시지가 같은 에러로 실패
  5. Opus 4.6에서는 발생 안 함

[English]

  1. Start a new session with claude-opus-4-7
  2. Attach images (screenshots) during conversation
  3. 400 error "Could not process image" occurs within 1 hour
  4. All subsequent messages in the session fail with the same error
  5. Does not occur with claude-opus-4-6

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.104

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 ↗