Mirrors the mastra (#4326) and smalls-batch (#4361) patterns:
Frontend:
- agentic-chat: provider-setup + configure-suggestions in place; sibling
chat-component.snippet.tsx for the QA-laden Chat case.
- tool-rendering: render-weather-tool in place; sibling
render-flight-tool.snippet.tsx covering render-flight-tool +
catchall-renderer (production demo only registers a weather renderer).
- frontend-tools: frontend-tool-registration + frontend-tool-handler in place.
- readonly-state-agent-context: context-provider-sketch +
use-agent-context-call in place.
- open-gen-ui: minimal-provider-setup in page; minimal-runtime-flag and
advanced-runtime-config share a span in copilotkit-ogui/route.ts.
- open-gen-ui-advanced: multi-file sandbox-function-registration
(page.tsx + sandbox-functions.ts).
Backend:
- tool-rendering: weather-tool-backend on src/agents/agent.py
(added to manifest highlight).
- a2ui-fixed-schema: backend-schema-json-load + backend-render-operations
on src/agents/a2ui_fixed.py (already in manifest highlight).
Deferred (defer until showcase team aligns or auto-config infrastructure
ships):
- gen-ui-interrupt + interrupt-headless: ms-agent uses useFrontendTool
with a Promise-based handler instead of useInterrupt because MS Agent
Framework lacks a native interrupt primitive. The canonical regions
don't apply.
- chat-slots: production demo only registers the welcome slot; disclaimer
and assistant-message slots not implemented.
- declarative-gen-ui::runtime-inject-tool: cross-cutting (tracked separately).
ag2's agentic-chat already had provider-setup and configure-suggestions
in place; just adds the sibling chat-component.snippet.tsx (same as
mastra). tool-rendering follows the same mirror pattern: render-weather-tool
in place, weather-tool-backend wraps get_weather() in src/agents/agent.py
(already in manifest highlight), sibling render-flight-tool.snippet.tsx
covers render-flight-tool and catchall-renderer.
agentic-chat follows the mastra (#4326) pattern. The ogui route gains
the nested minimal-runtime-flag + advanced-runtime-config markers (same
shape as langgraph-python and strands).
agentic-chat follows the mastra (#4326) pattern. open-gen-ui regions
mirror langgraph-python's: minimal-provider-setup wraps the CopilotKit
JSX in page.tsx; minimal-runtime-flag and advanced-runtime-config share
a span in copilotkit-ogui/route.ts (per langgraph-python's nested-region
shape). open-gen-ui-advanced uses a multi-file region for
sandbox-function-registration (page.tsx + sandbox-functions.ts).
a2ui-fixed-schema deferred — strands has the demo folder but no a2ui
backend agent in src/agents/, so the schema-loading regions have no
local source to wrap. Picks up in a future pass once showcase team
ships the strands a2ui_fixed implementation.
Same pattern as langgraph-typescript. The weather-tool-backend region
already existed in src/agents/src/tool_rendering_agent.py; just added
the file to the manifest highlight so the bundler picks it up.
Mirrors the mastra (#4326) pattern:
- agentic-chat: provider-setup + configure-suggestions in place; sibling
chat-component.snippet.tsx for a minimal Chat that doesn't carry the
production demo's QA hooks.
- tool-rendering: render-weather-tool in place; weather-tool-backend in
src/agent/tool-rendering.ts (added to manifest highlight); sibling
render-flight-tool.snippet.tsx covering both render-flight-tool and
catchall-renderer regions (the production demo only registers a weather
renderer).
agent-config — empty stream
The /demos/agent-config runtime returned RUN_ERROR on every send. The
existing route wrapper repacked the provider's properties into
forwardedProps.config.configurable.properties so the agent could read
them via RunnableConfig["configurable"]["properties"]. LangGraph 1.x
(deployed langgraph 1.1.x / langgraph-api 0.7.x) now rejects any run
that sends configurable with "Cannot specify both configurable and
context. Prefer setting context alone." because it auto-injects an
empty context and refuses both channels at once.
Switch to LangGraph 1.x's context API: route wrapper repacks user props
onto forwardedProps.context instead, the Python graph defines
context_schema=AgentConfigContext and reads via the
Runtime[AgentConfigContext] parameter, and RunnableConfig is no longer
consulted. Unit tests updated to pass the flat context dict directly.
Add context to RESERVED_FORWARDED_PROPS_KEYS so a caller that
explicitly sets forwardedProps.context is preserved (and merged with
provider-supplied properties) instead of being treated as a user prop
and double-wrapped.
multimodal — PDF "doesn't work"
The multimodal pipeline (legacy-shape rewrite shim → ag-ui-langgraph
converter → _PdfFlattenMiddleware running pypdf) is fine; sample.pdf
extraction shows up correctly in the run state snapshot. The visible
breakage is the aimock fixture file: aimock matches userMessage as a
substring, and the generic "hi" fixture lives early enough to swallow
any prompt containing "this" — including "What is in this PDF?" and
"What is in this image?" — short-circuiting before the request reaches
real OpenAI and returning a generic "I'm your showcase assistant"
greeting that never references the attachment.
Add two more-specific fixtures ("this PDF", "this image") ahead of the
"hi" entry so multimodal prompts return responses grounded in the
bundled samples. The "hi" fixture stays in place so the several E2E
specs that fill literal "hi" still match it.
Replace sys.path.insert hacks in Python agent files with direct
imports via symlinks to shared/{python,typescript}/tools.
Update Dockerfiles, entrypoints, and configs to support the new
symlink-based tool resolution. Add PARITY_NOTES for frameworks
that have known gaps.
The showcase framework directories better reflect their role as
integration examples rather than distributable packages.
Renames showcase/packages/ -> showcase/integrations/ and updates
the test docker-compose file reference accordingly.
Sam Julien