mirror of
https://github.com/CopilotKit/CopilotKit.git
synced 2026-09-14 16:26:20 +08:00
Sam Julien
e70bd26b0f
Adds @region[frontend-useinterrupt-render] and @region[backend-interrupt-tool] markers to the gen-ui-interrupt demo across all 17 integrations that ship this cell. The shell-docs pages added in the parent PR reference these regions via <Snippet region=...>, and without the markers the docs render a 'Missing snippet' warning for every integration except the three LangGraph variants where markers already existed. Each marker nests around the equivalent code in that integration: - frontend region wraps imports + useFrontendTool / useInterrupt call in src/app/demos/gen-ui-interrupt/page.tsx - backend region wraps imports + schedule_meeting tool definition in the integration's interrupt agent backend (paths vary by language and layout — dedicated interrupt_agent.py, snippet.ts sibling file, InterruptAgentController.java, mastra agents/index.ts, etc.) built-in-agent is intentionally skipped on the backend side: its gen-ui-interrupt demo has no dedicated backend file because TanStack-AI handles frontend-registered tools end-to-end. Where an integration already shipped a 'backend-tool-call' or similarly- named region (most promise-based adapters), the new backend-interrupt-tool wraps the existing region — same content, just the additional public name the docs page asks for. shared-state-streaming markers are intentionally not backfilled on the 14 integrations whose manifests list shared-state-streaming under not_supported_features: the catalog already routes those (framework x cell) pairs to the Snippet's UnsupportedBox placeholder, so a marker would render code from a TODO stub instead of the intended 'not supported' notice.