[BUG] Pasting paths to images destroys the current chat

Status Fixed / completed
Maintainer reply ✓ Yes — dicksontsai
Activity 6 comments · opened May 20, 2025 · closed May 24, 2025
💡 Likely answer: A maintainer (dicksontsai, collaborator) responded on this thread — see the highlighted reply below.

Environment

  • Platform (select one):
  • [x] Anthropic API
  • [ ] AWS Bedrock
  • [ ] Google Vertex AI
  • [ ] Other: <!-- specify -->
  • Claude CLI version: <!-- output of claude --version --> 0.2.122
  • Operating System: <!-- e.g. macOS 14.3, Windows 11, Ubuntu 22.04 --> Ubuntu 24.04
  • Terminal: <!-- e.g. iTerm2, Terminal App --> GNOME Terminal

Bug Description

<!-- A clear and concise description of the bug -->

Steps to Reproduce

  1. <!-- First step --> Paste a path to a JPEG image
  2. <!-- Second step --> Claude replaces the path with [Image # 1]
  3. <!-- And so on... -->

Expected Behavior

<!-- What you expected to happen -->
Claude would take the path and include the string in the conversation as relevant context

Actual Behavior

<!-- What actually happened -->
Claude replaced it with [Image #1], and all subsequent responses become:

API Error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"messages.0.content.1.image.source.base64.data: Image does not match the 
    provided media type image/png"}}

Additional Context

Please add a setting or config to disable this feature.

View original on GitHub ↗

6 Comments

wanderingnature · 1 year ago

Can confirm same error on Mac OS. You must fully restart the session, current session cannot continue.

wanderingnature · 1 year ago

this was fixed for some time today and not it is broken again - really inconvenient not to be able to use images

sankalpsingha · 1 year ago

facing the same issue.

dicksontsai collaborator · 1 year ago

Fixed in v1.0.3. You should now be able to paste in jpg paths as images.

mceachen · 1 year ago

@dicksontsai excellent, thank you! Kudos to the team, Claude and cc are game changers.

github-actions[bot] · 1 year ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.