UAT: `agents actor add` uses `--config` option instead of spec-required positional `<YAML_FILE>` argument #6306

New issue

Open

opened 2026-04-09 20:08:27 +00:00 by HAL9000 · 0 comments

HAL9000 commented

2026-04-09 20:08:27 +00:00

Owner

Summary

The spec defines agents actor add <NAME> <YAML_FILE> where <YAML_FILE> is a positional argument. The implementation accepts <NAME> as a positional argument but requires the YAML file path via a --config option (agents actor add <NAME> --config <FILE>). This means any scripts or users following the spec signature will fail with "missing argument" errors.

Spec Reference

docs/specification.md — Actor Commands:

agents actor add <NAME> <YAML_FILE>

Registers an actor from YAML config
Both <NAME> and <YAML_FILE> are positional

Code Location

src/cleveragents/cli/commands/actor.py, lines 507–655

@app.command()
def add(
    name: Annotated[str, typer.Argument(...)],             # line 509 — positional ✓
    config: Annotated[
        Path | None,
        typer.Option("--config", "-c", ...),               # line 516 — OPTION, not positional
    ] = None,
    ...
) -> None:

The docstring at lines 551–558 even acknowledges the non-spec signature:

Signature:
    agents actor add <NAME> --config <FILE> ...

Steps to Reproduce

# Spec-compliant invocation
agents actor add local/my-actor ./my-actor.yaml
# Result: Error — positional argument 'YAML_FILE' is treated as a second NAME argument

# Required invocation (implementation)
agents actor add local/my-actor --config ./my-actor.yaml

Expected vs Actual

	Expected	Actual
Command signature	`add <NAME> <YAML_FILE>`	`add <NAME> --config <FILE>`
YAML file arg type	Positional	Named option

Impact

Any automation or documentation following the spec signature will fail. Users must know the undocumented --config option to register actors.

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

## Summary The spec defines `agents actor add <NAME> <YAML_FILE>` where `<YAML_FILE>` is a **positional argument**. The implementation accepts `<NAME>` as a positional argument but requires the YAML file path via a `--config` option (`agents actor add <NAME> --config <FILE>`). This means any scripts or users following the spec signature will fail with "missing argument" errors. ## Spec Reference `docs/specification.md` — Actor Commands: ``` agents actor add <NAME> <YAML_FILE> ``` - Registers an actor from YAML config - Both `<NAME>` and `<YAML_FILE>` are positional ## Code Location `src/cleveragents/cli/commands/actor.py`, lines 507–655 ```python @app.command() def add( name: Annotated[str, typer.Argument(...)], # line 509 — positional ✓ config: Annotated[ Path | None, typer.Option("--config", "-c", ...), # line 516 — OPTION, not positional ] = None, ... ) -> None: ``` The docstring at lines 551–558 even acknowledges the non-spec signature: ``` Signature: agents actor add <NAME> --config <FILE> ... ``` ## Steps to Reproduce ```bash # Spec-compliant invocation agents actor add local/my-actor ./my-actor.yaml # Result: Error — positional argument 'YAML_FILE' is treated as a second NAME argument # Required invocation (implementation) agents actor add local/my-actor --config ./my-actor.yaml ``` ## Expected vs Actual | | Expected | Actual | |---|---|---| | Command signature | `add <NAME> <YAML_FILE>` | `add <NAME> --config <FILE>` | | YAML file arg type | Positional | Named option | ## Impact Any automation or documentation following the spec signature will fail. Users must know the undocumented `--config` option to register actors. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 referenced this issue

2026-04-09 20:18:09 +00:00

[AUTO-UAT-POOL] UAT Testing Report (Cycle 3) #6294

HAL9000 added the

labels

2026-04-09 20:19:27 +00:00