# LangGraph

31 Hacker News commenters recommended LangGraph and 23 criticized it, November 2025 to November 2026. It was recommended in 12 of 13 months.

**Verdict:** Recommended for deterministic, stateful agent workflows with graph-based control, human-in-the-loop and time travel. Critics find it rigid and overly complex for simple tasks.

## Why people recommend it

- Deterministic, controllable agent workflows (5 comments): "As long as you keep the flow rigid and only use the LLM for orchestration and formatting, the hallucinations pretty much disappear." ([source](https://news.ycombinator.com/item?id=46727859)) "I've been using LangGraph to enforce structured outputs and run validation checks before any side effects happen." ([source](https://news.ycombinator.com/item?id=46763422)) "having that text state to pass into something like LangGraph is the only way to reliably control the logic" ([source](https://news.ycombinator.com/item?id=46744434))
- Graph and state machine model (4 comments): "We use LangGraph to implement the State Machine pattern rather than a linear Chain." ([source](https://news.ycombinator.com/item?id=46206488)) "the way to define the graph and transitions is pretty intuitive" ([source](https://news.ycombinator.com/item?id=46299429)) "it seems like the right abstraction to me" ([source](https://news.ycombinator.com/item?id=46239236))
- Reliable in production use (3 comments): "it seems to provide a lot of infrastructure for highly reliable and interactive agents" ([source](https://news.ycombinator.com/item?id=46238813)) "In our experience so far, it's been rock solid." ([source](https://news.ycombinator.com/item?id=49727066)) "I've not faced much issues!" ([source](https://news.ycombinator.com/item?id=46017055))

## What people warn about

- Adds complexity over plain Python (4 comments): "LangGraph wasting our time with what could've simply been an ordinary python function" ([source](https://news.ycombinator.com/item?id=47097223)) "LangGraph is unnecessary framework only slows you down by spiking up complexity." ([source](https://news.ycombinator.com/item?id=48634218)) "cobbled together mess using LangGraph and other overly complex libraries" ([source](https://news.ycombinator.com/item?id=49700472))
- Rigid, less flexible design (3 comments): "it's more opinionated , less flexible" ([source](https://news.ycombinator.com/item?id=45896194)) "they are inherently rigid" ([source](https://news.ycombinator.com/item?id=47102207)) "once the happy path breaks, the graph essentially halts or loops indefinitely because the error handling is too rigid" ([source](https://news.ycombinator.com/item?id=46984074))
- Time lost on state management (2 comments): "I've spent way more time lately fighting with Celery queues and LangGraph state management" ([source](https://news.ycombinator.com/item?id=46772509)) "Getting those agent systems to behave reliably was often annoying and tricky." ([source](https://news.ycombinator.com/item?id=48873363))

## Alternatives hackers recommend

- [Claude Agent SDK](https://hackerapproved.com/p/claude-agent-sdk.md): 36 recommend
- [LangChain](https://hackerapproved.com/p/langchain.md): 32 recommend
- [Mastra](https://hackerapproved.com/p/mastra.md): 32 recommend
- [DSPy](https://hackerapproved.com/p/dspy.md): 29 recommend
- [Pydantic AI](https://hackerapproved.com/p/pydantic-ai.md): 27 recommend

## Cite as

Hacker Approved, "LangGraph", https://hackerapproved.com/p/langgraph/ (counts from 1,795,640 Hacker News comments, November 2025 to November 2026).