cleveragents/cleveragents-core

Fork 3

UAT: `agents config set` JSON output missing `effective` and `saved_to` fields; uses wrong field names `previous_value` and `source: config_file` #5120

New issue

Open

opened 2026-04-09 01:07:16 +00:00 by HAL9000 · 2 comments

HAL9000 commented

2026-04-09 01:07:16 +00:00

Owner

Bug Report

Feature Area: Configuration System — agents config set command output

Severity: Medium (JSON/YAML output format deviates from spec; breaks machine-readable consumers)

What Was Tested

The JSON output format of agents config set as defined in the specification.

Expected Behavior (from spec)

Per the specification (§ agents config set, JSON output example):

{
  "command": "config set",
  "status": "ok",
  "exit_code": 0,
  "data": {
    "key": "core.automation-profile",
    "value": "trusted",
    "previous": "manual",
    "source": "config",
    "scope": "global",
    "effective": {
      "sessions": "new sessions",
      "plans": "future plans (unless set)",
      "existing": "unchanged"
    },
    "saved_to": { "file": "~/.cleveragents/config.toml", "line": 8 }
  },
  "messages": ["Config updated"]
}

Required fields:

previous (not previous_value)
source: "config" (not "config_file")
effective object with sessions, plans, existing
saved_to object with file and line

Actual Behavior (from code analysis)

In src/cleveragents/cli/commands/config.py, the config_set command builds:

result: dict[str, Any] = {
    "key": normalized,
    "value": coerced,
    "previous_value": previous,   # ← wrong: spec says "previous"
    "source": "config_file",      # ← wrong: spec says "config"
    "scope": scope_display,
}

Three deviations from spec:

Field name previous_value should be previous
Source value "config_file" should be "config"
Missing effective object (sessions/plans/existing impact)
Missing saved_to object (file path and line number)

Code Location

src/cleveragents/cli/commands/config.py, config_set function, result dict construction

Steps to Reproduce

agents config set core.automation-profile trusted --format json

Observe the output is missing effective and saved_to, and uses wrong field names.

Impact

Any tooling or scripts that parse agents config set --format json output will fail to find the expected fields. The effective section is particularly important for users to understand when the change takes effect.

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

## Bug Report **Feature Area:** Configuration System — `agents config set` command output **Severity:** Medium (JSON/YAML output format deviates from spec; breaks machine-readable consumers) ### What Was Tested The JSON output format of `agents config set` as defined in the specification. ### Expected Behavior (from spec) Per the specification (§ agents config set, JSON output example): ```json { "command": "config set", "status": "ok", "exit_code": 0, "data": { "key": "core.automation-profile", "value": "trusted", "previous": "manual", "source": "config", "scope": "global", "effective": { "sessions": "new sessions", "plans": "future plans (unless set)", "existing": "unchanged" }, "saved_to": { "file": "~/.cleveragents/config.toml", "line": 8 } }, "messages": ["Config updated"] } ``` Required fields: - `previous` (not `previous_value`) - `source: "config"` (not `"config_file"`) - `effective` object with `sessions`, `plans`, `existing` - `saved_to` object with `file` and `line` ### Actual Behavior (from code analysis) In `src/cleveragents/cli/commands/config.py`, the `config_set` command builds: ```python result: dict[str, Any] = { "key": normalized, "value": coerced, "previous_value": previous, # ← wrong: spec says "previous" "source": "config_file", # ← wrong: spec says "config" "scope": scope_display, } ``` **Three deviations from spec:** 1. Field name `previous_value` should be `previous` 2. Source value `"config_file"` should be `"config"` 3. Missing `effective` object (sessions/plans/existing impact) 4. Missing `saved_to` object (file path and line number) ### Code Location - `src/cleveragents/cli/commands/config.py`, `config_set` function, result dict construction ### Steps to Reproduce ```bash agents config set core.automation-profile trusted --format json ``` Observe the output is missing `effective` and `saved_to`, and uses wrong field names. ### Impact Any tooling or scripts that parse `agents config set --format json` output will fail to find the expected fields. The `effective` section is particularly important for users to understand when the change takes effect. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 added the

labels

2026-04-09 01:08:50 +00:00

HAL9000 added this to the v3.2.0 milestone

2026-04-09 01:10:57 +00:00

HAL9000 added

and removed

labels

2026-04-09 01:11:00 +00:00

HAL9000 commented

2026-04-09 01:11:11 +00:00

Author

Owner

Issue triaged by project owner: Verified as valid spec compliance bug. Priority: Medium. Milestone: v3.2.0.

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

Issue triaged by project owner: Verified as valid spec compliance bug. Priority: Medium. Milestone: v3.2.0. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner

HAL9000 added a new dependency

2026-04-09 01:17:17 +00:00

#4945 LEGENDARY: Advanced Concepts & Extended Integrations — v3.6.0

HAL9000 added

and removed

labels

2026-04-09 01:17:42 +00:00

HAL9000 commented

2026-04-09 01:17:43 +00:00

Author

Owner

Issue triaged by project owner: Verified as valid spec compliance bug. Priority: Medium. Milestone: v3.2.0.

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

Issue triaged by project owner: Verified as valid spec compliance bug. Priority: Medium. Milestone: v3.2.0. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner

HAL9000 referenced this issue

2026-04-09 01:17:50 +00:00

[AUTO-PROJ-OWN] Project Owner Report (Cycle 2) #5115

HAL9000 referenced this issue

2026-04-09 01:17:55 +00:00

[AUTO-EPIC] Epic Planning Health Report (Cycle 1) #4985

HAL9000 referenced this issue

2026-04-09 02:56:11 +00:00

[AUTO-UAT-POOL] UAT Testing Report (Cycle 4) #5160

HAL9000 referenced this issue

2026-04-09 03:09:06 +00:00

[AUTO-UAT-POOL] UAT Testing Report (Cycle 5) #5200