CommandCodeAI / CommandCodeAI/command-code

Multi-Agent Visual Indicator for Active Sessions

Abierto
#817 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Lenguaje dominante
Sin datos de lenguaje
Estrellas
4k
Forks
350
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

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

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Línea de trabajo

Empieza rastreando las herramientas agent y agent_output, shell_tasks/shell_output y los eventos de transcripción de sesión para entender cómo se expone el estado del ciclo de vida del agente a la CLI. Revisa los puntos de entrada existentes /status y /agents, y después define e implementa un indicador compacto cuyo estado done cubra el recuento de agentes activos, la identidad, una vista previa de la tarea y los estados running, completed, failed y queued.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Área
ai, cli
Tipo de issue
Nueva funcionalidad
Dificultad
5/5
Tiempo estimado
Más de una semana
Estado de actividad
Activo
Claridad
Bastante claro
Aptitud para principiantes
45/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.