feat(cockpit): register ag-ui examples in sidebar + capability modules#576
Merged
Conversation
PR #567 added the ag-ui section to the cockpit-registry manifest and shipped two examples (interrupts, streaming), but the cockpit app itself never picked them up. Two hardcoded spots in apps/cockpit/src/lib/route-resolution.ts: - `capabilityModules` is a static import-and-array list. Without entries for the ag-ui descriptors, `capabilityModules.find(... product === 'ag-ui' ...)` returned undefined, so RunMode rendered "No runtime available" even when the route resolved. - `buildNavigationTree` hardcoded the products array to the original four (deep-agents, langgraph, render, chat), so ag-ui examples were filtered out of the sidebar entirely. This PR adds both: imports + array entries for agUi{Interrupts,Streaming}PythonModule, and inserts 'ag-ui' between 'langgraph' and 'render' to match APPROVED_TOPICS ordering. After this lands + cockpit redeploys, the AG-UI section appears in the sidebar and the Code/Docs/API tabs work. The Run tab still says "No runtime available" — that depends on a hosted ag-ui runtime, which is Phase 2 (a real infra brainstorm for hosting uvicorn ag-ui-langgraph apps). Spec test for buildNavigationTree updated to expect 5 products with ag-ui in position 3.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes the cockpit-side gap I surfaced while finishing #571: even though PR #567 added `ag-ui` to the cockpit-registry manifest and shipped two standalone examples (`cockpit/ag-ui/interrupts`, `cockpit/ag-ui/streaming`), the cockpit app itself never picked them up. Two hardcoded spots in `apps/cockpit/src/lib/route-resolution.ts` needed parallel updates:
This PR adds both: static imports + array entries for `agUiInterruptsPythonModule` / `agUiStreamingPythonModule`, and inserts `'ag-ui'` between `'langgraph'` and `'render'` to match the manifest's `APPROVED_TOPICS` ordering.
After this lands + cockpit redeploys: the AG-UI section appears in the sidebar; Code, Docs, and API tabs all work (they read from the imported descriptors' asset paths). The Run tab will still say "No runtime available" — that depends on hosting a uvicorn `ag-ui-langgraph` runtime somewhere reachable, which is Phase 2 (a real infra brainstorm — LangGraph Cloud can't host FastAPI apps).
Test `buildNavigationTree > groups manifest entries by product and section` updated to expect 5 products with `'ag-ui'` in position 3.
Test Plan
🤖 Generated with Claude Code