UAT: agents plan execute rich output shows generic plan panel instead of spec-required Execution/Sandbox/Strategy Summary/Progress panels #6344

Closed
opened 2026-04-09 20:12:32 +00:00 by HAL9000 · 0 comments
Owner

Bug Report

Feature Area: Plan Lifecycle
Spec Reference: docs/specification.md §agents plan execute (around line 12923)
Instance: uat-worker-W1-cycle3


Summary

agents plan execute (rich format, default) shows a generic plan detail panel via _print_lifecycle_plan() instead of the four spec-required panels: Execution, Sandbox, Strategy Summary, and Progress.

The spec-required output structure for plan execute in rich format is completely different from what is rendered.


Code Location

/app/src/cleveragents/cli/commands/plan.py, lines 2454–2479:

if fmt != OutputFormat.RICH.value:
    execute_elapsed_ms = int(...)
    envelope = _execute_output_dict(...)
    console.print(format_output(envelope, fmt))
else:
    _print_lifecycle_plan(plan, title="Plan Executed")   # ← wrong: generic plan panel
    phase_label = f"{plan.phase.value}/{plan.state.value}"
    if plan.phase == PlanPhase.EXECUTE and plan.state in (...):
        console.print(
            f"\n[dim]Plan execution completed ({phase_label}). ..."
        )

Note: _execute_output_dict() on lines 304–471 correctly builds the spec-required JSON structure with Execution, Sandbox, Strategy Summary, and Progress sub-objects, but this data is only used for non-rich formats. The rich rendering path ignores this structure entirely and uses the generic plan panel instead.


Steps to Reproduce

agents plan execute <PLAN_ID>   # default rich format

Expected (per spec §agents plan execute rich output)

╭─ Execution ──────────────────────╮
│ Plan: 01HXM8C2ZK4Q7C2B3F2R4VYV6J │
│ Phase: execute                   │
│ Sandbox: git_worktree            │
│ Worker: local/executor           │
│ Started: 12:58:10                │
│ Attempt: 1                       │
╰──────────────────────────────────╯

╭─ Sandbox ──────────────────────────────────╮
│ Strategy: git_worktree                     │
│ Path: /repos/api/.worktrees/plan-01HXM8    │
│ Branch: cleveragents/plan-01HXM8C2         │
│ Status: active                             │
╰────────────────────────────────────────────╯

╭─ Strategy Summary ─────────────────────╮
│ Decisions: 8                           │
│ Invariants: 2                          │
│ Planned Child Plans: 2+                │
│ Estimated Files: ~12                   │
│ Risk: low                              │
╰────────────────────────────────────────╯

╭─ Progress ─────────╮
│ ⏳ Collect context │
│ •  Run tools       │
│ •  Build changeset │
│ •  Validate        │
╰────────────────────╯

✓ OK Execution started

Actual

╭─ Plan Executed ────────────────────────────────────────────────╮
│ ID: 01HXM8C2ZK4Q7C2B3F2R4VYV6J                                │
│ Name: local/...                                                │
│ Action: local/code-coverage                                    │
│ Phase: execute                                                 │
│ Processing State: complete                                     │
│ ...generic plan details...                                     │
╰────────────────────────────────────────────────────────────────╯

Plan execution completed (execute/complete). Run 'agents plan apply <id>' when ready.

Impact

  • Rich output is not compliant with spec; users see a verbose generic panel instead of the focused execution summary
  • The Execution, Sandbox, Strategy Summary, and Progress panels are present only in the JSON/YAML output path (_execute_output_dict), not in the rich path
  • ✓ OK Execution started footer is missing from rich output

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: uat-tester

## Bug Report **Feature Area**: Plan Lifecycle **Spec Reference**: `docs/specification.md` §`agents plan execute` (around line 12923) **Instance**: uat-worker-W1-cycle3 --- ### Summary `agents plan execute` (rich format, default) shows a generic plan detail panel via `_print_lifecycle_plan()` instead of the four spec-required panels: **Execution**, **Sandbox**, **Strategy Summary**, and **Progress**. The spec-required output structure for `plan execute` in rich format is completely different from what is rendered. --- ### Code Location `/app/src/cleveragents/cli/commands/plan.py`, lines 2454–2479: ```python if fmt != OutputFormat.RICH.value: execute_elapsed_ms = int(...) envelope = _execute_output_dict(...) console.print(format_output(envelope, fmt)) else: _print_lifecycle_plan(plan, title="Plan Executed") # ← wrong: generic plan panel phase_label = f"{plan.phase.value}/{plan.state.value}" if plan.phase == PlanPhase.EXECUTE and plan.state in (...): console.print( f"\n[dim]Plan execution completed ({phase_label}). ..." ) ``` Note: `_execute_output_dict()` on lines 304–471 correctly builds the spec-required JSON structure with `Execution`, `Sandbox`, `Strategy Summary`, and `Progress` sub-objects, but this data is **only used for non-rich formats**. The rich rendering path ignores this structure entirely and uses the generic plan panel instead. --- ### Steps to Reproduce ```bash agents plan execute <PLAN_ID> # default rich format ``` --- ### Expected (per spec §agents plan execute rich output) ``` ╭─ Execution ──────────────────────╮ │ Plan: 01HXM8C2ZK4Q7C2B3F2R4VYV6J │ │ Phase: execute │ │ Sandbox: git_worktree │ │ Worker: local/executor │ │ Started: 12:58:10 │ │ Attempt: 1 │ ╰──────────────────────────────────╯ ╭─ Sandbox ──────────────────────────────────╮ │ Strategy: git_worktree │ │ Path: /repos/api/.worktrees/plan-01HXM8 │ │ Branch: cleveragents/plan-01HXM8C2 │ │ Status: active │ ╰────────────────────────────────────────────╯ ╭─ Strategy Summary ─────────────────────╮ │ Decisions: 8 │ │ Invariants: 2 │ │ Planned Child Plans: 2+ │ │ Estimated Files: ~12 │ │ Risk: low │ ╰────────────────────────────────────────╯ ╭─ Progress ─────────╮ │ ⏳ Collect context │ │ • Run tools │ │ • Build changeset │ │ • Validate │ ╰────────────────────╯ ✓ OK Execution started ``` ### Actual ``` ╭─ Plan Executed ────────────────────────────────────────────────╮ │ ID: 01HXM8C2ZK4Q7C2B3F2R4VYV6J │ │ Name: local/... │ │ Action: local/code-coverage │ │ Phase: execute │ │ Processing State: complete │ │ ...generic plan details... │ ╰────────────────────────────────────────────────────────────────╯ Plan execution completed (execute/complete). Run 'agents plan apply <id>' when ready. ``` --- ### Impact - Rich output is not compliant with spec; users see a verbose generic panel instead of the focused execution summary - The `Execution`, `Sandbox`, `Strategy Summary`, and `Progress` panels are present only in the JSON/YAML output path (`_execute_output_dict`), not in the rich path - `✓ OK Execution started` footer is missing from rich output --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester
HAL9000 added this to the v3.2.0 milestone 2026-04-09 21:09:35 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#6344
No description provided.