Files
copilotkit__copilotkit/showcase/integrations/google-adk/qa/agent-config.md
Tyler Slaton ef1ca9808c feat(showcase/google-adk): QA-blitz parity ports — agent prompts, tool surface, e2e specs
Result of 10 parallel QA agents auditing all 30 active demos against
langgraph-python (north-star). Each agent ported drift back to LP-verbatim
across three axes:

1. Agent layer
   - tool_rendering_common.py: rebuilt to LP's surface — get_weather,
     search_flights(origin, destination), get_stock_price, roll_d20,
     roll_dice. Removed the ADK-only query_data.
   - tool_rendering_*_agent.py (4 variants): ported LP's travel/concierge
     prompt; reasoning-chain variant got LP's chain-two-tools prompt.
   - beautiful_chat_agent.py: ported LP's per-tool system prompt; added
     manage_sales_todos / get_sales_todos / generate_a2ui; dropped the
     redundant schedule_meeting (frontend HITL handles it).
   - open_gen_ui_agents.py: ported LP's full SYSTEM_PROMPT for both
     variants, including the Websandbox.connection.remote.* contract
     for the advanced sandbox demo (was `window.sandbox.*`, which the
     LP frontend's Websandbox bridge silently no-ops).
   - byoc_agents.py: fused LP's hashbrown + json-render prompts so the
     single ADK byoc_agent emits both wire shapes. Aliases exported for
     a future per-route split.
   - declarative_gen_ui_agent.py: ported LP's a2ui_dynamic SYSTEM_PROMPT.
   - a2ui_fixed_agent.py: picked up LP's #4734 regression guard
     ("exactly ONCE", "do NOT call again").
   - agent_config_agent.py: rewrote to read useAgentContext (was
     state["config"]); reconciled schema to LP's 3-field camelCase
     {tone, expertise, responseLength} with LP's value enums.
   - subagents_agent.py: dropped the "running" placeholder; returns
     plain str so the LP-verbatim frontend's `result?.trim()` works.
   - hitl_in_app_agent.py / hitl_in_chat_book_call_agent.py: prompts +
     tool-result shape ({approved, reason}) aligned to LP.
   - AGUIToolset() added wherever it was missing on the bespoke agents
     (multimodal, mcp_apps, a2ui_fixed) so frontend-registered tools
     reach the model.

2. Dedicated runtime routes
   - copilotkit-multimodal/route.ts (new) — mirrors LP shape with
     ADK's HttpAgent + AGENT_URL pattern.
   - copilotkit-agent-config/route.ts (new) — same pattern.
   - copilotkit-mcp-apps/route.ts — refreshed.

3. Frontend ports (ADK frontend brought to LP-verbatim where it had
   drifted from the parity blitz state)
   - tool-rendering family (4 demos): full re-port — WeatherCard,
     FlightListCard, StockCard, D20Card, ReasoningBlock, CatchallRenderer,
     suggestions, and the page wiring with all useRenderTool /
     useDefaultRenderTool / reasoningMessage registrations.
   - a2ui-fixed-schema, mcp-apps, multimodal: full frontend re-ports
     with their _components/ Tailwind primitives.
   - frontend-tools, frontend-tools-async, agent-config: ported LP's
     component structure (separate Background, NotesCard with query_notes,
     config-context-relay).
   - shared-state-read, shared-state-read-write, readonly-state-agent-context:
     ported LP's demo-layout + _components + suggestions. recipe-card.tsx
     pulled directly from LP (one QA agent had adapted to Unicode glyphs
     thinking ADK lacked lucide-react — it doesn't, after the parity blitz).
   - shared-state-streaming, subagents, hitl-in-app: ported LP's
     DocumentView / supervisor-activity / TicketsPanel structure.
     hitl-in-app/page.tsx pulled directly from LP to keep the hyphenated
     agent slug aligned with the renamed registry key.
   - auth, hitl-in-chat: ported LP's SignInCard-first auth UX and the
     time-picker Tailwind port.
   - prebuilt-popup: pulled LP's main-content + suggestions split.

4. Test fixtures
   - 30 tests/e2e/<slug>.spec.ts ported from LP, several overwriting
     stale stubs (shared-state-streaming, subagents, auth, hitl-in-chat,
     shared-state-read, agent-config).
   - 30 qa/<slug>.md ported from LP with ADK env-var and registry
     references substituted (GOOGLE_API_KEY, AGENT_URL, registry.py).
   - QA3's byoc-hashbrown / byoc-json-render specs renamed to
     declarative-hashbrown / declarative-json-render with internal
     URL references substituted (the orchestrator pass had already
     renamed the demo dirs + manifest entries).

Frontend changes from QA agents were filtered: kept where they ported
LP-verbatim into ADK, replaced with direct LP pulls where the agent
had made ADK-specific adaptations (one Unicode-glyph case, one
stale-registry-slug case).

Not touched per blitz rules: shared_chat.py, registry.py, manifest.yaml,
src/app/api/copilotkit/route.ts.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-12 17:58:06 -07:00

2.3 KiB

QA: Agent Config Object — Google ADK

Prerequisites

  • Demo deployed and accessible at /demos/agent-config
  • Railway service showcase-google-adk healthy
  • GOOGLE_API_KEY set on Railway

Test Steps

1. Initial state

  • Navigate to /demos/agent-config
  • Header "Agent Config Object" visible
  • agent-config-card is visible with the heading "Agent Config"
  • Tone dropdown (data-testid="agent-config-tone-select") shows "professional"
  • Expertise dropdown (data-testid="agent-config-expertise-select") shows "intermediate"
  • Response length dropdown (data-testid="agent-config-length-select") shows "concise"
  • <CopilotChat /> composer visible below the card

2. Default send

  • Type "Tell me about black holes" and send
  • Agent responds within 15 seconds
  • Response is brief (1-3 sentences), professional tone, no emoji (consistent with the default config)

3. Enthusiastic + detailed

  • Change Tone to "enthusiastic"
  • Change Response length to "detailed"
  • Verify both select values updated in the DOM
  • Send "Tell me about black holes" again
  • Response is noticeably longer (multiple paragraphs) and uses upbeat / energetic language
  • Compare to Step 2's response — the style difference is visible

4. Beginner expertise

  • Change Expertise to "beginner"
  • Send "What is quantum entanglement?"
  • Response defines jargon and uses analogies

5. Expert expertise

  • Change Expertise to "expert"
  • Send the same question
  • Response uses precise terminology, skips basics

6. Reactivity mid-thread

  • Without reloading the page, with previous replies visible, change Tone to "casual"
  • Send a follow-up
  • Reply reflects the casual tone; previous replies in the transcript remain unchanged

7. Error handling

  • Send an empty message; verify no-op or graceful empty-message handling
  • Verify no console errors during any of the above steps

Expected Results

  • Dropdown value changes appear in the DOM within 100ms of selection
  • Agent responses arrive within 15s per send
  • Visible style differences across tone / expertise / length changes (qualitative, but clear side-by-side)
  • Transcript preserves history when config changes mid-thread