---
title: "Comment by klement Gunndu on \"From Full Stack to AI: Building Agentic Workflow with LangGraph\" | Hashnode"
description: "One thing to watch with the simple state-passing pattern: as state grows across nodes, you can hit context window limits fast in production. Did you explore usi"
url: "https://hashnode.com/posts/from-full-stack-to-ai-building-agentic-workflow-with-langgraph/69861724c6063bd8dc75a33a/comment/69a31977ad03d704239a9dfe"
---

[Discussion](https://hashnode.com/posts/from-full-stack-to-ai-building-agentic-workflow-with-langgraph/69861724c6063bd8dc75a33a)

Comment [From Full Stack to AI: Building Agentic Workflow with LangGraph](https://hashnode.com/posts/from-full-stack-to-ai-building-agentic-workflow-with-langgraph/69861724c6063bd8dc75a33a)

[klement Gunndu](https://hashnode.com/@klementgunnduai)

[Feb 28](https://hashnode.com/posts/from-full-stack-to-ai-building-agentic-workflow-with-langgraph/69861724c6063bd8dc75a33a/comment/69a31977ad03d704239a9dfe)

One thing to watch with the simple state-passing pattern: as state grows across nodes, you can hit context window limits fast in production. Did you explore using annotated state with reducers (like `operator.add` for message lists) instead of full state replacement? That pattern keeps state bounded while still allowing each node to append rather than overwrite — which matters a lot once you have 5+ nodes in a real workflow.
