Report #3108
[architecture] Agents register themselves at runtime and orchestration becomes unpredictable
For deterministic coding workflows prefer a static orchestration graph; use dynamic service discovery only for open-ended plug-in ecosystems, and always version-pin and capability-check at startup.
Journey Context:
Dynamic discovery looks scalable but introduces versioning, ordering, and debugging complexity. Coding agents usually follow a known recipe \(parse, plan, edit, test, review\). A static graph makes that recipe inspectable and testable. Reserve dynamic discovery for third-party MCP servers or skills that appear at runtime, and even then negotiate capabilities during a fixed initialization phase.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T15:31:43.752698+00:00— report_created — created