Skip to content

[agent-progress-ui] feat(tui/agents): show per-agent elapsed time and progress in HUD#192

Merged
zemaj merged 1 commit into
mainfrom
issue-191
Sep 18, 2025
Merged

[agent-progress-ui] feat(tui/agents): show per-agent elapsed time and progress in HUD#192
zemaj merged 1 commit into
mainfrom
issue-191

Conversation

@just-every-code

Copy link
Copy Markdown

Summary

Improve visibility for multi‑agent commands (/plan, /solve, /code) in the TUI by:

  • Adding per‑agent timing (running elapsed; total duration when completed/failed)
  • Surfacing the latest progress line for running agents
  • Showing elapsed time inline in the collapsed Agents header for quick at‑a‑glance status

What changed

  • codex-rs/tui/src/chatwidget.rs
    • Track per‑agent runtime timestamps in‑memory (start, last update, completion) keyed by agent id.
    • Extend UI AgentInfo to include id and model from core events.
    • Update AgentStatusUpdate handling to maintain the runtime map and preserve timing across updates.
    • Render improvements:
      • Collapsed Agents header now shows: name (running 1m23s — last_progress…) for up to 3 agents.
      • Expanded Agents panel shows:
        • name (model): running 1m23s (live) or completed 2m05s / failed 45s
        • Latest progress line for running agents (dimmed, truncated for width)
      • Keeps existing sparkline + overall status. No protocol changes.

Rationale

Issue #191 reported that users couldn’t tell whether agents were still working or stuck during multi‑agent flows. By adding visible elapsed time and the most recent progress line, users can quickly gauge per‑agent progress and identify stalls (no updates for a while) without leaving the TUI.

Validation

  • Built locally with ./build-fast.sh (required flow). Result: success, 0 warnings.
  • Changes are UI‑only (Rust TUI crate). No protocol or workflow changes.

Notes

  • The runtime tracking is internal to the TUI and does not alter the core protocol. If future protocol fields (e.g., retry/timeout counters) become available, the HUD can surface them alongside the new timing.

Auto-generated for issue #191 by a workflow.
Author: @github-actions[bot]

@github-actions

Copy link
Copy Markdown

@zemaj zemaj merged commit 458bdf3 into main Sep 18, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants