github / github/copilot-cli

Feature Request: Visual Progress Indicator for File Deletion Operations

Aberta
#2,566 0 comentários 0 reações 0 responsáveis Ver no GitHub
area:terminal-rendering area:tools
Linguagem predominante
Shell
Estrelas
11.2k
Forks
1.9k
Merge médio
14h 16min
PRs com merge (30d)
6

Descrição

### Describe the feature or problem you'd like to solve

When Copilot performs long-running file deletion operations (e.g., deleting a directory with ~58,000 files), the UI provides almost no progress feedback. Users only see generic messages like "Still deleting ~58K files. Let me wait for it to finish." and "Waiting up to 180 seconds for command output." There is no indication of how many files have been deleted or how close the operation is to completing.

### Issue

Image

### Proposed solution

Display a real-time progress indicator during file deletion operations. This could include:

- A running count of files deleted vs. total (e.g., "Deleted 12,400 / 57,907 files")
- A progress bar or percentage
- Estimated time remaining based on current deletion rate
- Optionally, a collapsible log showing individual file names as they are deleted

This would give users confidence that the operation is progressing and help them estimate when it will finish, rather than staring at repeated "Waiting up to N seconds" messages with no visibility into actual progress.

---

### Example prompts or workflows

1. **"Delete the _boost_temp directory"** — Copilot deletes ~58K files. Instead of opaque wait messages, the user sees: `Deleting files... 34,200 / 57,907 (59%) — ~45s remaining`
2. **"Clean up all build artifacts in this repo"** — Copilot removes thousands of files across multiple directories. A progress bar updates in real time as each directory is cleared.
3. **"Remove node_modules and reinstall"** — Copilot deletes a large `node_modules` folder. The user sees file-by-file or batch progress instead of a spinning indicator with no context.

### Additional context

_No response_

Guia de contribuição

Abrir o guia de contribuição

Direção de pesquisa

The issue does not name files, tests, or entry points, so first locate the file-deletion operation and the terminal output that emits the repeated waiting messages. Define the completed behavior against the examples: long-running deletions should show current progress toward a total, with an optional time estimate or file log.

Escrita pelo modelo de indexação a partir do texto da issue.

Avaliação

Stack de tecnologia
shell
Domínio
cli
Tipo de issue
Funcionalidade
Dificuldade
5/5
Tempo estimado
Mais de uma semana
Status de atividade
Pouca atividade
Clareza
Razoavelmente clara
Facilidade para iniciantes
40/100

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.