mirror of
https://github.com/CopilotKit/CopilotKit.git
synced 2026-09-14 16:26:20 +08:00
Jordan Ritter
1900bace89
Re-applies the starter @chat usability fix that was collaterally reverted.
PR #5210 standardized starter agent registry keys to "default", and PR #5151
(ENT-679) had added useSingleEndpoint={false} to the starter <CopilotKit>
layouts. Together those two halves fixed the "@chat: No assistant response"
blocker: without them the client auto-detects single-endpoint transport and
POSTs to a route that 404s instead of the per-agent endpoint keyed "default".
The ENT-679 revert (#5217, commit 3721e7b36) backed out BOTH halves as
collateral, so starters on main are broken again (adk key my_agent, agno
agno_agent, etc., and no useSingleEndpoint={false}).
This re-applies ONLY the usability fix, fully decoupled from the Intelligence
threads feature. No threads-drawer, no _intelligence overlay, no
CopilotKitIntelligence runtime block, no ghcr composite images.
Per affected starter:
- route.ts (or mastra/index.ts): agents registry key -> default
- layout.tsx: add useSingleEndpoint={false}, drop agent= prop (falls back to default)
- page.tsx: useAgent name/agentId literal -> "default"
Affected starters: adk, agno, crewai-crews, llamaindex,
ms-agent-framework-dotnet, ms-agent-framework-python, pydantic-ai, mastra.
Agent semantic names/exports (e.g. mastra weatherAgent) are unchanged; only
the registry KEY and frontend agentId become "default".
Real verification is the smoke-starter @chat matrix legs in CI.