Files
Benjamin Taylor b13fa63cb5 docs(examples): call them Channels, not managed Channels
The starter READMEs, channel-host.mts headers, and the host's own log
lines described the feature as a "managed Channel". Managed is an
implementation detail of how Intelligence attaches the provider edge,
not part of the name — the product surface is just a Channel.

Renames every occurrence across the 15 starters. Section headings become
"Running a Channel", the host header becomes "Channel host", and the
setup_required log reads "no provider is attached yet".

"managed Intelligence" in the .env.example comments is left alone: that
one distinguishes hosted Intelligence from a self-hosted deployment and
is unrelated to Channel naming.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-02 12:17:13 -05:00

21 lines
713 B
TypeScript

import { LangGraphAgent } from "@copilotkit/runtime/langgraph";
/**
* Builds this starter's agent.
*
* Extracted from the runtime route so both mounts share one definition: the
* route serves the web app over HTTP, and `channel-host.mts` serves a Channel.
* A fresh instance per call — the channel host sets `threadId` per
* conversation, so a shared instance would leak state across threads.
*/
export function createDefaultAgent(): LangGraphAgent {
return new LangGraphAgent({
deploymentUrl:
process.env.AGENT_URL ||
process.env.LANGGRAPH_DEPLOYMENT_URL ||
"http://localhost:8123",
graphId: "sample_agent",
langsmithApiKey: process.env.LANGSMITH_API_KEY || "",
});
}