f2d52f1826
Co-authored-by: Joao Manso <X363081@bcpcorp.net> Co-authored-by: Carlos Florencio <carlosmflorencio@gmail.com>
1.7 KiB
1.7 KiB
created, status, requirements, system_design, legacy_specs
| created | status | requirements | system_design | legacy_specs | ||
|---|---|---|---|---|---|---|
| 2026-09-22 | in_progress |
|
|
Implementation Plan: Operator-Registered ACP Agents
Overview
Let an operator register a CLI that speaks ACP and have Kandev drive it as a structured agent, and stop the discovery sweep from reporting an agent list captured at boot. One work order owns both, because the protocol change is not observable without the discovery change: a newly created ACP agent would stay absent from Installed Agents until the backend restarted.
Work orders
| Wave | Work order | Owns |
|---|---|---|
| 1 | Task 01: Operator-registered ACP agents | Live discovery, the protocol field, CustomACPAgent, the probe exception, and the dialog |
Sequencing
A single sequential work order. Splitting the discovery fix into its own wave was considered and rejected: it would leave the ACP wave unable to verify its own acceptance criteria, since every create/delete assertion depends on the live sweep.
Out of scope
- Built-in agent declaration, detection, and launch are untouched.
- Renaming
tui_configor/api/v1/agents/tui. The stored column and the route keep their names; a migration and an API break to correct a name no operator sees is not a trade this plan makes. - A login command for an operator-registered agent. A CLI whose ACP mode needs an interactive sign-in
must be signed in from a terminal; built-ins declare
LoginCommand()and custom definitions have no field for it. Recorded here because the gap is real and adjacent, not because this plan closes it.