Add a diff-only view/keybind for reviewing just agent code changes
- Lingua principale
- Shell
- Stelle
- 11.2k
- Fork
- 1.9k
- Merge medio
- 14h 16m
- PR unite (30g)
- 6
Descrizione
### Describe the feature or problem you'd like to solve
Copilot CLI has useful visibility controls, but none that focus specifically on **code line changes only**.
- `Ctrl+O` / expanded timeline shows too much: shell commands, script output, session-state files, markdown/session artifacts, and other operational noise.
- `Ctrl+T` is about reasoning, not code review.
- `/diff` is helpful, but it doesn't map to the quick "show me exactly what code changed from the agent" interaction I want while staying inside the main terminal flow.
When I'm working in the terminal, I care most about **how the agent changed my code**. I usually don't care about session-state updates, helper scripts, or verbose command output.
### Proposed solution
Add a **diff-only review mode** in Copilot CLI for agent edits.
Ideal behavior:
1. A dedicated keybind to toggle **code diff view only**.
2. Show only edited file hunks, grouped by file.
3. Hide shell/script output, session artifacts, state files, and unrelated timeline items by default.
4. Support scoping such as:
- **last turn only**
- **all changes in current session**
5. Render diffs in a clean terminal-native viewer instead of requiring users to expand the entire timeline or open an external editor.
This would make it much easier to audit agent changes quickly and confidently from inside the CLI.
### Example prompts or workflows
1. I ask Copilot CLI to refactor a function, then hit a keybind to see only the code hunks it changed in that turn.
2. I let the agent make several edits, then toggle a session-wide diff-only view without seeing all shell commands and background task output.
3. I review changes in a terminal-only workflow without switching to VS Code or manually running `git diff`.
4. I compare the agent's edits before deciding whether to keep working, rewind, or undo.
### Additional context
The main gap is not "can I see changes at all?" — it's that the current visibility options are too broad or noisy for the common "review only code edits" workflow.
A dedicated diff-only view would be especially valuable for users who prefer terminal-first workflows and want a fast audit surface similar to focused code-diff review in other coding agents.
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia esaminando la timeline espansa esistente di Ctrl+O, la vista di ragionamento di Ctrl+T e il workflow /diff per comprenderne gli scope e il rendering attuali. Definisci come una modalità nativa del terminale con solo diff identificherebbe gli hunk di codice, raggrupperebbe i file modificati e distinguerebbe le modifiche dell’ultimo turno da tutte le modifiche della sessione. Il lavoro è completato quando l’interazione, la combinazione di tasti, il comportamento dello scope e la gestione degli artefatti non di codice sono specificati abbastanza dettagliatamente da poter essere implementati e revisionati.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- shell
- Ambito
- cli
- Tipo di issue
- Funzionalità
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Stato di attività
- Tranquilla
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 30/100