UAT: `agents plan status` JSON/YAML output missing spec-required command envelope and uses wrong field names #6279

New issue

Open

opened 2026-04-09 19:47:55 +00:00 by HAL9000 · 0 comments

HAL9000 commented

2026-04-09 19:47:55 +00:00

Owner

Spec Reference

Spec §agents plan status (lines 13660–13703) defines the JSON output envelope:

{
  "command": "plan status",
  "status": "ok",
  "exit_code": 0,
  "data": {
    "plan_id": "...",
    "phase": "execute",
    "state": "processing",
    "action": "local/code-coverage",
    "project": "local/api-service",
    "automation": "review",
    "attempt": 1,
    "progress": [...],
    "timing": {"started": "...", "elapsed": "...", "eta": "..."},
    "execution": {"sandbox": "...", "tool_calls": 8, "files_modified": 3, "child_plans": "...", "checkpoints": 2},
    "cost": {"tokens_used": 12420, "cost_so_far": 0.041, "estimated": 0.085}
  },
  "timing": {"started": "...", "duration_ms": 120},
  "messages": ["Status refreshed"]
}

Expected Behavior

agents plan status <PLAN_ID> --format json should return the full spec-required JSON envelope with:

Top-level command, status, exit_code, data, timing, messages keys
data.action (not action_name)
data.project (not project_links)
data.automation (profile name)
data.attempt
data.progress (phase progress steps)
data.timing (started, elapsed, eta)
data.execution (sandbox, tool_calls, files_modified, child_plans, checkpoints)
data.cost (tokens_used, cost_so_far, estimated)

Actual Behavior

The implementation uses _plan_spec_dict(plan) (see src/cleveragents/cli/commands/plan.py line 2734) which returns a flat dict without the command envelope. Missing: command, status, exit_code, timing, messages, attempt, progress, execution, cost. Wrong field names: action_name instead of action, project_links instead of project.

Code Location

src/cleveragents/cli/commands/plan.py lines 2733–2735 (plan_status, non-rich output)

Steps to Reproduce

agents plan status <PLAN_ID> --format json

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

## Spec Reference Spec §agents plan status (lines 13660–13703) defines the JSON output envelope: ```json { "command": "plan status", "status": "ok", "exit_code": 0, "data": { "plan_id": "...", "phase": "execute", "state": "processing", "action": "local/code-coverage", "project": "local/api-service", "automation": "review", "attempt": 1, "progress": [...], "timing": {"started": "...", "elapsed": "...", "eta": "..."}, "execution": {"sandbox": "...", "tool_calls": 8, "files_modified": 3, "child_plans": "...", "checkpoints": 2}, "cost": {"tokens_used": 12420, "cost_so_far": 0.041, "estimated": 0.085} }, "timing": {"started": "...", "duration_ms": 120}, "messages": ["Status refreshed"] } ``` ## Expected Behavior `agents plan status <PLAN_ID> --format json` should return the full spec-required JSON envelope with: - Top-level `command`, `status`, `exit_code`, `data`, `timing`, `messages` keys - `data.action` (not `action_name`) - `data.project` (not `project_links`) - `data.automation` (profile name) - `data.attempt` - `data.progress` (phase progress steps) - `data.timing` (started, elapsed, eta) - `data.execution` (sandbox, tool_calls, files_modified, child_plans, checkpoints) - `data.cost` (tokens_used, cost_so_far, estimated) ## Actual Behavior The implementation uses `_plan_spec_dict(plan)` (see `src/cleveragents/cli/commands/plan.py` line 2734) which returns a flat dict without the command envelope. Missing: `command`, `status`, `exit_code`, `timing`, `messages`, `attempt`, `progress`, `execution`, `cost`. Wrong field names: `action_name` instead of `action`, `project_links` instead of `project`. ## Code Location - `src/cleveragents/cli/commands/plan.py` lines 2733–2735 (plan_status, non-rich output) ## Steps to Reproduce ```bash agents plan status <PLAN_ID> --format json ``` --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

Rows
Columns

UAT: agents plan status JSON/YAML output missing spec-required command envelope and uses wrong field names #6279