Langchain is for model-agnostic composition. Claude Code only uses one interface to hoist its own models so zero need for an abstraction layer.

Langgraph is for multi-agent orchestration as state graphs. This isn't useful for Claude Code as there is no multi-agent chaining. It uses a single coordinator agent that spawns subagents on demand. Basically too dynamic to constrain to state graphs.

▲

simianwords 8 hours ago | parent [-]

You may have a point but to drive it further, can you give an example of a thing I can do with langgraph that I can't do with Claude Code?

▲

ossa-ma 8 hours ago | parent | next [-]

I'm not an supporter of blindly adopting the "langs" but langgraph is useful for deterministically reproducable orchestration. Let's say you have a particular data flow that takes an email sends it through an agent for keyword analysis the another agent for embedding then splits to two agents for sentiment analysis and translation - there is where you'd use langgraph in your service. Claude Code is a consumer tool, not production.

▲

simianwords 8 hours ago | parent [-]

I see what you mean. Maybe in the cases where the steps are deterministic, it might be worth moving the coordination at the code layer instead of AI layer.

What's the value add over doing it with just Python code? I mean you can represent any logic in terms of graphs and states..

	▲	chaos_emergent 4 hours ago \| parent [-]
		Most of the value I’ve gotten out of is has been observability. Graph and DAG workflow abstractions just help OTel structure your LLM logs in a clean hierarchy of spans. I could imagine figuring out a better solution to this than the whole graph abstraction. Other than that I’m not too sure.

▲

edgyquant 7 hours ago | parent | prev [-]

Use Gemini or codex models