Langgraph

davila7/claude-code-templates/cli-tool/components/skills/ai-research/langgraph

作者 davila78da17d671b6f无许可证32K 个星标收录于 2026年10月8日更新于 2026年10月8日仓库今天更新

Expert in LangGraph - the production-grade framework for building stateful, multi-actor AI applications. Covers graph construction, state management, cycles and branches, persistence with checkpointers, human-in-the-loop patterns, and the ReAct agent pattern. Used in production at LinkedIn, Uber, and 400+ companies. This is LangChain's recommended approach for building agents. Use when: langgraph, langchain agent, stateful agent, agent graph, react agent.

仅含说明AI & Agents
AI 生成的概览

指导使用 LangGraph 构建有状态、多角色的 AI 智能体,涵盖图结构、状态、持久化与 ReAct 模式。

功能
该技能为使用 LangGraph 框架构建 AI 智能体提供专家指导和代码模式。内容涵盖使用 StateGraph 构建图、状态管理与 reducer、节点与边定义、条件路由、检查点与持久化、人在回路模式、工具集成,以及流式与异步执行。它还列出常见反模式,如无限循环、无状态节点和臃肿的单一状态,并给出对应修正方法。
适用场景
适用于设计或实现有状态智能体工作流、LangChain 智能体、智能体图或 ReAct 风格智能体时。当需要条件分支、多个智能体共享状态,或需要持久化与可恢复对话时也很有用。
运行要求
Python 3.9+、langgraph 包、LLM API 访问(如 OpenAI、Anthropic),以及图结构概念的基础知识。该技能仅包含说明文档,不含脚本。

LangGraph

Role: LangGraph Agent Architect

You are an expert in building production-grade AI agents with LangGraph. You understand that agents need explicit structure - graphs make the flow visible and debuggable. You design state carefully, use reducers appropriately, and always consider persistence for production. You know when cycles are needed and how to prevent infinite loops.

Capabilities

  • Graph construction (StateGraph)
  • State management and reducers
  • Node and edge definitions
  • Conditional routing
  • Checkpointers and persistence
  • Human-in-the-loop patterns
  • Tool integration
  • Streaming and async execution

Requirements

  • Python 3.9+
  • langgraph package
  • LLM API access (OpenAI, Anthropic, etc.)
  • Understanding of graph concepts

Patterns

Basic Agent Graph

Simple ReAct-style agent with tools

When to use: Single agent with tool calling

python
from typing import Annotated, TypedDictfrom langgraph.graph import StateGraph, START, ENDfrom langgraph.graph.message import add_messagesfrom langgraph.prebuilt import ToolNodefrom langchain_openai import ChatOpenAIfrom langchain_core.tools import tool
# 1. Define Stateclass AgentState(TypedDict):    messages: Annotated[list, add_messages]    # add_messages reducer appends, doesn't overwrite
# 2. Define Tools@tooldef search(query: str) -> str:    """Search the web for information."""    # Implementation here    return f"Results for: {query}"
@tooldef calculator(expression: str) -> str:    """Evaluate a math expression."""    return str(eval(expression))
tools = [search, calculator]
# 3. Create LLM with toolsllm = ChatOpenAI(model="gpt-4o").bind_tools(tools)
# 4. Define Nodesdef agent(state: AgentState) -> dict:    """The agent node - calls LLM."""    response = llm.invoke(state["messages"])    return {"messages": [response]}
# Tool node handles tool executiontool_node = ToolNode(tools)
# 5. Define Routingdef should_continue(state: AgentState) -> str:    """Route based on whether tools were called."""    last_message = state["messages"][-1]    if last_message.tool_calls:        return "tools"    return END
# 6. Build Graphgraph = StateGraph(AgentState)
# Add nodesgraph.add_node("agent", agent)graph.add_node("tools", tool_node)
# Add edgesgraph.add_edge(START, "agent")graph.add_conditional_edges("agent", should_continue, ["tools", END])graph.add_edge("tools", "agent")  # Loop back
# Compileapp = graph.compile()
# 7. Runresult = app.invoke({    "messages": [("user", "What is 25 * 4?")]})

State with Reducers

Complex state management with custom reducers

When to use: Multiple agents updating shared state

python
from typing import Annotated, TypedDictfrom operator import addfrom langgraph.graph import StateGraph
# Custom reducer for merging dictionariesdef merge_dicts(left: dict, right: dict) -> dict:    return {**left, **right}
# State with multiple reducersclass ResearchState(TypedDict):    # Messages append (don't overwrite)    messages: Annotated[list, add_messages]
    # Research findings merge    findings: Annotated[dict, merge_dicts]
    # Sources accumulate    sources: Annotated[list[str], add]
    # Current step (overwrites - no reducer)    current_step: str
    # Error count (custom reducer)    errors: Annotated[int, lambda a, b: a + b]
# Nodes return partial state updatesdef researcher(state: ResearchState) -> dict:    # Only return fields being updated    return {        "findings": {"topic_a": "New finding"},        "sources": ["source1.com"],        "current_step": "researching"    }
def writer(state: ResearchState) -> dict:    # Access accumulated state    all_findings = state["findings"]    all_sources = state["sources"]
    return {        "messages": [("assistant", f"Report based on {len(all_sources)} sources")],        "current_step": "writing"    }
# Build graphgraph = StateGraph(ResearchState)graph.add_node("researcher", researcher)graph.add_node("writer", writer)# ... add edges

Conditional Branching

Route to different paths based on state

When to use: Multiple possible workflows

python
from langgraph.graph import StateGraph, START, END
class RouterState(TypedDict):    query: str    query_type: str    result: str
def classifier(state: RouterState) -> dict:    """Classify the query type."""    query = state["query"].lower()    if "code" in query or "program" in query:        return {"query_type": "coding"}    elif "search" in query or "find" in query:        return {"query_type": "search"}    else:        return {"query_type": "chat"}
def coding_agent(state: RouterState) -> dict:    return {"result": "Here's your code..."}
def search_agent(state: RouterState) -> dict:    return {"result": "Search results..."}
def chat_agent(state: RouterState) -> dict:    return {"result": "Let me help..."}
# Routing functiondef route_query(state: RouterState) -> str:    """Route to appropriate agent."""    query_type = state["query_type"]    return query_type  # Returns node name
# Build graphgraph = StateGraph(RouterState)
graph.add_node("classifier", classifier)graph.add_node("coding", coding_agent)graph.add_node("search", search_agent)graph.add_node("chat", chat_agent)
graph.add_edge(START, "classifier")
# Conditional edges from classifiergraph.add_conditional_edges(    "classifier",    route_query,    {        "coding": "coding",        "search": "search",        "chat": "chat"    })
# All agents lead to ENDgraph.add_edge("coding", END)graph.add_edge("search", END)graph.add_edge("chat", END)
app = graph.compile()

Anti-Patterns

❌ Infinite Loop Without Exit

Why bad: Agent loops forever. Burns tokens and costs. Eventually errors out.

Instead: Always have exit conditions:

  • Max iterations counter in state
  • Clear END conditions in routing
  • Timeout at application level

def should_continue(state): if state["iterations"] > 10: return END if state["task_complete"]: return END return "agent"

❌ Stateless Nodes

Why bad: Loses LangGraph's benefits. State not persisted. Can't resume conversations.

Instead: Always use state for data flow. Return state updates from nodes. Use reducers for accumulation. Let LangGraph manage state.

❌ Giant Monolithic State

Why bad: Hard to reason about. Unnecessary data in context. Serialization overhead.

Instead: Use input/output schemas for clean interfaces. Private state for internal data. Clear separation of concerns.

Limitations

  • Python-only (TypeScript in early stages)
  • Learning curve for graph concepts
  • State management complexity
  • Debugging can be challenging

Related Skills

Works well with: crewai, autonomous-agents, langfuse, structured-output

来源与署名

来源:davila7/claude-code-templates位于cli-tool/components/skills/ai-research/langgraph提交8da17d6

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架