cleveragents/cleveragents-core

Fork 3

EPIC: Server Client Implementations — Replace Stubs with Real Clients #4956

New issue

Open

opened 2026-04-08 23:40:09 +00:00 by freemo · 1 comment

freemo commented

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

Owner

Epic: Server Client Implementations

This Epic covers replacing the stub server client implementations (StubServerClient, StubRemoteExecutionClient, StubAuthClient) with real implementations that connect to actual servers.

Demonstrable Capability

When this Epic is complete, a developer can:

Connect CleverAgents to a real server using agents server connect
Execute plans remotely via StubRemoteExecutionClient → real RemoteExecutionClient
Authenticate with the server using --token option
Disconnect from the server using agents server disconnect
Resolve server mode as connected (not just disabled/stubbed)

Child Issues

Definition of Done

All child issues are closed
StubServerClient replaced with real ServerClient
StubRemoteExecutionClient replaced with real RemoteExecutionClient
StubAuthClient replaced with real AuthClient
agents server connect --token option works
agents server disconnect command implemented
resolve_server_mode() returns connected for active connections
All nox stages pass
Coverage >= 97%

Metadata

Branch Naming Convention: feat/m6/server-clients
Milestone: v3.5.0
Parent Legendary: #4944

Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planner

## Epic: Server Client Implementations This Epic covers replacing the stub server client implementations (`StubServerClient`, `StubRemoteExecutionClient`, `StubAuthClient`) with real implementations that connect to actual servers. ### Demonstrable Capability When this Epic is complete, a developer can: 1. Connect CleverAgents to a real server using `agents server connect` 2. Execute plans remotely via `StubRemoteExecutionClient` → real `RemoteExecutionClient` 3. Authenticate with the server using `--token` option 4. Disconnect from the server using `agents server disconnect` 5. Resolve server mode as `connected` (not just `disabled`/`stubbed`) ### Child Issues  ### Definition of Done - [ ] All child issues are closed - [ ] `StubServerClient` replaced with real `ServerClient` - [ ] `StubRemoteExecutionClient` replaced with real `RemoteExecutionClient` - [ ] `StubAuthClient` replaced with real `AuthClient` - [ ] `agents server connect --token` option works - [ ] `agents server disconnect` command implemented - [ ] `resolve_server_mode()` returns `connected` for active connections - [ ] All nox stages pass - [ ] Coverage >= 97% ## Metadata - **Branch Naming Convention**: `feat/m6/server-clients` - **Milestone**: v3.5.0 - **Parent Legendary**: #4944 --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planner

freemo added the

labels

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

freemo added a new dependency

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

#4944 LEGENDARY: Autonomy Hardening — Full Autonomous Execution, Safety & A2A Facade

freemo added a new dependency

2026-04-08 23:42:08 +00:00

#4908 UAT: StubServerClient, StubRemoteExecutionClient, StubAuthClient raise NotImplementedError — no real server client implementations exist

freemo added a new dependency

2026-04-08 23:42:53 +00:00

#4936 UAT: Remote plan execution client (StubRemoteExecutionClient) raises NotImplementedError — server-side plan execution impossible

freemo referenced this issue

2026-04-08 23:43:07 +00:00

LEGENDARY: Autonomy Hardening — Full Autonomous Execution, Safety & A2A Facade #4944

HAL9000 commented

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

Owner

Issue triaged by project owner:

State: Verified
Priority: High — Replacing stub server clients with real implementations is critical; current stubs raise NotImplementedError blocking all server-side functionality
Milestone: v3.5.0
Story Points: 34 — XXL — Epic covering all stub client replacements: RemoteExecutionClient, namespace operations, entity sync, and registry operations
MoSCoW: Must Have — The stub clients are explicitly blocking UAT tests (issues #4933, #4935, #4936, #4939); real implementations are required for any server functionality to work
Parent Legendary: #4944

This Epic is valid and urgent. Multiple UAT failures (#4931, #4933, #4935, #4936, #4939) are directly caused by stub implementations.

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

Issue triaged by project owner: - **State**: Verified - **Priority**: High — Replacing stub server clients with real implementations is critical; current stubs raise NotImplementedError blocking all server-side functionality - **Milestone**: v3.5.0 - **Story Points**: 34 — XXL — Epic covering all stub client replacements: RemoteExecutionClient, namespace operations, entity sync, and registry operations - **MoSCoW**: Must Have — The stub clients are explicitly blocking UAT tests (issues #4933, #4935, #4936, #4939); real implementations are required for any server functionality to work - **Parent Legendary**: #4944 This Epic is valid and urgent. Multiple UAT failures (#4931, #4933, #4935, #4936, #4939) are directly caused by stub implementations. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner

HAL9000 added

and removed

labels

2026-04-09 00:48:22 +00:00

HAL9000 added this to the v3.5.0 milestone