Blocker: Compact can be triggered accidentally with no confirmation or Undo
まだ誰も着手していません。
- 主要言語
- Shell
- スター
- 11.2k
- フォーク
- 1.9k
- 平均マージ
- 14時間 16分
- マージ済み PR(30日)
- 6
説明
Describe the bug
The Compact action in the VS Code Copilot CLI experience can be activated accidentally and immediately rewrites the active conversation context without:
- a confirmation dialog,
- a clear warning that the operation cannot be reversed,
- an Undo action, or
- a supported way to restore the original conversation into the active UI/context.
This is a blocker-level data-loss UX issue. Although an underlying session record/checkpoint may remain on disk, that is not equivalent to preserving the user's active conversation. After accidental activation, the user cannot restore the session to its prior state or see the original conversation as it appeared before compaction.
Affected version
- VS Code: 1.131.0 (Windows x64)
- Copilot CLI runtime integrated into VS Code; standalone
copilotexecutable is not available in PATH - Observed August 3, 2026
Steps to reproduce
- Open a long-running Copilot CLI session in VS Code.
- Accidentally activate Compact.
- Observe that compaction begins immediately without confirmation.
- After it completes, attempt to undo or restore the original active conversation.
- Observe that no Undo or restoration path exists.
Actual behavior
A single accidental activation permanently replaces a large active conversation with a generated summary. In the observed session, compaction removed approximately 133,000 tokens from active context. The session checkpoint/log remained, but the original visible/active conversation could not be restored.
Expected behavior
Before Compact runs, show a blocking confirmation that clearly states what will change and whether it can be undone. At minimum:
- Require explicit confirmation for manual compaction.
- Clearly state that the current active context will be replaced by a summary.
- Provide an immediate Undo/Restore action backed by the retained session record.
- Preserve access to the original visible transcript.
- Consider moving Compact away from controls that are easy to trigger accidentally.
Please treat this as a release-blocking UX/data-preservation defect rather than a normal enhancement request. Irreversible context replacement must not occur from one accidental click.
Additional context
No private session content or source code is included in this report.
コントリビューションガイド
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
調査の方向性
まず、VS Code Copilot CLI エクスペリエンスで Compact アクションを再現し、手動コンパクションのエントリポイントを追跡します。セッションのチェックポイント/ログがどのように保持され、アクティブな会話がどのように置き換えられるかを確認します。手動コンパクションに確認が必要で、元のトランスクリプトを保持しながら、サポートされた Undo または復元の経路が提供されれば完了です。
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- shell, vscode
- 領域
- cli, developer-experience
- issue の種類
- バグ
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 活発さ
- 静か
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 25/100