Import LangGraph Threads

What is this?#

The LangGraph importer reads already-persisted LangGraph Server, LangGraph Platform, or LangSmith Deployment threads and writes them into Enterprise Intelligence as CopilotKit threads.

This works for LangGraph Python, LangGraph TypeScript, and LangGraph FastAPI when the source history is available through the LangGraph SDK thread and run APIs. It does not import classic LangChain message history stores, LangSmith traces, or embedded checkpointers that are not exposed through LangGraph Server / Platform.

Prerequisites#

• A CopilotKit app created with the CLI and Enterprise Intelligence enabled.
• A LangGraph Server, LangGraph Platform, or LangSmith Deployment URL.
• A LangGraph API key, LangSmith API key, or LangChain API key accepted by the LangGraph SDK.
• Source threads that belong to one graph_id per thread. Threads spanning multiple graph IDs are skipped instead of imported partially.

Select the target project#

The importer uses the Enterprise Intelligence project selected when you created the app with the CopilotKit CLI. If that is the project that should receive the LangGraph threads, continue to source configuration.

To target a different cloud-hosted project, select it before the dry run:

npx copilotkit@latest project select

The command updates the project selected for the current directory and provisions its project-scoped runtime key.

Configure the source#

Set the LangGraph deployment URL and API key in your shell. The importer reads source credentials from framework-native environment variables, not raw CLI flags.

export LANGGRAPH_API_URL="https://your-langgraph-deployment"
export LANGGRAPH_API_KEY="..."

LANGSMITH_API_KEY or LANGCHAIN_API_KEY can be used instead when that is how your deployment authenticates. If your LangGraph Cloud workspace requires a tenant header, set LANGGRAPH_TENANT_ID or LANGSMITH_TENANT_ID.

Run a dry run#

Start with a preview. This reads the source, discovers graph IDs, counts conversations, reports skips, and estimates upload size without writing to Enterprise Intelligence.

npx copilotkit@latest import --source langgraph --dry-run

Map graph IDs to CopilotKit agent IDs#

The source agent key for LangGraph is the thread's graph_id. Map each discovered graph ID to the agentId your live CopilotKit runtime uses.

{
  "support_graph": "support-agent",
  "research_graph": "research-agent"
}

Using the same agentId as live traffic keeps imported history and future conversations grouped together.

Import the threads#

Run the import after the dry run and agent mapping look right.

npx copilotkit@latest import \
  --source langgraph \
  --agent-map ./agent-map.json \
  --user-source configurable.user_id

Use --user-source to tell the importer where to find the end-user id for each thread. You can also pass a literal when every imported thread belongs to the same user:

npx copilotkit@latest import \
  --source langgraph \
  --agent-map ./agent-map.json \
  --user-source literal:imported-user

For self-hosted Enterprise Intelligence, pass the target connection explicitly:

npx copilotkit@latest import \
  --source langgraph \
  --api-url "$INTELLIGENCE_API_URL" \
  --api-key "$INTELLIGENCE_API_KEY" \
  --agent-map ./agent-map.json \
  --user-source configurable.user_id \
  --yes

Re-run or replace#

Re-running the same import is idempotent. Conversations already imported from the same source thread are skipped.

Use --replace to delete and re-import previously imported threads:

npx copilotkit@latest import \
  --source langgraph \
  --agent-map ./agent-map.json \
  --user-source configurable.user_id \
  --replace

Keep future LangGraph conversations synced#

Historical import does not keep polling LangGraph. Your CLI-created app already sends new CopilotKit conversations to the selected Enterprise Intelligence project. To keep each conversation continuous, reopen it with the same CopilotKit threadId using one of these UI paths:

• Threads Drawer: follow the Threads Drawer guide. The drawer and chat share a CopilotChatConfigurationProvider, so selecting a conversation updates the active threadId without separate state wiring.
• Headless Threads: follow the Headless Threads guide. Select a thread with useThreads, store its thread.id, and pass that value to your chat component as threadId.

If your backend maps CopilotKit thread IDs to LangGraph thread IDs, keep that mapping stable so a resumed CopilotKit thread reaches the expected LangGraph thread. LangGraph Platform thread IDs must be UUIDs, so persist a mapping instead of reusing the CopilotKit threadId when necessary.