mini TUI: show live activity while thinking, using tools, or waiting on task child sessions

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

メンテナーはふだん 1 日以内に返信

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

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
typescript
領域
cli

調査の方向性

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.

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

説明

area/tui platform/macos type/feature version/v2

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 orchestrator agent with task allow-list for developer, code-reviewer, etc.

Expected behavior

While a turn is active, mini should always expose something observable:

  1. Phase in the status/footer: thinking | tool:<name> | task:<agent> | waiting_permission | idle
  2. Inline tool activity (compact cards or one-line ticker), including when the parent is waiting on a child
  3. When task spawns a child: show child session id (ses_…) with a keybind or hint to open/list (opencode session list / switch session)
  4. 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

  1. Configure a primary agent with task allowed for a subagent (e.g. developer).
  2. opencode mini --agent orchestrator in a terminal-only surface (cmux or plain).
  3. Ask for work that delegates via task (or resume with a large context thread).
  4. 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.

主要言語
TypeScript
スター
227k
フォーク
30.7k
平均マージ
3時間 57分
マージ済み PR(30日)
484

環境構築

はじめの一歩

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

anomalyco/opencode のほかの issue

anomalyco/opencode の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

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

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