Feature request: allow Copilot agents to read user-opened terminal panes with...
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
Línea de trabajo
Start at the /chat terminal-pane experience and review how terminal actions such as “Send terminal to chat” or Ctrl+L could be represented in the app. Done means explicit, visible, time-limited, terminal-scoped and revocable consent lets Copilot read the approved terminal context without default access.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Feature request: allow Copilot agents to read user-opened terminal panes with explicit consent.
Use case:
I opened a terminal manually inside the GitHub Copilot app and ran an external agent CLI (ant). When I asked Copilot if it could see the terminal output, it could detect that a terminal panel existed from context, but it could not read the scrollback because the terminal instance was not accessible to the agent.
Desired behavior:
- User opens a terminal manually and runs commands.
- User asks Copilot to inspect the terminal, or clicks a terminal action such as “Send terminal to chat”.
- App asks for explicit per-terminal consent, or the click itself acts as an intentional share action.
- If approved, Copilot can read current viewport / recent scrollback / selected scrollback / full scrollback.
- Access should be time-limited, visible, scoped to that terminal, and revocable.
Prior art / UX reference:
In Antigravity IDE, when a terminal is open, the top bar has an @ action, also available via Ctrl+L, labeled “Send terminal to chat”. This is a useful interaction pattern: the user explicitly chooses to attach/share the terminal context with the chat instead of the agent having automatic access.
Why this matters:
This would improve debugging and coordination when using external agent CLIs (ant, agy, copilot) inside Copilot app project worktrees. It would avoid manual copy/paste of terminal output while preserving the right privacy model: no terminal access by default, only explicit user-initiated sharing.
| Field | Value |
|---|---|
| App version | 1.1.22 |
| OS | Windows 10.0.26200 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Day 1 |
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 2.1k
- Forks
- 157
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de github/app
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Todos los issues de github/app
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix impact:other issue-rating: 🌊 off-meta tidepool no-stale P2
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
0xPlaygrounds/rig#2584 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
danielmiessler/LifeOS#2232 ·
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
datalayer/mcp-compose#42 ·