UAT: JSON/YAML envelope `messages` text is always generic `"ok"` instead of spec-required descriptive message #4869

New issue

Open

opened 2026-04-08 20:10:52 +00:00 by HAL9000 · 0 comments

HAL9000 commented

2026-04-08 20:10:52 +00:00

Owner

Bug Report

Feature Area: CLI Commands — JSON/YAML output envelope

What Was Tested

Runtime testing of multiple CLI commands with --format json output, comparing the messages field against the spec's required format.

Note: This is distinct from issue #4497 which reports messages being an empty dict {}. This issue reports that messages is correctly a list of {level, text} objects, but the text value is always the generic string "ok" instead of a descriptive message.

Expected Behavior (from spec)

The spec requires the messages field to contain descriptive, context-specific text. Examples from the spec:

agents session list: [{"level": "ok", "text": "2 sessions listed"}]
agents version: [{"level": "ok", "text": "Version reported"}]
agents info: [{"level": "ok", "text": "Environment loaded"}]
agents session create: [{"level": "ok", "text": "Session created"}]
agents plan use: [{"level": "ok", "text": "Plan created"}]

Actual Behavior

All commands return the same generic message regardless of what was done:

"messages": [
  {
    "level": "ok",
    "text": "ok"
  }
]

Verified across multiple commands:

agents --format json version → "text": "ok" (should be "Version reported")
agents --format json info → "text": "ok" (should be "Environment loaded")
agents --format json diagnostics → "text": "ok" (should be "N warnings require attention" or similar)
agents --format json session create → "text": "ok" (should be "Session created")
agents --format json session list → "text": "ok" (should be "N sessions listed")
agents --format json config list → "text": "ok" (should be "N keys listed")

Code Location

The messages field is populated in the output envelope construction. The generic "ok" text is likely a placeholder that was never replaced with command-specific messages. The issue is widespread across all commands that use the JSON output envelope.

Steps to Reproduce

agents --format json session list
# Output includes: "messages": [{"level": "ok", "text": "ok"}]
# Expected: "messages": [{"level": "ok", "text": "1 session listed"}]

Impact

Scripts and CI pipelines that parse the messages field to determine what happened (e.g., how many items were listed, whether warnings were raised) cannot rely on the messages field for any meaningful information. The spec explicitly uses descriptive messages to communicate operation results.

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

## Bug Report **Feature Area:** CLI Commands — JSON/YAML output envelope ### What Was Tested Runtime testing of multiple CLI commands with `--format json` output, comparing the `messages` field against the spec's required format. Note: This is distinct from issue #4497 which reports `messages` being an empty dict `{}`. This issue reports that `messages` is correctly a list of `{level, text}` objects, but the `text` value is always the generic string `"ok"` instead of a descriptive message. ### Expected Behavior (from spec) The spec requires the `messages` field to contain descriptive, context-specific text. Examples from the spec: - `agents session list`: `[{"level": "ok", "text": "2 sessions listed"}]` - `agents version`: `[{"level": "ok", "text": "Version reported"}]` - `agents info`: `[{"level": "ok", "text": "Environment loaded"}]` - `agents session create`: `[{"level": "ok", "text": "Session created"}]` - `agents plan use`: `[{"level": "ok", "text": "Plan created"}]` ### Actual Behavior All commands return the same generic message regardless of what was done: ```json "messages": [ { "level": "ok", "text": "ok" } ] ``` Verified across multiple commands: - `agents --format json version` → `"text": "ok"` (should be `"Version reported"`) - `agents --format json info` → `"text": "ok"` (should be `"Environment loaded"`) - `agents --format json diagnostics` → `"text": "ok"` (should be `"N warnings require attention"` or similar) - `agents --format json session create` → `"text": "ok"` (should be `"Session created"`) - `agents --format json session list` → `"text": "ok"` (should be `"N sessions listed"`) - `agents --format json config list` → `"text": "ok"` (should be `"N keys listed"`) ### Code Location The `messages` field is populated in the output envelope construction. The generic `"ok"` text is likely a placeholder that was never replaced with command-specific messages. The issue is widespread across all commands that use the JSON output envelope. ### Steps to Reproduce ```bash agents --format json session list # Output includes: "messages": [{"level": "ok", "text": "ok"}] # Expected: "messages": [{"level": "ok", "text": "1 session listed"}] ``` ### Impact Scripts and CI pipelines that parse the `messages` field to determine what happened (e.g., how many items were listed, whether warnings were raised) cannot rely on the messages field for any meaningful information. The spec explicitly uses descriptive messages to communicate operation results. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

Rows
Columns

UAT: JSON/YAML envelope messages text is always generic "ok" instead of spec-required descriptive message #4869