Messages cut off / trimmed down — no way to rewind to view full content

Summary

During long conversations, messages sometimes get cut off or trimmed down — either in the terminal display or after context compaction. There is currently no reliable way to rewind or scroll back to see the full original content of earlier messages.

This is distinct from issue #394 (rewind/restore failing to revert code changes) — this is about message content visibility.

Expected Behavior

• All messages should be fully viewable at any point in a conversation
• Rewind / session history should preserve the complete text of every message, even after /compact or long sessions
• If display truncation is intentional (for performance), there should be a way to expand or view the full message

Actual Behavior

• Messages appear truncated or cut off in the terminal
• After compacting or in long sessions, earlier message content is partially or fully lost
• No command to view the original full text of a prior message

Steps to Reproduce

1. Start a long conversation with multiple exchanges
2. Issue several tool calls and receive long responses
3. Use /compact or continue until context is large
4. Try to scroll back or rewind to earlier messages
5. Message content is missing or truncated

Context

This affects the ability to review what was previously discussed, copy earlier outputs, and maintain continuity in long coding sessions. Related: #394 (rewind/restore), #411 (fork conversation), #435 (copy last message).

Command Code Version

0.26.25

Operating System

macOS (likely affects all platforms)

No files, tests, or entry points are identified in the issue. Reproduce the problem with a long conversation, tool calls, and /compact, then trace the terminal display and rewind/session-history paths; done means the complete original text remains viewable or can be expanded after compaction.