[BUG] Stashing (ctrl + s) doesn't save pasted strings in followup conversation

Resolved 💬 3 comments Opened Dec 19, 2025 by arevlo Closed Dec 20, 2025

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?

Whenever strings show up as pasted text, if you ctrl + s to stash them and do /clear, they get added again but as an empty "Pasted Text" string e.g. [Pasted text #2 + 12 lines] and Claude Code has no clue what to do since it gets rid of the actual text that was pasted from the prior stashed convo.

https://github.com/user-attachments/assets/0b5a03be-f161-4c51-91ec-55322e2f54f4

Note: It does save images when unstashed but not text.

What Should Happen?

Stashing should save the text that is being stashed, it's shouldn't unstash an empty [Pasted text #2 + 12 lines] string that does nothing.

Steps to Reproduce

Here are the steps:

  1. Paste a long piece of text into the Claude Code prompt.
  2. If it gets saved as pasted text do Ctrl+S to slash.
  3. Do now /clear and press Enter; you'll see that Claude Code has no idea what that pasted text was from the prior conversation.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.0.73 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other: Ghostty

View original on GitHub ↗

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