We're working towards LangGraph v1, and we're looking for input from our user base — you!
This is your chance to help shape the core of LangGraph — especially the low-level StateGraph API and related tooling. What we want to hear from you about:
- What parts of LangGraph are confusing or unclear?
- What feels unnecessarily complex or boilerplate-heavy?
- What's annoying or unintuitive when using StateGraph?
- What's missing / what features should be top prio?
We'll use this feedback to prioritize changes for v1, including API cleanup, improved documentation, and new features.
Note: We're prioritizing backward compatibility for users and don't plan to make any major breaking changes that make upgrading from v0 to v1 difficult.
Thanks in advance!
[UPDATE]: we'd love feedback on #5023 specifically as well!!
— LangGraph team
Tracking progress on v1 here: LangGraph v1 sprint (view)
.png)


![Educating the Next Generation of Open Source Project Contributors [video]](https://www.youtube.com/img/desktop/supported_browsers/chrome.png)