mirror of
https://github.com/CopilotKit/CopilotKit.git
synced 2026-09-14 16:26:20 +08:00
23a3b24a01
Adds real working Shared State (Read+Write) and Sub-Agents demos to 15 showcase integrations, mirroring the canonical langgraph-python and google-adk reference implementations. Fills rows previously empty on the showcase coverage dashboard. Packages: ag2, agno, claude-sdk-python, claude-sdk-typescript, crewai-crews, langgraph-fastapi, langgraph-typescript, langroid, llamaindex, mastra, ms-agent-dotnet, ms-agent-python, pydantic-ai, spring-ai, strands. (built-in-agent landed independently on main as PR #4321 — its variant is canonical; this PR no longer touches it.) Per-package deliverables: framework-native backend agents (preferences-injection middleware/callback + set_notes tool; supervisor + 3 sub-agents wired as tools with running -> completed /failed delegation log); frontend page.tsx + preferences-card.tsx / notes-card.tsx for SSRW and delegation-log.tsx for subagents — wired to useAgent({ updates: [OnStateChanged] }); manifest entries; runtime route registration + per-package agent server config; real QA scripts. Includes targeted hardening fixes from a 7-agent code-review loop: - Sub-agent failure paths now correctly emit status: "failed" (previously hardcoded "completed" or unreachable in mastra/strands/langgraph-fastapi/langgraph-typescript/ag2) - Parallel-tool-call delegation race fixed in langgraph-fastapi (Annotated[list, add]) and langgraph-typescript (concat reducer) - Silent data loss eliminated in claude-sdk-python/claude-sdk-typescript/crewai-crews — empty JSON.parse catches now log + emit error events - ms-agent-dotnet set_notes writes to per-thread slot via AsyncLocal - mastra working-memory writes are deterministic via src/mastra/tools/working-memory.ts helper - spring-ai tool-call envelope ids match supervisor's tc.id() and AG-UI event ordering reordered; CopyOnWriteArrayList for parallel-call safety - Stack trace + raw error message leaks scrubbed across 8+ Next.js routes — log server-side with errorId + return generic envelope - Sub-agent calls no longer block event loops in ag2 (asyncio.to_thread), langroid (llm_response_async), pydantic-ai (async run + async tools) - langroid lru_cache cross-request contamination dropped - Numerous smaller items: claude-sdk-python invalid model id, Callable annotation, /health endpoint exposed; crewai-crews supervisor no longer resets delegations every turn; pydantic-ai snapshot uses model_dump() CI fixes folded in: - crewai-crews test_forwarded_props: extend the stubbed ag_ui_crewai.endpoint module to expose add_crewai_flow_fastapi_endpoint and add stub agents.shared_state_read_write / agents.subagents modules - generate-catalog test: bump crewai-crews wired-cell expectation 28 -> 30; replace hardcoded total-wired count with an invariant (wired + stub + unshipped = 737) plus a lower-bound floor - oxfmt run on the qa/shared-state-read-write.md files in mastra + spring-ai Rebased onto latest main (post showcase/packages -> showcase/integrations rename + post built-in-agent landing). Original blitz history preserved at the blitz-pre-rebase-snapshot tag. Known follow-ups (deferred to follow-up PR): - agno sync sub_agent.run() blocks event loop (perf only) - ms-agent-python asyncio thread-fallback fragility - llamaindex initial-state coercion when UI clears state - Manifest highlight audit (langgraph-typescript headless-complete, langgraph-fastapi byoc-* missing route.ts highlights) - agno hitl-in-chat declared in demos but not features; duplicate /demos/hitl-in-chat route - langgraph-typescript server.mjs graphSpec only registers 3 graphs vs 23 in langgraph.json (pre-existing) - mastra hitl legacy demo missing from features list - claude-sdk-python agents/agent.py line 474 also has the legacy claude-opus-4-5 default - PARITY_NOTES vs manifest mismatches for hitl-in-app across spring-ai/agno/ag2 (pre-existing) - spring-ai a2ui-fixed-schema missing from generative_ui list
3.7 KiB
3.7 KiB
QA: Sub-Agents — LlamaIndex
Prerequisites
- Demo is deployed and accessible at
/demos/subagentson the dashboard host - Agent backend is healthy (
/api/health);OPENAI_API_KEYis set; LlamaIndex agent_server has thesubagents_routermounted at/subagents
Test Steps
1. Basic Functionality
- Navigate to
/demos/subagents; verify the page renders within 3s with a left-side delegation log and a right-sideCopilotChatpane - Verify
data-testid="delegation-log"is visible with heading "Sub-agent delegations" - Verify
data-testid="delegation-count"shows "0 calls" before any interaction - Verify the empty-state copy reads "Ask the supervisor to complete a task. Every sub-agent it calls will appear here."
- Verify the chat input placeholder is "Give the supervisor a task..."
- Verify all 3 suggestion pills are visible with verbatim titles: "Write a blog post", "Explain a topic", "Summarize a topic"
2. Feature-Specific Checks
Multi-Step Delegation (research -> writing -> critique)
- Click the "Write a blog post" suggestion; verify the supervisor running indicator (
data-testid="supervisor-running") appears within 2s and shows "Supervisor running" - Within 60s, verify three
data-testid="delegation-entry"rows appear in order withdata-status="completed"and these badges (in order):- Research (blue badge)
- Writing (emerald badge)
- Critique (purple badge)
- Verify
data-testid="delegation-count"reads "3 calls" - Verify each entry shows a "Task:" line and an output box; the research output is a bulleted list of facts, the writing output is a paragraph, and the critique output is 2-3 bullet critiques
- Verify the supervisor's final chat message in the right-side pane summarizes the result (1-3 sentences)
- After the run completes verify the running indicator is hidden
Live "running" State
- Send "Write a short blog post about AI agents. Research first, then write."; while the supervisor is in flight, verify at least one entry briefly shows
data-status="running"with the spinner and "Sub-agent is working…" copy before flipping tocompleted
Status Coloring & Ordering
- Click the "Explain a topic" suggestion; verify entries appear top-down in invocation order (research first, writing second, critique last)
- Verify
runningentries use amber styling,completedentries use neutral styling, and anyfailedentries use red styling
Multi-Turn Accumulation
- After one full delegation run, send "Now do the same for cold plunges"; verify the delegation log grows (previous entries preserved, 3 new entries appended) and
delegation-countreads "6 calls" - Reload the page; verify the delegation log resets to empty (state is per-session)
3. Error Handling
- Send an empty message; verify it is a no-op (no user bubble, no assistant response, no new delegation entries)
- If a sub-agent invocation fails (e.g. transient OpenAI 5xx), verify the corresponding entry shows
data-status="failed"with red styling and a[sub-agent failed]message; verify the supervisor's chat reply briefly surfaces the failure rather than fabricating a result - Verify DevTools -> Console shows no uncaught errors during any flow above
Expected Results
- Page loads within 3 seconds
- A typical research/write/critique sequence completes within 60 seconds
- The delegation log updates live as each sub-agent finalizes (entries flip from running to completed/failed)
- The supervisor running indicator reflects
agent.isRunning - Delegation entries persist across multi-turn runs within a session and reset on reload
- No UI layout breaks, no uncaught console errors