CommandCodeAI / CommandCodeAI/command-code

Multi-Agent Visual Indicator for Active Sessions

オープン
#817 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

主要言語
言語のデータがありません
スター
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:

  1. Active agent count — e.g., "3 agents running"
  2. Agent identity badges — show agent name/type (General, Explore, Plan, or custom names)
  3. Status states — running (spinner), completed (checkmark), failed (error icon)
  4. Task preview — truncated description of what each agent is doing
  5. Background agent awareness — show agents started with background: true or run_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
  • /agents command 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:

  • agent tool returns agent_id for background runs
  • agent_output tool can check status of running agents
  • shell_tasks / shell_output track background processes
  • Session transcript already records agent delegation events
Implementation Approaches
  1. Status bar component — persistent footer showing active agents (least intrusive)
  2. Inline badges — agent indicators appear inline with conversation flow
  3. 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)
  • /agents manager

Priority: Medium — improves UX significantly for power users leveraging multi-agent workflows

Affected Users: Anyone using parallel agent delegation, background agents, or custom subagents

コントリビューションガイド

このリポジトリのコントリビューションガイドは索引されていません

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

調査の方向性

まず、agent と agent_output ツール、shell_tasks/shell_output、およびセッション転記イベントを追跡し、エージェントのライフサイクル状態が CLI にどのように公開されているかを理解します。既存の /status と /agents のエントリポイントを確認し、アクティブなエージェント数、識別情報、タスクのプレビュー、および running、completed、failed、queued の各状態をカバーする done 状態を持つコンパクトなインジケーターを定義して実装します。

索引モデルが issue の本文から書いたものです。

評価

領域
ai, cli
issue の種類
機能追加
難易度
5/5
見積もり時間
1週間以上
活発さ
活発
明瞭さ
おおむね明確
初心者へのやさしさ
45/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。