CommandCodeAI / CommandCodeAI/command-code

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

未關閉
#457 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

主要語言
沒有語言資料
星號
4k
分支
350
PR 合併指標
30 天內沒有已合併 PR

描述

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)

貢獻指南

這個儲存庫沒有索引到貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

研究方向

issue 中沒有指定檔案、測試或進入點。使用一段較長的對話、工具呼叫和 /compact 重現問題,然後追蹤終端顯示和倒帶/工作階段歷史路徑;完成的標準是壓縮後完整的原始文字仍可檢視或展開。

由索引模型根據 Issue 內容生成。

評估

領域
cli
Issue 類型
缺陷
難度
4/5
預估耗時
3-5 天
活躍度
冷清
描述清晰度
需要釐清
新手友好度
35/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。