CommandCodeAI / CommandCodeAI/command-code
Multi-Agent Visual Indicator for Active Sessions
還沒有人認領這個 Issue。
- 主要語言
- 沒有語言資料
- 星號
- 4k
- 分支
- 350
- PR 合併指標
- 30 天內沒有已合併 PR
描述
Feature Request: Multi-Agent Visual Indicator for Active Session
Summary
Add a visual indicator in the Command Code CLI that shows when multiple agents are running concurrently within the session, giving users real-time awareness of active subagent work — similar to how Theo implemented this for T3 Code and how Codex displays active agents.
Problem
Currently, when Command Code delegates work to multiple subagents (via the agent tool), there's no visible indicator in the UI showing:
- Which agents are currently running
- How many agents are active
- What each agent is working on (its task/description)
- Agent status (running, completed, failed)
Users are left unaware of background work happening in their session. When multiple agent calls fire in parallel (e.g., 3 explorers + 2 editors), the main session appears idle while work happens invisibly.
Proposed Solution
Implement a persistent visual indicator (status bar, footer, or inline badge) that displays:
- Active agent count — e.g., "3 agents running"
- Agent identity badges — show agent name/type (General, Explore, Plan, or custom names)
- Status states — running (spinner), completed (checkmark), failed (error icon)
- Task preview — truncated description of what each agent is doing
- Background agent awareness — show agents started with
background: trueorrun_in_background: true
Visual Inspiration
- T3 Code (Theo): Shows active agents as colored badges with spinners in the terminal footer
- Codex: Displays agent tiles with status indicators and task descriptions
- GitHub Copilot Workspace: Shows parallel task execution with progress indicators
User Experience
In-Session Indicator
┌─────────────────────────────────────────────────────────────┐
│ 🤖 3 agents running │
│ ● Explore — "Searching auth middleware..." │
│ ● General — "Refactoring database layer..." │
│ ◌ Plan — "Designing API routes..." (queued) │
└─────────────────────────────────────────────────────────────┘
Status States
- ● Running (with spinner animation)
- ✓ Completed successfully
- ✗ Failed/errored
- ◌ Queued/pending
Interaction Ideas
- Click/tap an agent badge to see its full output
- Keyboard shortcut to cycle through active agents
/agentscommand enhanced to show live status alongside agent definitions- Optional: notification when all agents complete
Technical Considerations
Existing Primitives
Command Code already has the building blocks:
agenttool returnsagent_idfor background runsagent_outputtool can checkstatusof running agentsshell_tasks/shell_outputtrack background processes- Session transcript already records agent delegation events
Implementation Approaches
- Status bar component — persistent footer showing active agents (least intrusive)
- Inline badges — agent indicators appear inline with conversation flow
- Dedicated panel — toggle-able side panel with full agent details (heavier)
Agent Lifecycle Events to Surface
- Agent started (with name + task description)
- Agent progress (optional, if agents can report intermediate status)
- Agent completed (with result summary or token usage)
- Agent failed (with error reason)
Benefits
- Transparency: Users know work is happening even when main session is quiet
- Debuggability: Easier to understand what went wrong when an agent fails
- Confidence: Visual feedback that parallel delegation is working
- Discoverability: Encourages users to leverage multi-agent parallelism
Potential Concerns
- Terminal real estate: Status bar takes up space — should be compact and optionally hideable
- Noise: Could be distracting with many agents — consider collapsing/expanding
- Performance: Polling agent status shouldn't add overhead
Settings
Consider a setting to control visibility:
{
"showAgentIndicator": true,
"agentIndicatorStyle": "compact" // "compact" | "detailed" | "none"
}
Related Features
- Background tasks (
run_in_background) - Agent output streaming (
showOutput: true) - Session status (
/status) /agentsmanager
Priority: Medium — improves UX significantly for power users leveraging multi-agent workflows
Affected Users: Anyone using parallel agent delegation, background agents, or custom subagents
貢獻指南
這個儲存庫沒有索引到貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
首先追蹤 agent 和 agent_output 工具、shell_tasks/shell_output 以及工作階段逐字稿事件,以了解 agent 生命週期狀態如何向 CLI 公開。檢視現有的 /status 和 /agents 進入點,然後定義並實作一個精簡的指示器,其 done 狀態涵蓋作用中 agent 數量、身分、工作預覽,以及 running、completed、failed 和 queued 狀態。
由索引模型根據 Issue 內容生成。
評估
- 領域
- ai, cli
- Issue 類型
- 功能
- 難度
- 5/5
- 預估耗時
- 一週以上
- 活躍度
- 活躍
- 描述清晰度
- 基本清楚
- 新手友好度
- 45/100