mini TUI: show live activity while thinking, using tools, or waiting on task child sessions
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
- Área
- cli
Línea de trabajo
Start from the opencode mini TUI's footer/status-bar rendering and the session-status source it reads, then trace how a task child session (ses_…) is recorded so the parent pane can see descendant status. Confirm the scope with a maintainer first: the issue bundles phase display, an inline tool ticker, a subagents strip, and child-session navigation, and overlaps #65057 and #57097. Done looks like a opencode mini --agent orchestrator run showing a phase (thinking/tool:<name>/task:<agent>), a tool line, and the child session id while a task runs.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
In opencode mini (terminal TUI, often embedded in cmux), the parent session frequently shows no visible progress for long stretches: prompt + block cursor, status bar only (agent + model + context %). Users cannot tell whether the model is thinking, calling a tool, or waiting on a task child session that runs elsewhere.
This is especially painful for orchestrator → Task → specialist flows (e.g. developer), where the parent is intentionally quiet but the UI offers no phase indicator, no inline tool ticker, and no link to the active child ses_….
Related issues (overlap, not duplicate):
- #65057 — parent session looks idle while subagent still running (desktop)
- #57097 — bring subagents back to session sidebar (TUI + desktop)
- #6191 — subagent session not in sidebar (historical)
Environment
- OpenCode: 2.3.x (
opencode mini) - Host: cmux 0.65.x (Ghostty surface) on macOS
- Pattern: custom
orchestratoragent withtaskallow-list fordeveloper,code-reviewer, etc.
Expected behavior
While a turn is active, mini should always expose something observable:
- Phase in the status/footer:
thinking|tool:<name>|task:<agent>|waiting_permission|idle - Inline tool activity (compact cards or one-line ticker), including when the parent is waiting on a child
- When
taskspawns a child: show child session id (ses_…) with a keybind or hint to open/list (opencode session list/ switch session) - Elapsed time since last event (helps distinguish slow model vs wedged permission
ask)
Optional: mirror last N tool events from child into parent as read-only feed (collapsed).
Actual behavior
- Long gaps with no streamed output and no tool lines (large context makes “time to first token” long).
- Footer shows parent agent name only, not the active subagent or tool.
- After
task, work continues in a child session with no parent-pane visibility; users assume the session is stuck. - Permission prompts on subagents can wedge headless terminals with no obvious UI.
Reproduction
- Configure a primary agent with
taskallowed for a subagent (e.g.developer). opencode mini --agent orchestratorin a terminal-only surface (cmux or plain).- Ask for work that delegates via
task(or resume with a large context thread). - Observe: parent pane static for minutes; child may be running in another session.
Proposed direction (OpenCode-owned)
Prioritize mini first (cmux and plain SSH), reuse session/subagent data already in the local DB:
- Status bar phase driven by session + descendant status (not only parent
idle) - Subagents strip in mini (may share implementation with #57097)
- Stream tool_start / tool_end to TUI even before assistant text tokens
Additional context
Downstream users work around this with opencode session list, second-pane log tailing, or avoiding task for tool-heavy work (build single thread). A first-class mini indicator would remove the need for those hacks.
Happy to test nightlies or a TUI plugin hook if there is an interim API.
- Lenguaje dominante
- TypeScript
- Estrellas
- 227k
- Forks
- 30.7k
- Merge medio
- 3 h 57 min
- PR fusionados (30 d)
- 484
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de anomalyco/opencode
-
[Site] Active section detection should respect scroll-margin-topPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertoarea/web reproduced type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
anomalyco/opencode#65384 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area/cli type/feature version/v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
anomalyco/opencode#65379 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Shell tool: no upper bound on the timeout a model can ask for, so one call can hold a turn for hoursAbiertoarea/core platform/linux type/feature version/v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
anomalyco/opencode#65254 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
inference/go type/feature
Dificultad 1/5 1-3 horas Aptitud para principiantes 72/100
anomalyco/opencode#65148 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area/providers type/feature version/v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
anomalyco/opencode#64845 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de anomalyco/opencode
Issues similares
-
[Provider] antigravity-acp catalog omits gemini-4-hydrogen and gemini-4-neon that agy acp offersPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertocatalog provider provider-compatibility
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
lidge-jun/opencodex#9037 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
Project submission: xmcp DocsAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 62/100
slavakurilyak/awesome-ai-agents#1005 ·
-
kind/bug triage/unresolved
Dificultad 2/5 1-3 horas Aptitud para principiantes 60/100
Los mantenedores suelen responder en 1 día
-
effort:S P3 refactor
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
nightscout/nocturne#3735 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
wpilibsuite/systemcore-blocks-interface#641 ·
Los mantenedores suelen responder en 2 días