You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the TUI transcript, an ordinary compact tool row can be name-only during the live tool_start window, and a quiet successful call can degrade to an unhelpful ● Bash (no output). The user has no useful middle ground between the compact row and expanding the full output card.
Current main already renders commands and other invocation details after durable args/results arrive. This issue covers the earlier live window and the compact-row relationship between what ran and what happened.
Scope
Let ordinary tools consume a bounded, redacted live invocation preview.
Keep command/path/query information visible independently of the result annotation.
Do not show the dim no output placeholder when the row already names a successful quiet call.
Preserve fixed-shape result statistics, exit status, truncation priority, and the existing Ctrl+O expanded-card contract.
Empty or unavailable args remain a name-only fallback rather than input: {} noise.
Scope split
Task Ledger tools are not generic nested-args tools. A useful create row needs the complete committed task set and real IDs; a useful update row needs the subject and exact mutation state, not merely T1 → completed. Their Host-owned semantic timeline is tracked separately in #4179 and is intentionally excluded from this issue and #3376.
Acceptance
During the live window, a quiet ordinary Bash call can show ● Bash $ git add -A (running) rather than ● Bash (running).
After success, a named quiet call does not use (no output) as its only outcome signal.
Preview strings are redacted and bounded before crossing the Runtime Host wire.
Durable args replace the preview after reconciliation without changing tool identity.
Symptom
In the TUI transcript, an ordinary compact tool row can be name-only during the live
tool_startwindow, and a quiet successful call can degrade to an unhelpful● Bash (no output). The user has no useful middle ground between the compact row and expanding the full output card.Current main already renders commands and other invocation details after durable args/results arrive. This issue covers the earlier live window and the compact-row relationship between what ran and what happened.
Scope
no outputplaceholder when the row already names a successful quiet call.Ctrl+Oexpanded-card contract.input: {}noise.Scope split
Task Ledger tools are not generic nested-args tools. A useful create row needs the complete committed task set and real IDs; a useful update row needs the subject and exact mutation state, not merely
T1 → completed. Their Host-owned semantic timeline is tracked separately in #4179 and is intentionally excluded from this issue and #3376.Acceptance
● Bash $ git add -A (running)rather than● Bash (running).(no output)as its only outcome signal.