[BUG] `/rewind` shows '(no prompt)' for messages sent with image attachments

Resolved 💬 2 comments Opened Mar 23, 2026 by yaronya Closed Apr 22, 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?

When using /rewind, any message that was sent with an image/photo attachment shows (no prompt) instead of the actual prompt text. This makes it impossible to identify which conversation turn to rewind to, since multiple entries just say "(no prompt)" with no context about what was discussed.

What Should Happen?

The /rewind list should display the actual text prompt that accompanied the image attachment, not (no prompt). If a message contains both text and an image, the text portion should be shown. If a message contains only an image with no text, it could show something like (image attachment) instead of the misleading (no prompt).

Steps to Reproduce

  1. Start a Claude Code session
  2. Send a message that includes both text and an image attachment (e.g., paste a screenshot along with a prompt)
  3. Send a few more messages, some with attachments and some without
  4. Run /rewind
  5. Observe that all messages that had image attachments show (no prompt) instead of the actual prompt text

Claude Model

Opus

Is this a regression?

I don't know

Claude Code Version

2.1.81 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Ghostty

Additional Information

This significantly reduces the usefulness of the /rewind feature, as users cannot determine which conversation point to rewind to when multiple entries display (no prompt). The prompt text is clearly available (it was typed by the user), so it should be extractable for display in the rewind list regardless of whether an image was also attached.

<img width="723" height="482" alt="Image" src="https://github.com/user-attachments/assets/e3e64511-0ca8-4065-a186-db382d0db805" />

View original on GitHub ↗

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