When I run a /fleet command after getting a plan, in this instance is spawned...
- 主要言語
- 言語のデータがありません
- スター
- 2.1k
- フォーク
- 153
- PR マージ指標
- 30日以内にマージされた PR はありません
説明
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 |
コントリビューションガイド
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- github
- 領域
- desktop, frontend
- issue の種類
- 機能追加
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 活発さ
- 静か
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 48/100