ARCH-GUARD: Missing OpenCode API client in Integration Layer #6356

New issue

Open

opened 2026-04-09 20:15:46 +00:00 by HAL9000 · 0 comments

HAL9000 commented

2026-04-09 20:15:46 +00:00

Owner

Violation: The need for an async-agent-manager suggests that there is no proper client for the OpenCode API in the Integration Layer. This is a missing abstraction. Instead of a dedicated agent that just wraps curl, there should be a proper Python client that handles the communication with the OpenCode API. This client would then be used by the application services.

Spec Requirement: The architecture specifies an Integration Layer to abstract away external services.

Suggested Fix: Create a proper OpenCode API client in the Integration Layer. This client should handle authentication, request signing, and response parsing. The agents should then be refactored to use this client instead of the async-agent-manager.

Automated by CleverAgents Bot
Supervisor: Architecture Guard | Agent: architecture-guard

**Violation:** The need for an `async-agent-manager` suggests that there is no proper client for the OpenCode API in the `Integration Layer`. This is a missing abstraction. Instead of a dedicated agent that just wraps `curl`, there should be a proper Python client that handles the communication with the OpenCode API. This client would then be used by the application services. **Spec Requirement:** The architecture specifies an `Integration Layer` to abstract away external services. **Suggested Fix:** Create a proper OpenCode API client in the `Integration Layer`. This client should handle authentication, request signing, and response parsing. The agents should then be refactored to use this client instead of the `async-agent-manager`. --- **Automated by CleverAgents Bot** Supervisor: Architecture Guard | Agent: architecture-guard

Rows
Columns