cleveragents/cleveragents-core

Fork 3

UAT: JSON envelope omits command name #7968

New issue

Open

opened 2026-04-12 16:14:07 +00:00 by HAL9000 · 3 comments

HAL9000 commented

2026-04-12 16:14:07 +00:00

Owner

Summary

Feature area: CLI & Output Rendering
JSON/YAML outputs omit the command string that the specification requires in the envelope (docs/specification.md §1309–1344, §1412–1431). The CLI currently emits an empty string, which prevents consumers from correlating output with the invoked command.

Steps to Reproduce

From the repo root, run uv run agents --format json version.
Observe the top-level command and messages fields in the JSON envelope.

Expected Result

Per the specification, the envelope should include the full command string (e.g. "agents version") and a message reflecting that command, so downstream tooling can attribute the payload.

Actual Result

The command field is an empty string and the default message is just "ok":

{
  "command": "",
  "status": "ok",
  ...
  "messages": [{"level": "ok", "text": "ok"}]
}

Additional Notes

src/cleveragents/cli/formatting.py::format_output supports a command argument, but the core commands (version/info/diagnostics) never pass it, so the default empty string is emitted. The same omission affects other commands that call format_output via shared renderers.
Filling in the command path would also allow the default message text to be specific ("agents version completed").

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

## Summary - **Feature area:** CLI & Output Rendering - JSON/YAML outputs omit the `command` string that the specification requires in the envelope (docs/specification.md §1309–1344, §1412–1431). The CLI currently emits an empty string, which prevents consumers from correlating output with the invoked command. ## Steps to Reproduce 1. From the repo root, run `uv run agents --format json version`. 2. Observe the top-level `command` and `messages` fields in the JSON envelope. ## Expected Result - Per the specification, the envelope should include the full command string (e.g. `"agents version"`) and a message reflecting that command, so downstream tooling can attribute the payload. ## Actual Result - The `command` field is an empty string and the default message is just `"ok"`: ```json { "command": "", "status": "ok", ... "messages": [{"level": "ok", "text": "ok"}] } ``` ## Additional Notes - `src/cleveragents/cli/formatting.py::format_output` supports a `command` argument, but the core commands (version/info/diagnostics) never pass it, so the default empty string is emitted. The same omission affects other commands that call `format_output` via shared renderers. - Filling in the command path would also allow the default message text to be specific (`"agents version completed"`). --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

freemo added the

labels

2026-04-12 18:33:21 +00:00

HAL9000 added the

State

Unverified

label

2026-04-12 18:43:04 +00:00

HAL9000 referenced this issue

2026-04-12 19:32:29 +00:00

[AUTO-GROOMER] Backlog Grooming Report (Cycle 1) #8009

HAL9000 added

and removed

labels

2026-04-14 05:57:37 +00:00

HAL9000 commented

2026-04-14 05:57:38 +00:00

Author

Owner

✅ Verified — UAT bug: JSON envelope omits command name, violating spec. MoSCoW: Must-have. Priority: Medium.

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

✅ **Verified** — UAT bug: JSON envelope omits command name, violating spec. MoSCoW: Must-have. Priority: Medium. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor

HAL9000 commented

2026-04-14 06:10:57 +00:00

Author

Owner

✅ Verified — UAT bug: JSON envelope omits command name, violating spec. MoSCoW: Must-have. Priority: Medium.

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