[FEATURE] [Feature Request] Restore per-message copy button
Resolved 💬 4 comments Opened Apr 14, 2026 by cchoi177 Closed May 24, 2026
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Summary
The copy button that used to appear next to each message has been removed in a recent update.
Use Case
- I frequently hit context limits during complex coding sessions (ARIS quant trading platform development)
- I need to copy Claude Code responses to continue work in Claude.ai or share with other AI agents
- Without the per-message copy button, I have to manually drag-select text, which is tedious for long responses
Current Workarounds
/exportcopies entire conversation, not individual messagesCtrl+Shift+Calso copies full conversation- Manual drag-select works but is inefficient
Request
Please restore the per-message copy icon, or add a keyboard shortcut to copy the current/selected message only.
Environment
- Windows 11
- Claude Code latest version
Proposed Solution
Summary
The copy button that used to appear next to each message has been removed in a recent update.
Use Case
- I frequently hit context limits during complex coding sessions (ARIS quant trading platform development)
- I need to copy Claude Code responses to continue work in Claude.ai or share with other AI agents
- Without the per-message copy button, I have to manually drag-select text, which is tedious for long responses
Current Workarounds
/exportcopies entire conversation, not individual messagesCtrl+Shift+Calso copies full conversation- Manual drag-select works but is inefficient
Request
Please restore the per-message copy icon, or add a keyboard shortcut to copy the current/selected message only.
Environment
- Windows 11
- Claude Code latest version
Alternative Solutions
_No response_
Priority
Critical - Blocking my work
Feature Category
CLI commands and flags
Use Case Example
_No response_
Additional Context
_No response_
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗