Files
Alem Tuzlak 23a3b24a01 feat(showcase/integrations): shared-state-read-write + subagents demos across 15 packages
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
2026-04-28 18:36:13 +02:00

3.6 KiB

QA: Sub-Agents — PydanticAI

Prerequisites

  • Demo is deployed and accessible at /demos/subagents on the dashboard host
  • Agent backend is healthy (/api/health); OPENAI_API_KEY is set; the PydanticAI agent server is reachable on the configured AGENT_URL and the /subagents sub-path is mounted (supervisor + 3 sub-agents)

Test Steps

1. Basic Functionality

  • Navigate to /demos/subagents; verify the page renders within 3s with a left-side delegation log panel and a right-side CopilotChat pane
  • Verify data-testid="delegation-log" is visible with heading "Sub-agent delegations"
  • Verify data-testid="delegation-count" reads 0 calls initially
  • Verify the empty state message "Ask the supervisor to complete a task. Every sub-agent it calls will appear here." is visible
  • Verify the chat input placeholder is "Give the supervisor a task..."
  • Verify all 3 suggestion pills are visible: "Write a blog post", "Explain a topic", "Summarize a topic"
  • Send "Hello, what can you do?" and verify an assistant text response within 10s

2. Feature-Specific Checks

Supervisor Delegates to Sub-Agents

  • Click the "Write a blog post" suggestion (the supervisor should delegate to research → writing → critique)
  • Within 5s of the run starting, verify data-testid="supervisor-running" appears next to the heading
  • Verify a data-testid="delegation-entry" for Research appears with the running task visible, then transitions from running to completed with a bulleted list of facts
  • Verify a Writing entry appears next, transitioning from running to completed with a polished paragraph in the result
  • Verify a Critique entry appears last, transitioning from running to completed with 2-3 actionable critiques
  • Verify data-testid="delegation-count" reads 3 calls after the full sequence completes
  • Verify each entry's badge shows the correct sub-agent label and emoji (Research 🔎, Writing ✍️, Critique 🧐)

Live Updates

  • While a delegation is in flight, verify the entry is visible with status running and the placeholder copy "Sub-agent is working..."
  • Verify entries are appended in order (#1, #2, #3) as the supervisor calls each sub-agent

Multi-Turn Accumulation

  • After the first task completes, send "Do another one — same topic but with a marketing angle."
  • Verify new delegation entries are appended below the existing ones (the log grows; previous entries are preserved) and delegation-count increases accordingly

Supervisor-Running Indicator

  • While the supervisor is producing its final summary, verify the running pill is still visible
  • Verify it disappears once the supervisor finishes its turn

3. Error Handling

  • Attempt to send an empty message; verify it is a no-op
  • If a sub-agent fails (e.g. transient OpenAI error), verify the corresponding delegation entry shows status failed with the failure message in the result body, and the supervisor surfaces the failure to the user (no fabricated success)
  • Verify DevTools -> Console shows no uncaught errors during any flow above

Expected Results

  • Page loads within 3 seconds
  • First delegation entry appears within 5 seconds of submitting a multi-step task
  • Each sub-agent completes within 30 seconds for short tasks
  • The full research → write → critique chain runs and the log shows 3 entries, all completed
  • Failed sub-agents render as failed (red) with a server-safe message; the supervisor does not pretend the work succeeded
  • No UI layout breaks, no uncaught console errors