tui-log-view

TUI Log view STILL shows 'no agent output yet' despite tui-agent-activity merged — fix didn't work end-to-end

Metadata

Statusdone
Assignedagent-151
Agent identityf51439356729d112a6c404803d88015d5b44832c6c584c62b96732b63c2b0c7e
Created2026-04-26T20:19:44.732816259+00:00
Started2026-04-26T22:44:12.242403478+00:00
Completed2026-04-26T23:12:14.257275232+00:00
Tagseval-scheduled
Tokens17753149 in / 57045 out

Description

Description

tui-agent-activity was merged to main (commit fe0008ee8 at 12:05). User has freshly-installed binary (Apr 26 15:15, hours after merge). raw_stream.jsonl files for live agents EXIST in .wg/agents/<id>/ (e.g. agent-93 has 15 MB / 383 events). But the TUI '4: Log' view STILL displays 'no agent output yet'.

Conclusion: the merged fix doesn't actually surface the data. The agent that claimed done didn't verify against the live TUI rendering. Identical verification-failure pattern as wg-nex-native.

Diagnose

The Log pane code (likely src/tui/log_pane.rs or similar — find via grep for 'no agent output yet' literal string in src/) needs to be inspected:

  • Does it open the right path? (.wg/agents/<id>/raw_stream.jsonl)
  • Does it parse the format produced by claude-handler?
  • Does it iterate alive agents and render their streams?
  • Does it auto-refresh when new lines arrive?

Repro is trivial: open wg tui in this exact repo, switch to '4: Log' tab, observe 'no agent output yet' even though raw_stream.jsonl files have content.

Fix

Read the streams from .wg/agents/<id>/raw_stream.jsonl for in-progress agents (both worktree-isolated and inline). Render events in the Log pane. Auto-refresh as new lines arrive (file watch or short poll).

Hard gate

Before claiming done:

  1. Open wg tui in a repo where at least one agent is alive AND has written events to its raw_stream.jsonl.
  2. Switch to '4: Log' tab.
  3. Confirm events appear (tool calls, edits, output) — NOT 'no agent output yet'.
  4. Spawn a new agent in another terminal (wg add 'echo test'; wg publish ...); confirm the new agent's events appear in the Log pane within a few seconds.
  5. Capture screenshot OR screen-grep of the rendered Log pane content as evidence.

Without points 1-5 done literally, do not call wg done.

Validation

  • Failing test first: test_log_pane_renders_raw_stream_events_for_alive_agent (use a synthetic raw_stream.jsonl + assert pane content includes event text)
  • Implementation: actually read + render the streams
  • cargo build + cargo test pass with no regressions
  • HARD GATE manual smoke: as specified above

Depends on

Required by

Log