cleveragents/cleveragents-core

Fork 3

UAT: `agents server connect` missing `--token` option — authentication token cannot be set during connection #4891

New issue

Open

opened 2026-04-08 20:16:18 +00:00 by HAL9000 · 2 comments

HAL9000 commented

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

Owner

Bug Report

Feature Area: Server Mode — agents server connect command

What Was Tested

The agents server connect command and its ability to configure all required server connection parameters per the spec.

Expected Behavior (from spec)

Per ADR-023 (Server Mode) and the spec's server.* configuration section:

server.token is required when server.url is set: "Authentication token for server mode. Required when server.url is set. Obtained via server registration or team invite flow."
The connection lifecycle requires authentication via Authorization: Bearer <server.token> header on every request.
agents server connect is the primary command for configuring a server connection.

The connect command should accept a --token (or --auth-token) option to set the authentication token as part of the connection setup workflow, since the token is always required alongside the URL.

Actual Behavior (from code)

File: src/cleveragents/cli/commands/server.py

The server_connect command only persists three settings:

svc.set_value("server.url", config.server_url)
svc.set_value("server.namespace", config.namespace)
svc.set_value("server.tls-verify", config.tls_verify)

There is no --token parameter on the server_connect command. The ServerConnectionConfig model has auth_token_ref but it is not exposed as a CLI option. Users must separately run agents config set server.token <token> to complete the connection setup — a non-obvious two-step workflow that breaks the connection UX.

Steps to Reproduce

$ agents server connect https://agents.example.com --help
# No --token option visible
$ agents server connect https://agents.example.com
# Token not set — server mode will fail authentication on first use

Code Location

src/cleveragents/cli/commands/server.py — server_connect() function
src/cleveragents/a2a/server_config.py — ServerConnectionConfig model (has auth_token_ref but not exposed)

Impact

Users connecting to a server must perform a non-obvious two-step workflow (connect + config set) to complete authentication setup. The server connect command gives a false sense of completion when the token is not set.

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

## Bug Report **Feature Area:** Server Mode — `agents server connect` command ### What Was Tested The `agents server connect` command and its ability to configure all required server connection parameters per the spec. ### Expected Behavior (from spec) Per ADR-023 (Server Mode) and the spec's `server.*` configuration section: - `server.token` is **required** when `server.url` is set: *"Authentication token for server mode. Required when `server.url` is set. Obtained via server registration or team invite flow."* - The connection lifecycle requires authentication via `Authorization: Bearer <server.token>` header on every request. - `agents server connect` is the primary command for configuring a server connection. The `connect` command should accept a `--token` (or `--auth-token`) option to set the authentication token as part of the connection setup workflow, since the token is always required alongside the URL. ### Actual Behavior (from code) **File:** `src/cleveragents/cli/commands/server.py` The `server_connect` command only persists three settings: ```python svc.set_value("server.url", config.server_url) svc.set_value("server.namespace", config.namespace) svc.set_value("server.tls-verify", config.tls_verify) ``` There is **no `--token` parameter** on the `server_connect` command. The `ServerConnectionConfig` model has `auth_token_ref` but it is not exposed as a CLI option. Users must separately run `agents config set server.token <token>` to complete the connection setup — a non-obvious two-step workflow that breaks the connection UX. ### Steps to Reproduce ```bash $ agents server connect https://agents.example.com --help # No --token option visible $ agents server connect https://agents.example.com # Token not set — server mode will fail authentication on first use ``` ### Code Location - `src/cleveragents/cli/commands/server.py` — `server_connect()` function - `src/cleveragents/a2a/server_config.py` — `ServerConnectionConfig` model (has `auth_token_ref` but not exposed) ### Impact Users connecting to a server must perform a non-obvious two-step workflow (connect + config set) to complete authentication setup. The `server connect` command gives a false sense of completion when the token is not set. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 referenced this issue

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

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

HAL9000 referenced this issue

2026-04-08 20:18:58 +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:23 +00:00

freemo commented

2026-04-08 23:40:14 +00:00

Owner

Issue triaged by project owner:

State: Verified
Priority: Medium — Missing --token option on agents server connect; authentication cannot be configured
Milestone: v3.5.0 (Autonomy Hardening — server mode)
Story Points: 2 — S — Adding a CLI option is a small task
MoSCoW: Must Have — Authentication token is required for secure server connections per spec
Parent Epic: #4947 (Server Implementation Legendary)

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

Issue triaged by project owner: - **State**: Verified - **Priority**: Medium — Missing `--token` option on `agents server connect`; authentication cannot be configured - **Milestone**: v3.5.0 (Autonomy Hardening — server mode) - **Story Points**: 2 — S — Adding a CLI option is a small task - **MoSCoW**: Must Have — Authentication token is required for secure server connections per spec - **Parent Epic**: #4947 (Server Implementation Legendary) --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner

freemo added

and removed

labels

2026-04-08 23:40:37 +00:00

freemo added this to the v3.5.0 milestone

2026-04-08 23:40:54 +00:00

freemo added a new dependency

2026-04-08 23:41:03 +00:00

#4947 LEGENDARY: Server Implementation — A2A Protocol, Multi-User & Team Collaboration

freemo added

and removed

labels

2026-04-08 23:41:31 +00:00

freemo commented

2026-04-08 23:41:51 +00:00

Owner

Issue triaged by project owner:

State: Verified
Priority: Medium — agents server connect missing --token option for authentication
Milestone: v3.5.0 — Server connect authentication is M6 scope
Story Points: 3 — M — Adding --token option to server connect command
MoSCoW: Should Have — Token auth is needed for server mode but not blocking local workflow
Parent Epic: #360 (Autonomy Hardening + Stubs M6)

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

Issue triaged by project owner: - **State**: Verified - **Priority**: Medium — `agents server connect` missing `--token` option for authentication - **Milestone**: v3.5.0 — Server connect authentication is M6 scope - **Story Points**: 3 — M — Adding `--token` option to server connect command - **MoSCoW**: Should Have — Token auth is needed for server mode but not blocking local workflow - **Parent Epic**: #360 (Autonomy Hardening + Stubs M6) --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner