You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(cockpit): per-topic framework adapters in the AG-UI deployment generator
Generalizes scripts/generate-ag-ui-deployment-config.ts away from its
hardcoded LangGraph assumptions so a registry capability can declare which
AG-UI backend framework serves it:
- capability-registry: new optional 'framework' discriminator
('langgraph' | 'microsoft-agent-framework', default 'langgraph') and a
'runtimes' product for the one-capability-many-runtimes axis
(cockpit/runtimes/<runtime>/). No entries added — pure type extension.
- generator: FRAMEWORK_ADAPTERS maps framework -> {bridge import, per-topic
module import, FastAPI mount block}. LangGraph keeps the exact emitted
bytes; the MAF adapter mounts a module-level 'agent' object via
add_agent_framework_fastapi_endpoint (no wrapper class). Bridge imports
are emitted only for frameworks in use, langgraph first.
- generate-shared-deployment-config + serve-example treat 'runtimes' like
'ag-ui' (Railway-deployed uvicorn AG-UI backends, no langgraph.json).
- spec: adapter-branching tests plus a committed-artifact byte-equality
test mirroring the deploy-ag-ui drift check.
With only this change applied the generated deployments/ag-ui-dev
artifacts are byte-identical to the committed ones (verified via
regeneration + git diff).
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
0 commit comments