Migrate from LangChain and LangGraph to Guild

LangChain and LangGraph are open-source agent libraries. LangSmith is LangChain’s commercial platform for tracing, evals, deployment, and Fleet, its no-code agent builder. Guild runs LangGraph v1 graphs natively: a Python LangGraph agent keeps its graph and swaps in Guild’s model and tools. JavaScript createAgent agents move to Guild TypeScript, and Fleet agents move to Guild Native.

Who this is for

Teams with LangGraph agents on LangSmith Deployment or their own servers, createAgent agents in Node services, or Fleet agents, who want them on a shared Hub. On Guild, credentials stay behind a proxy and every run shows in one workspace.

Concept map

Guild	LangChain / LangGraph / LangSmith
LangGraph agent with `guild_model()`	`create_agent` (Python)
TypeScript `llmAgent`	`createAgent` (JS)
LangGraph agent unchanged, or TypeScript `agent` control flow	`StateGraph` nodes and edges
`guild_model()` or `guild.yaml` `models`	Model string (`anthropic:…`)
Integrations declared in `guild.yaml`, loaded with `guild_tools()`	`@tool` functions, MCP tools (`langchain-mcp-adapters` or `langchain.mcp`)
A credential policy scoped to the agent (who can call it), plus a `ui_prompt` confirmation (sign-off on each call)	`humanInTheLoopMiddleware`, `interrupt()`
Guild session state	Checkpointer, thread state
Credentials	`langgraph.json` `env`
Session event log and Insights	LangSmith tracing
Guild Evaluations and `guild agent test`	LangSmith datasets and evaluators
Schedule trigger	Deployment cron jobs
API trigger	Agent Server API (`runs` endpoints)
Native agent (`PROMPT.md` + `guild.yaml`)	Fleet agent
Event triggers on those integrations	Fleet Slack, Teams, Gmail, and Outlook triggers
Schedule trigger	Fleet schedules
`guild agent save --wait --publish`	`langgraph deploy`

Before you start

guild auth login
guild workspace select

Upgrade to LangChain and LangGraph v1 first. AgentExecutor moved to langchain-classic in v1, which Guild’s LangGraph runtime doesn’t include. create_react_agent is deprecated in v1, so replace it with create_agent from langchain.agents.

Inventory

Graph entry points in langgraph.json and every node.
Every tool and MCP server (MultiServerMCPClient, or MCPAdapter from langchain.mcp), and the service it reaches.
Python dependencies beyond langchain, langchain-core, langchain-openai, and langgraph.
Interrupt or human-in-the-loop points.
Cron jobs, webhooks, and, for Fleet, triggers and connection identities (“Claws” use fixed credentials; “Assistants” and per-user connections act as the invoker).
Environment variables, by name only.

Steps

Python LangGraph
JS createAgent
LangSmith Fleet

Scaffold a LangGraph agent

guild agent init --name issue-triage --agent-type LANGGRAPH \
  --category <category> --owner <owner>

--category and --owner stop the CLI from prompting, which a script or coding agent can’t answer. List categories with guild agent categories.The scaffold contains langgraph.json, graph.py, guild.yaml, README.md, and .gitignore.

Swap model and tools

from guildai_langchain import guild_model, guild_tools
from langchain.agents import create_agent

async def graph():
    return create_agent(guild_model(), await guild_tools(), system_prompt="Triage new GitHub issues.")

from langchain.agents import create_agent
from langchain_anthropic import ChatAnthropic
from langchain_mcp_adapters.client import MultiServerMCPClient

client = MultiServerMCPClient({"github": {"url": "https://mcp.example.com/github", "transport": "streamable_http"}})

async def graph():
    tools = await client.get_tools()
    return create_agent(ChatAnthropic(model="claude-sonnet-5-5"), tools, system_prompt="Triage new GitHub issues.")

guild_tools() is async, so the graph target must be an async factory.

Declare tools in guild.yaml

integrations:
  - name: guildai~github
    version: ^1.0.0
    tools: [github_issues_list_for_repo, github_issues_update]

Keep langgraph.json targets as relative file paths: { "dependencies": ["."], "graphs": { "agent": "./graph.py:graph" } }.

Test

git add -A
guild agent test

guild agent test uploads only the files git tracks, so git add -A stages new files such as logic.ts first. Without it, the cloud build fails with “Cannot find module ’./logic.ts’”.

Scaffold a TypeScript agent

guild agent init --name support-agent --agent-type GUILD_TYPESCRIPT --template LLM \
  --category <category> --owner <owner>

--category and --owner stop the CLI from prompting, which a script or coding agent can’t answer. List categories with guild agent categories.

Port the agent

"use agent";
import { llmAgent, pick, userInterfaceTools } from "@guildai/agents-sdk";
import { ZendeskTools } from "@guildai-services/<owner>~zendesk";

export default llmAgent({
  description: "Answers support questions and opens a ticket, after confirmation, when it cannot.",
  tools: {
    ...pick(ZendeskTools, ["zendesk_search", "zendesk_tickets_create"]),
    ...pick(userInterfaceTools, ["ui_prompt"]),
  },
  systemPrompt: "Answer support questions. Before creating a ticket, ask the user to confirm with ui_prompt.",
  mode: "multi-turn",
});

import { createAgent, humanInTheLoopMiddleware } from "langchain";

const agent = createAgent({
  model: "anthropic:claude-sonnet-5-5",
  tools: [searchDocs, createTicket],
  systemPrompt: "Answer support questions; open a ticket when you cannot.",
  middleware: [humanInTheLoopMiddleware({ interruptOn: { create_ticket: true } })],
});

Use agent({ ..., run }) instead when the graph has deterministic branches. Nodes become functions, and parallel branches become an inline task.gather([...]).The ui_prompt confirmation replaces interruptOn as the sign-off on each call. To control which agents can call the operation at all, add a credential policy rule scoped to the agent and workspace. DENY wins.

Test

pnpm install && pnpm test
git add -A
guild agent test

The scaffold has no test script, so pnpm test passes without running anything. Add a test script to package.json before you rely on it, such as "test": "tsc --build && node --test logic.test.mjs". If pnpm install fails with ERR_PNPM_IGNORED_BUILDS, newer pnpm is blocking esbuild’s install script. Run pnpm approve-builds, approve esbuild, and install again.guild agent test uploads only the files git tracks, so git add -A stages new files such as logic.ts first. Without it, the cloud build fails with “Cannot find module ’./logic.ts’”.

Scaffold a Native agent

guild agent init --name inbox-assistant --agent-type GUILD_NATIVE \
  --category <category> --owner <owner>

--category and --owner stop the CLI from prompting, which a script or coding agent can’t answer. List categories with guild agent categories.

Move instructions and connections

Copy the Fleet instructions into PROMPT.md. List each connection’s tools under integrations in guild.yaml, and add builtins: [{ name: ui, tools: [ui_prompt] }] for any tool set to “Ask”. Tell the agent in PROMPT.md to confirm with ui_prompt before it calls those tools. To control which agents can call a tool at all, add a credential policy rule scoped to the agent and workspace.

Test

git add -A
guild agent test

guild agent test uploads only the files git tracks, so git add -A stages new files such as logic.ts first. Without it, the cloud build fails with “Cannot find module ’./logic.ts’”.

Then publish and wire triggers:

guild agent save --message "Port from LangGraph" --wait --publish
guild workspace agent add <owner~agent> --workspace <owner~workspace>
guild trigger create --workspace <owner~workspace> --type webhook --agent <owner~agent> \
  --integration github --event issues --action opened \
  --input '{"type":"text","text":"Triage this issue: {webhook_payload}"}'

The first guild agent save --wait --publish after guild agent init fails with “No saved state… use —force” because of the .gitignore the scaffold writes. Add --force to that first save for now.

You can also publish with the Publish Agent to Guild GitHub Action instead of guild agent save --publish. The Action needs an account API key with the agents:write scope:

guild api-key create --owner <owner> --name "Publish migrated agent" --scopes agents:write

Credentials and policies

Remove provider API keys and LangSmith keys; Guild routes model calls through its own proxy. Recreate service tokens as credentials. Fleet “Claws” map to workspace- or agent-scoped credentials, and “Assistants” and per-user connections map to member-scoped credentials. Restrict operations with credential policies.

What doesn’t map 1:1

Extra Python packages

Guild’s LangGraph runtime provides Python 3.13 with langchain, langchain-core, langchain-openai, langgraph, and guildai_langchain only. A graph that needs other packages (vector store clients, requests, provider SDKs) must replace them with Guild integrations or move to TypeScript.

Network access

The container has no general network access. Every outside call must go through a Guild tool.

Long turns

A LangGraph turn fails after 10 minutes without events. The clock pauses during Guild tool calls.

Approval lists

interruptOn and Fleet’s per-tool “Ask” map to two Guild controls. To control which agents can call the operation at all, add a credential policy rule scoped to the agent and workspace that allows or denies that operation. DENY wins. To have a person sign off on each call, have the agent confirm with ui_prompt first. The run pauses until someone answers.

Run webhooks

LangSmith Deployment webhooks send a POST callback to your service when a run finishes. They notify, they don’t start runs, so they have no Guild trigger equivalent. To notify a service when a Guild run ends, have the agent call it through an integration as its last step.

Self-hosting and hybrid

LangSmith Deployment offers hybrid and self-hosted options. Guild is hosted only.

Evaluations

LangSmith datasets, evaluators, and Engine have no 1:1 equivalent. Port your key cases to Guild Evaluations.

Three ways to migrate

guild-migrate skill

Ask your coding agent: “Migrate this LangGraph project to Guild.” It picks the LangGraph or TypeScript path and writes MIGRATION.md.

Publish Agent to Guild Action

Commit the port to your repository, then publish it from GitHub Actions with an account API key.

Migration agent

Point Migrate to Guild at your repository; it opens a draft pull request. The guild-migrate skill ships in the same package.

A worked before/after example lives in examples/migrations/langchain/ in the guild-migrate repository.

LangGraph agents

The runtime, guild_model(), guild_tools(), and constraints.

guild.yaml

Models, integrations, sub-agents, and builtins.

Overview

The Smith

The Factory

Platform

Agent SDK

Migrations

Migrate from LangChain and LangGraph to Guild

Who this is for

Concept map

Before you start

Inventory

Steps

Credentials and policies

What doesn’t map 1:1

Three ways to migrate

guild-migrate skill

Publish Agent to Guild Action

Migration agent

LangGraph agents

guild.yaml

​Who this is for

​Concept map

​Before you start

​Inventory

​Steps

​Credentials and policies

​What doesn’t map 1:1

​Three ways to migrate

guild-migrate skill

Publish Agent to Guild Action

Migration agent

​Related pages

LangGraph agents

guild.yaml

Who this is for

Concept map

Before you start

Inventory

Steps

Credentials and policies

What doesn’t map 1:1

Three ways to migrate

Related pages