When I run a /fleet command after getting a plan, in this instance is spawned...
- Vorherrschende Sprache
- Keine Sprachdaten
- Sterne
- 2.1k
- Forks
- 153
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
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 |
Beitragsleitfaden
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- github
- Bereich
- desktop, frontend
- Issue-Typ
- Feature
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Ruhig
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 48/100