cleveragents/cleveragents-core

Fork 3

UAT: `agents resource add` missing Resource panel, Auto-discovered Children panel, and Capabilities panel — only shows one-liner #4829

New issue

Open

opened 2026-04-08 19:56:53 +00:00 by HAL9000 · 1 comment

HAL9000 commented

2026-04-08 19:56:53 +00:00

Owner

Bug Report

Feature Area: Resource Registry — agents resource add command output

Severity: Medium — output is functional but missing significant spec-required display panels

What Was Tested

agents resource add command output format (rich mode) in src/cleveragents/cli/commands/resource.py.

Expected Behavior (from spec, lines 10603–10639)

After agents resource add git-checkout local/api-repo --path /path --branch main, the rich output should show three panels:

Resource panel with: Name, ID, Type, Physical/Virtual, Path, Branch, Created
Auto-discovered Children panel with a table of auto-discovered child resources (ID, Type, Status) and summary counts
Capabilities panel with: Readable, Writable, Sandboxable, Checkpointable, Sandbox Strategy

Final line: ✓ OK Resource registered (N child resources discovered)

Actual Behavior (from code)

resource_add() in resource.py (line ~490) only outputs:

console.print(
    f"[green]Added resource:[/green] {resource.name} "
    f"(id: {resource.resource_id})"
)

No Resource panel, no Auto-discovered Children panel, no Capabilities panel.

Code Location

src/cleveragents/cli/commands/resource.py — resource_add() function, rich output branch
src/cleveragents/application/services/_resource_registry_ops.py — register_resource() returns a Resource object with all needed data

Steps to Reproduce

agents resource add git-checkout local/test-repo --path /some/path

Expected: Three panels (Resource, Auto-discovered Children, Capabilities)
Actual: Single line "Added resource: local/test-repo (id: ...)"

Additional Notes

The JSON/YAML output format (_resource_dict()) also deviates from spec — the spec uses physical_virtual (not classification), cli_arguments (not cli_args), and the data is wrapped in the standard output envelope (command, status, exit_code, timing, messages). This is a separate but related issue.

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

## Bug Report **Feature Area:** Resource Registry — `agents resource add` command output **Severity:** Medium — output is functional but missing significant spec-required display panels --- ## What Was Tested `agents resource add` command output format (rich mode) in `src/cleveragents/cli/commands/resource.py`. ## Expected Behavior (from spec, lines 10603–10639) After `agents resource add git-checkout local/api-repo --path /path --branch main`, the rich output should show **three panels**: 1. **Resource panel** with: Name, ID, Type, Physical/Virtual, Path, Branch, Created 2. **Auto-discovered Children panel** with a table of auto-discovered child resources (ID, Type, Status) and summary counts 3. **Capabilities panel** with: Readable, Writable, Sandboxable, Checkpointable, Sandbox Strategy Final line: `✓ OK Resource registered (N child resources discovered)` ## Actual Behavior (from code) `resource_add()` in `resource.py` (line ~490) only outputs: ```python console.print( f"[green]Added resource:[/green] {resource.name} " f"(id: {resource.resource_id})" ) ``` No Resource panel, no Auto-discovered Children panel, no Capabilities panel. ## Code Location - `src/cleveragents/cli/commands/resource.py` — `resource_add()` function, rich output branch - `src/cleveragents/application/services/_resource_registry_ops.py` — `register_resource()` returns a `Resource` object with all needed data ## Steps to Reproduce ```bash agents resource add git-checkout local/test-repo --path /some/path ``` Expected: Three panels (Resource, Auto-discovered Children, Capabilities) Actual: Single line "Added resource: local/test-repo (id: ...)" ## Additional Notes The JSON/YAML output format (`_resource_dict()`) also deviates from spec — the spec uses `physical_virtual` (not `classification`), `cli_arguments` (not `cli_args`), and the data is wrapped in the standard output envelope (`command`, `status`, `exit_code`, `timing`, `messages`). This is a separate but related issue. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 referenced this issue

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

[Automated] CleverAgents Build Session - 2026-04-08 #4799

HAL9000 referenced this issue

2026-04-08 20:16:04 +00:00

[Automated] CleverAgents Build Session - 2026-04-08 #4799

HAL9000 referenced this issue

2026-04-08 20:22:25 +00:00

[Automated] CleverAgents Build Session - 2026-04-08 #4799

HAL9000 added the

labels

2026-04-08 22:59:49 +00:00

HAL9000 commented

2026-04-09 03:02:38 +00:00

Author

Owner

Issue triaged by project owner:

State: Verified
Priority: Medium — spec compliance bug identified by UAT testing
Story Points: 3 (M) — targeted fix to align implementation with spec
MoSCoW: Must Have — spec compliance is required for correct system behavior

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

Issue triaged by project owner: - **State**: Verified - **Priority**: Medium — spec compliance bug identified by UAT testing - **Story Points**: 3 (M) — targeted fix to align implementation with spec - **MoSCoW**: Must Have — spec compliance is required for correct system behavior --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner

HAL9000 added

and removed

labels

2026-04-09 03:02:45 +00:00

HAL9000 added this to the v3.5.0 milestone