github / github/copilot-cli

Feature Request: Plan status indicators (badge/symbol) on session list items

未關閉
#3,969 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
area:sessions
主要語言
Shell
星號
11.2k
分支
1.9k
平均合併
14 小時 16 分鐘
30 天內合併 PR
6

描述

### Describe the feature or problem you'd like to solve

When managing multiple sessions, there's no visual way to tell at a glance what stage each session's plan is in. You have to open each session to check progress, which breaks flow when juggling several workstreams.

### Proposed solution

Add a small status indicator (symbol with tooltip, or badge) on each session item in the sidebar that reflects the current plan state:

| Status | Meaning | Suggested Icon |
|--------|---------|----------------|
| **Planning** | Agent is actively generating/refining the plan | 🔄 or spinner |
| **PlanReady** | Plan has been generated and is awaiting user approval or kickoff | 📋 or checkmark-outline |
| **PlanInProgress** | Plan has been approved and work is underway | ⚙️ or progress indicator |
| **PlanComplete** | All plan steps are done | ✅ or filled checkmark |

**Requirements:**
- The indicator should be compact enough to not clutter the session list
- A tooltip on hover should show the full status label (e.g., "Plan In Progress")
- Status should update in real-time as the session progresses
- Sessions without a plan (e.g., chat sessions, sessions in interactive/autopilot mode) can omit the indicator or show a neutral state

### Example prompts or workflows

1. User has 5 project sessions open
2. Glancing at the sidebar, they can immediately see:
- Session A: ✅ (done, ready to review/merge)
- Session B: ⚙️ (agent is executing the plan)
- Session C: 📋 (plan ready, waiting for approval)
- Session D: 🔄 (still planning)
3. User clicks Session C to approve the plan, then moves on — no wasted context-switching

### Additional context

Related to #981 (Status Sidebar). This is a lighter-weight version focused specifically on plan lifecycle visibility in the existing session list UI.

貢獻指南

開啟貢獻指南

研究方向

首先定位現有的工作階段清單/側邊欄,以及工作階段使用的計畫生命週期狀態。追蹤規劃、核准、執行和完成更新的傳播方式,然後驗證精簡指示器、暫留標籤、即時更新以及沒有計畫的工作階段是否符合所述需求。

由索引模型根據 Issue 內容生成。

評估

技術堆疊
shell
領域
cli
Issue 類型
功能
難度
4/5
預估耗時
3-5 天
活躍度
冷清
描述清晰度
基本清楚
新手友好度
48/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。