cleveragents/cleveragents-core

Fork 3

UAT: `agents session create` missing `--name` option — session naming not supported via CLI #5843

New issue

Open

opened 2026-04-09 10:35:19 +00:00 by HAL9000 · 1 comment

HAL9000 commented

2026-04-09 10:35:19 +00:00

Owner

Bug Report

Feature Area: Session Management — agents session create
Severity: Backlog (naming is a convenience feature)

What Was Tested

Code-level analysis of src/cleveragents/cli/commands/session.py — the create command.

Expected Behavior

The Session domain model (session.py line 206) has a name field:

name: str | None = Field(
    default=None,
    description="Optional human-readable name for this session",
)

The SessionModel database model also has a name column (line 2075):

name = Column(String(255), nullable=True)

The agents session list output uses session.name for display (line 145):

most_recent = sorted_sessions[0].name or sorted_sessions[0].session_id[:8]

Users should be able to create a named session: agents session create --name "my-feature-work".

Actual Behavior (from code)

The create command (session.py lines 171–260) only accepts --actor and --format options:

@app.command()
def create(
    actor: Annotated[
        str | None,
        typer.Option("--actor", help="Orchestrator actor name (namespace/name)"),
    ] = None,
    fmt: Annotated[
        str,
        typer.Option("--format", "-f", help=_FORMAT_HELP),
    ] = "rich",
) -> None:

There is no --name option. The service.create() call (line 194) also does not accept a name parameter:

session = service.create(actor_name=actor)

The SessionService.create() abstract method signature only accepts actor_name.

Code Location

src/cleveragents/cli/commands/session.py, lines 171–260 (create command)
src/cleveragents/application/services/session_service.py, create() method — missing name parameter
src/cleveragents/domain/models/core/session.py, SessionService.create() ABC — missing name parameter

Impact

Users cannot assign human-readable names to sessions via the CLI. Sessions can only be identified by their ULID, which is not user-friendly. The name field in the domain model and database is effectively unused.

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

## Bug Report **Feature Area:** Session Management — `agents session create` **Severity:** Backlog (naming is a convenience feature) ## What Was Tested Code-level analysis of `src/cleveragents/cli/commands/session.py` — the `create` command. ## Expected Behavior The `Session` domain model (`session.py` line 206) has a `name` field: ```python name: str | None = Field( default=None, description="Optional human-readable name for this session", ) ``` The `SessionModel` database model also has a `name` column (line 2075): ```python name = Column(String(255), nullable=True) ``` The `agents session list` output uses `session.name` for display (line 145): ```python most_recent = sorted_sessions[0].name or sorted_sessions[0].session_id[:8] ``` Users should be able to create a named session: `agents session create --name "my-feature-work"`. ## Actual Behavior (from code) The `create` command (`session.py` lines 171–260) only accepts `--actor` and `--format` options: ```python @app.command() def create( actor: Annotated[ str | None, typer.Option("--actor", help="Orchestrator actor name (namespace/name)"), ] = None, fmt: Annotated[ str, typer.Option("--format", "-f", help=_FORMAT_HELP), ] = "rich", ) -> None: ``` There is no `--name` option. The `service.create()` call (line 194) also does not accept a `name` parameter: ```python session = service.create(actor_name=actor) ``` The `SessionService.create()` abstract method signature only accepts `actor_name`. ## Code Location - `src/cleveragents/cli/commands/session.py`, lines 171–260 (`create` command) - `src/cleveragents/application/services/session_service.py`, `create()` method — missing `name` parameter - `src/cleveragents/domain/models/core/session.py`, `SessionService.create()` ABC — missing `name` parameter ## Impact Users cannot assign human-readable names to sessions via the CLI. Sessions can only be identified by their ULID, which is not user-friendly. The `name` field in the domain model and database is effectively unused. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 added the

labels

2026-04-09 10:42:48 +00:00

~~HAL9000 referenced this issue 2026-04-09 10:56:39 +00:00~~

[AUTO-UAT-POOL] UAT Testing Report (Cycle 1) #5750

HAL9000 added

and removed

labels

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

HAL9000 referenced this issue

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

UAT: SessionRepository.update() does not persist name field — session name changes lost on update #5859

HAL9000 added a new dependency

2026-04-09 12:20:44 +00:00

#4949 EPIC: A2A Local Facade & Event Queue — Session/Plan Lifecycle Operations

HAL9000 referenced this issue

2026-04-09 12:32:04 +00:00

[AUTO-EPIC] Epic Planning Health Report (Cycle 13) #5737

HAL9000 added this to the v3.5.0 milestone

2026-04-09 12:49:37 +00:00

HAL9000 commented

2026-04-09 12:53:25 +00:00

Author

Owner

Milestone compliance fix applied:

Assigned to milestone: v3.5.0 (Autonomy Hardening)
Reason: Issue is State/Verified but had no milestone assigned. Session management CLI features belong to v3.5.0 scope (A2A facade session and plan lifecycle operations functional via CLI).

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: backlog-groomer

Milestone compliance fix applied: - Assigned to milestone: **v3.5.0** (Autonomy Hardening) - Reason: Issue is `State/Verified` but had no milestone assigned. Session management CLI features belong to v3.5.0 scope (A2A facade session and plan lifecycle operations functional via CLI). --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer

HAL9000 referenced this issue

2026-04-09 13:32:13 +00:00

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