When I run a /fleet command after getting a plan, in this instance is spawned...
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 2.1k
- Forks
- 153
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
When I run a /fleet command after getting a plan, in this instance is spawned off 6 background agents, but the UX renders it differently than if you had asked GH Copilot app in the chat to spawn off child sessions.
I can see that there are 6 background threads running in the pill above the chat window, but the parent session does not show a "working" gif, nor do any of those background sessions show as child sessions underneath the parent.
It'd be nice if that experience was unified, since they are effectively the same thing
---
| Field | Value |
| --- | --- |
| App version | 1.1.5 |
| OS | Windows 10.0.26200 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 11 |
Guía de contribución
Línea de trabajo
Reproduce the /fleet flow in /chat after a plan is generated and compare it with spawning child sessions from the GitHub Copilot app chat. Inspect the background-thread pill, parent working indicator, and child-session list; done means both flows present the same parent/child session UX.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- github
- Área
- desktop, frontend
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Tranquilo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 48/100