cleveragents/cleveragents-core

Fork 3

UAT: `agents plan execute` output uses generic plan details panel instead of spec-required execution panels (Execution, Sandbox, Strategy Summary, Progress) #4129

New issue

Open

opened 2026-04-06 10:30:52 +00:00 by freemo · 1 comment

freemo commented

2026-04-06 10:30:52 +00:00

Owner

Metadata

Branch Naming Convention: fix/cli/plan-execute-output-panels
Commit Message: fix(cli): add spec-required execution panels to agents plan execute output
Milestone: None (backlog)
Parent Epic: #3374

Summary

The agents plan execute command uses a generic _print_lifecycle_plan() helper that shows a single plan details panel. The specification requires four distinct panels: Execution, Sandbox, Strategy Summary (for strategize phase), and Progress, plus a phase-specific confirmation line.

What Was Tested

Reviewed src/cleveragents/cli/commands/plan.py, the execute_plan() function (line 1732) and _print_lifecycle_plan() helper (line 1326), and compared against the specification's Example 1 workflow (spec lines 36505–36540 and 36618–36645).

Expected Behavior (from spec)

The spec (lines 36505–36540) requires four panels for the strategize phase:

╭─ Execution ─────────────────────────────╮
│ Plan: 01HXR1C1D2E3F4G5H6I7J8K9L0        │
│ Phase: strategize                       │
│ Sandbox: git_worktree                   │
│ Worker: anthropic/claude-3.5-sonnet     │
│ Started: 09:17:02                       │
│ Attempt: 1                              │
╰─────────────────────────────────────────╯

╭─ Sandbox ───────────────────────────────────────────────────────╮
│ Strategy: git_worktree                                          │
│ Path: /home/dev/projects/api-service/.worktrees/plan-01HXR1C1   │
│ Branch: cleveragents/plan-01HXR1C1D2                            │
│ Status: active                                                  │
╰─────────────────────────────────────────────────────────────────╯

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

╭─ Progress ────────╮
│ ✓ Collect context │
│ ✓ Build strategy  │
│ • Awaiting review │
╰───────────────────╯

✓ OK Strategize complete — awaiting manual approval

And for the execute phase (spec lines 36618–36645):

╭─ Progress ────────────────────────────────╮
│ ✓ Collect context (0.4s)                  │
│ ✓ Modify src/routes/health.py (1.2s)      │
│ ✓ Add tests/test_health.py test (2.1s)    │
│ ✓ Validate: pytest tests/ (3.8s)          │
╰───────────────────────────────────────────╯

✓ OK Execution complete — awaiting apply

Actual Behavior

The code at src/cleveragents/cli/commands/plan.py lines 2033–2051 calls _print_lifecycle_plan(plan, title="Plan Executed") which outputs a single generic panel with all plan details merged together, not the four distinct execution panels required by the spec.

Code Location

File: src/cleveragents/cli/commands/plan.py
Function: execute_plan() at line 1732
Output section: lines 2033–2051

Steps to Reproduce

Create and use a plan: agents plan use local/fix-bug local/api-service
Execute it: agents plan execute <PLAN_ID>
Observe the output — a single generic panel is printed instead of four distinct execution panels

Impact on Workflow Examples

This blocks visual verification of all workflow examples in the spec that use agents plan execute. The command functions correctly (plan is executed), but the output does not match the spec.

Subtasks

Replace _print_lifecycle_plan() call with dedicated _print_plan_execute_output() function
Execution panel: Plan ID, Phase, Sandbox strategy, Worker actor, Started time, Attempt
Sandbox panel: Strategy, Path, Branch, Status
Strategy Summary panel (strategize phase only): Decisions, Invariants, Planned Child Plans, Estimated Files, Risk
Progress panel: list of completed steps with timing
Phase-specific confirmation line: ✓ OK Strategize complete — awaiting manual approval or ✓ OK Execution complete — awaiting apply

Definition of Done

agents plan execute <PLAN_ID> outputs four panels matching the spec format
Strategize phase shows Strategy Summary panel; Execute phase shows file modification steps
Progress panel shows timing for each step
All nox stages pass
Coverage >= 97%

Backlog note: This issue was discovered during autonomous operation
on milestone None (backlog). It does not block milestone completion and has been
placed in the backlog for human review and future milestone assignment.

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: ca-new-issue-creator

## Metadata - **Branch Naming Convention**: `fix/cli/plan-execute-output-panels` - **Commit Message**: `fix(cli): add spec-required execution panels to agents plan execute output` - **Milestone**: None (backlog) - **Parent Epic**: #3374 ## Summary The `agents plan execute` command uses a generic `_print_lifecycle_plan()` helper that shows a single plan details panel. The specification requires four distinct panels: Execution, Sandbox, Strategy Summary (for strategize phase), and Progress, plus a phase-specific confirmation line. ## What Was Tested Reviewed `src/cleveragents/cli/commands/plan.py`, the `execute_plan()` function (line 1732) and `_print_lifecycle_plan()` helper (line 1326), and compared against the specification's Example 1 workflow (spec lines 36505–36540 and 36618–36645). ## Expected Behavior (from spec) The spec (lines 36505–36540) requires four panels for the strategize phase: ``` ╭─ Execution ─────────────────────────────╮ │ Plan: 01HXR1C1D2E3F4G5H6I7J8K9L0 │ │ Phase: strategize │ │ Sandbox: git_worktree │ │ Worker: anthropic/claude-3.5-sonnet │ │ Started: 09:17:02 │ │ Attempt: 1 │ ╰─────────────────────────────────────────╯ ╭─ Sandbox ───────────────────────────────────────────────────────╮ │ Strategy: git_worktree │ │ Path: /home/dev/projects/api-service/.worktrees/plan-01HXR1C1 │ │ Branch: cleveragents/plan-01HXR1C1D2 │ │ Status: active │ ╰─────────────────────────────────────────────────────────────────╯ ╭─ Strategy Summary ────────────────╮ │ Decisions: 4 │ │ Invariants: 0 │ │ Planned Child Plans: 0 │ │ Estimated Files: ~2 │ │ Risk: low │ ╰───────────────────────────────────╯ ╭─ Progress ────────╮ │ ✓ Collect context │ │ ✓ Build strategy │ │ • Awaiting review │ ╰───────────────────╯ ✓ OK Strategize complete — awaiting manual approval ``` And for the execute phase (spec lines 36618–36645): ``` ╭─ Progress ────────────────────────────────╮ │ ✓ Collect context (0.4s) │ │ ✓ Modify src/routes/health.py (1.2s) │ │ ✓ Add tests/test_health.py test (2.1s) │ │ ✓ Validate: pytest tests/ (3.8s) │ ╰───────────────────────────────────────────╯ ✓ OK Execution complete — awaiting apply ``` ## Actual Behavior The code at `src/cleveragents/cli/commands/plan.py` lines 2033–2051 calls `_print_lifecycle_plan(plan, title="Plan Executed")` which outputs a single generic panel with all plan details merged together, not the four distinct execution panels required by the spec. ## Code Location - File: `src/cleveragents/cli/commands/plan.py` - Function: `execute_plan()` at line 1732 - Output section: lines 2033–2051 ## Steps to Reproduce 1. Create and use a plan: `agents plan use local/fix-bug local/api-service` 2. Execute it: `agents plan execute <PLAN_ID>` 3. Observe the output — a single generic panel is printed instead of four distinct execution panels ## Impact on Workflow Examples This blocks visual verification of all workflow examples in the spec that use `agents plan execute`. The command functions correctly (plan is executed), but the output does not match the spec. ## Subtasks - [ ] Replace `_print_lifecycle_plan()` call with dedicated `_print_plan_execute_output()` function - [ ] Execution panel: Plan ID, Phase, Sandbox strategy, Worker actor, Started time, Attempt - [ ] Sandbox panel: Strategy, Path, Branch, Status - [ ] Strategy Summary panel (strategize phase only): Decisions, Invariants, Planned Child Plans, Estimated Files, Risk - [ ] Progress panel: list of completed steps with timing - [ ] Phase-specific confirmation line: `✓ OK Strategize complete — awaiting manual approval` or `✓ OK Execution complete — awaiting apply` ## Definition of Done - [ ] `agents plan execute <PLAN_ID>` outputs four panels matching the spec format - [ ] Strategize phase shows Strategy Summary panel; Execute phase shows file modification steps - [ ] Progress panel shows timing for each step - [ ] All nox stages pass - [ ] Coverage >= 97% > **Backlog note:** This issue was discovered during autonomous operation > on milestone None (backlog). It does not block milestone completion and has been > placed in the backlog for human review and future milestone assignment. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: ca-new-issue-creator

freemo added a new dependency

2026-04-06 10:31:11 +00:00

#3374 Epic: E2E Workflow Specification Tests & Code Review Tool Examples

freemo added the

Points

label

2026-04-06 10:32:28 +00:00

freemo referenced this issue

2026-04-06 10:33:32 +00:00

[Automated] CleverAgents Build Session - 2026-04-06 #3775

freemo referenced this issue

2026-04-06 10:34:17 +00:00

[Automated] CleverAgents Build Session - 2026-04-06 #3775

freemo referenced this issue

2026-04-06 10:35:53 +00:00

[Automated] CleverAgents Build Session - 2026-04-06 #3775

freemo commented

2026-04-06 16:43:17 +00:00

Author

Owner

TRIAGE: v3.2.0 Runtime & Sessions - Medium Priority

CLI output formatting issue for plan execute command. Part of user experience polish after core functionality works.

Rationale: Similar to #4128 - affects UX and spec compliance but doesn't block functionality. Should be addressed in v3.2.0 along with other CLI polish issues.

**TRIAGE: v3.2.0 Runtime & Sessions - Medium Priority** CLI output formatting issue for `plan execute` command. Part of user experience polish after core functionality works. **Rationale:** Similar to #4128 - affects UX and spec compliance but doesn't block functionality. Should be addressed in v3.2.0 along with other CLI polish issues.

freemo added this to the v3.4.0 milestone

2026-04-06 17:48:59 +00:00

freemo removed this from the v3.4.0 milestone

2026-04-06 20:42:47 +00:00