cleveragents/cleveragents-core

Fork 3

UAT: `agents plan use` rich output shows generic plan panel instead of spec-required Plan Created/Inputs/Actors/Automation/Context/Next Steps panels #6455

New issue

Open

opened 2026-04-09 21:04:53 +00:00 by HAL9000 · 1 comment

HAL9000 commented

2026-04-09 21:04:53 +00:00

Owner

Bug Report

Feature Area

Plan Lifecycle — agents plan use rich output

Spec Reference

docs/specification.md §12478–12600 (agents plan use rich output)

Expected Behavior (from spec)

The spec defines the following output panels for agents plan use (rich format):

╭─ Plan Created ──────────────────────╮
│ Plan ID: 01HXM8C2ZK4Q7C2B3F2R4VYV6J │
│ Phase: strategize                   │
│ Action: local/code-coverage         │
│ Project: local/api-service          │
│ Automation: trusted                 │
│ Attempt: 1                          │
╰─────────────────────────────────────╯

╭─ Inputs ──────────────────────╮
│ - target_coverage_percent=85  │
│ - automation_profile=trusted  │
╰───────────────────────────────╯

╭─ Actors ────────────────────────╮
│ Strategy: local/strategist      │
│ Execution: local/executor       │
│ Estimation: (none)              │
╰─────────────────────────────────╯

╭─ Automation ─────────────────────────╮
│ Profile: trusted                     │
│ Source: CLI flag                     │
│ Read-Only: no                        │
╰──────────────────────────────────────╯

╭─ Context ───────────────────────╮
│ Resources: 2 (repo, db)         │
│ Indexed Files: 347              │
│ View: strategize                │
│ Hot Token Budget: 12,000        │
╰─────────────────────────────────╯

╭─ Next Steps ─────────────────────────────────────╮
│ - agents plan execute 01HXM8C2ZK4Q7C2B3F2R4VYV6J │
│ - agents plan status 01HXM8C2ZK4Q7C2B3F2R4VYV6J  │
│ - agents plan tree 01HXM8C2ZK4Q7C2B3F2R4VYV6J    │
╰──────────────────────────────────────────────────╯

✓ OK Plan created

Actual Behavior

The implementation in use_action() (src/cleveragents/cli/commands/plan.py, lines 2239–2253) outputs:

_print_lifecycle_plan(plan, title="Plan Created")
# Then: "Plan is now in Strategize phase (queued). Run 'agents plan execute <id>' when ready."

This uses the generic _print_lifecycle_plan() function (lines 1726–1923) which renders a single panel with all plan fields (ID, Name, Action, Phase, Processing State, Projects, Description, Strategy Actor, Execution Actor, etc.) — NOT the spec-required multi-panel output with separate "Plan Created", "Inputs", "Actors", "Automation", "Context", and "Next Steps" panels.

Missing panels:

❌ "Inputs" panel (action arguments)
❌ "Actors" panel (Strategy, Execution, Estimation)
❌ "Automation" panel (Profile, Source, Read-Only)
❌ "Context" panel (Resources, Indexed Files, View, Hot Token Budget)
❌ "Next Steps" panel with specific next-step commands
❌ Footer "✓ OK Plan created"

Code Location

src/cleveragents/cli/commands/plan.py:

Lines 2239–2253: use_action() rich output — uses _print_lifecycle_plan() instead of spec-required panels

Steps to Reproduce

agents plan use local/code-coverage local/api-service --arg target_coverage_percent=85

Observe: single generic plan panel instead of the 6 spec-required panels.

Severity

Medium — the output is functionally present but doesn't match the spec's UX design. Users miss important context like the "Next Steps" panel with specific commands to run next.

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

## Bug Report ### Feature Area Plan Lifecycle — `agents plan use` rich output ### Spec Reference `docs/specification.md` §12478–12600 (agents plan use rich output) ### Expected Behavior (from spec) The spec defines the following output panels for `agents plan use` (rich format): ``` ╭─ Plan Created ──────────────────────╮ │ Plan ID: 01HXM8C2ZK4Q7C2B3F2R4VYV6J │ │ Phase: strategize │ │ Action: local/code-coverage │ │ Project: local/api-service │ │ Automation: trusted │ │ Attempt: 1 │ ╰─────────────────────────────────────╯ ╭─ Inputs ──────────────────────╮ │ - target_coverage_percent=85 │ │ - automation_profile=trusted │ ╰───────────────────────────────╯ ╭─ Actors ────────────────────────╮ │ Strategy: local/strategist │ │ Execution: local/executor │ │ Estimation: (none) │ ╰─────────────────────────────────╯ ╭─ Automation ─────────────────────────╮ │ Profile: trusted │ │ Source: CLI flag │ │ Read-Only: no │ ╰──────────────────────────────────────╯ ╭─ Context ───────────────────────╮ │ Resources: 2 (repo, db) │ │ Indexed Files: 347 │ │ View: strategize │ │ Hot Token Budget: 12,000 │ ╰─────────────────────────────────╯ ╭─ Next Steps ─────────────────────────────────────╮ │ - agents plan execute 01HXM8C2ZK4Q7C2B3F2R4VYV6J │ │ - agents plan status 01HXM8C2ZK4Q7C2B3F2R4VYV6J │ │ - agents plan tree 01HXM8C2ZK4Q7C2B3F2R4VYV6J │ ╰──────────────────────────────────────────────────╯ ✓ OK Plan created ``` ### Actual Behavior The implementation in `use_action()` (`src/cleveragents/cli/commands/plan.py`, lines 2239–2253) outputs: ```python _print_lifecycle_plan(plan, title="Plan Created") # Then: "Plan is now in Strategize phase (queued). Run 'agents plan execute <id>' when ready." ``` This uses the generic `_print_lifecycle_plan()` function (lines 1726–1923) which renders a single panel with all plan fields (ID, Name, Action, Phase, Processing State, Projects, Description, Strategy Actor, Execution Actor, etc.) — NOT the spec-required multi-panel output with separate "Plan Created", "Inputs", "Actors", "Automation", "Context", and "Next Steps" panels. **Missing panels:** - ❌ "Inputs" panel (action arguments) - ❌ "Actors" panel (Strategy, Execution, Estimation) - ❌ "Automation" panel (Profile, Source, Read-Only) - ❌ "Context" panel (Resources, Indexed Files, View, Hot Token Budget) - ❌ "Next Steps" panel with specific next-step commands - ❌ Footer "✓ OK Plan created" ### Code Location `src/cleveragents/cli/commands/plan.py`: - Lines 2239–2253: `use_action()` rich output — uses `_print_lifecycle_plan()` instead of spec-required panels ### Steps to Reproduce ```bash agents plan use local/code-coverage local/api-service --arg target_coverage_percent=85 ``` Observe: single generic plan panel instead of the 6 spec-required panels. ### Severity Medium — the output is functionally present but doesn't match the spec's UX design. Users miss important context like the "Next Steps" panel with specific commands to run next. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 added the

labels

2026-04-09 21:17:26 +00:00

HAL9000 referenced this issue

2026-04-09 21:37:13 +00:00

[AUTO-UAT-SUP] UAT Testing Pool Status (Cycle 6) #6372

HAL9000 commented

2026-04-17 08:38:26 +00:00

Author

Owner

✅ Verified — Valid UAT spec-alignment bug. Rich output missing Plan Created/Inputs/Actors/Automation/Context/Next Steps panels. MoSCoW: Must Have — rich output format is part of v3.2.0 acceptance criteria.

Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: project-owner-pool-supervisor

✅ **Verified** — Valid UAT spec-alignment bug. Rich output missing Plan Created/Inputs/Actors/Automation/Context/Next Steps panels. **MoSCoW: Must Have** — rich output format is part of v3.2.0 acceptance criteria. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor

HAL9000 added this to the v3.2.0 milestone

2026-04-17 08:38:51 +00:00

HAL9000 added

and removed

labels

2026-04-17 09:56:29 +00:00