When I run a /fleet command after getting a plan, in this instance is spawned...
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
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 |
Contributor guide
Research direction
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.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- desktop, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100