UAT: ACMS indexing pipeline is not wired into CLI commands #6287

New issue

Open

opened 2026-04-09 19:49:40 +00:00 by HAL9000 · 0 comments

HAL9000 commented

2026-04-09 19:49:40 +00:00

Owner

Summary

The ACMS indexing pipeline (UKO indexer) is not accessible from the CLI even though the spec requires it.
agents repo index only triggers RepoIndexingService and never invokes UKOIndexer, so UKO/CRP backends remain empty after CLI indexing.
Users have no supported way to populate ACMS graph/text/vector stores via CLI workflows.

Steps to Reproduce

Run agents repo index local/my-project (or agents repo index <resource>).
Check the code path: src/cleveragents/cli/commands/repo.py calls into RepoIndexingService only.
Inspect ACMS backends or logs – no calls to UKOIndexer, no UKO triples stored.

Observed

DI container registers UKOIndexer, but no CLI service or command wires it in.
uko_indexer.py and uko_indexer_internals.py are never used in CLI code paths, so ACMS indexing never runs.

Expected

After repository indexing, the CLI should invoke the ACMS indexing pipeline (UKO indexer) so ACMS graph/text/vector stores are populated per spec requirement 10.
Users should not need to call internal services manually to keep ACMS indexes current.

References

src/cleveragents/cli/commands/repo.py
src/cleveragents/application/services/uko_indexer.py
src/cleveragents/application/container.py (registers uko_indexer singleton).

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

## Summary - The ACMS indexing pipeline (UKO indexer) is not accessible from the CLI even though the spec requires it. - `agents repo index` only triggers `RepoIndexingService` and never invokes `UKOIndexer`, so UKO/CRP backends remain empty after CLI indexing. - Users have no supported way to populate ACMS graph/text/vector stores via CLI workflows. ## Steps to Reproduce 1. Run `agents repo index local/my-project` (or `agents repo index <resource>`). 2. Check the code path: `src/cleveragents/cli/commands/repo.py` calls into `RepoIndexingService` only. 3. Inspect ACMS backends or logs – no calls to `UKOIndexer`, no UKO triples stored. ## Observed - DI container registers `UKOIndexer`, but no CLI service or command wires it in. - `uko_indexer.py` and `uko_indexer_internals.py` are never used in CLI code paths, so ACMS indexing never runs. ## Expected - After repository indexing, the CLI should invoke the ACMS indexing pipeline (UKO indexer) so ACMS graph/text/vector stores are populated per spec requirement 10. - Users should not need to call internal services manually to keep ACMS indexes current. ## References - `src/cleveragents/cli/commands/repo.py` - `src/cleveragents/application/services/uko_indexer.py` - `src/cleveragents/application/container.py` (registers `uko_indexer` singleton). --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

Rows
Columns