r/LangGraph

I built a LangGraph boilerplate kit for building AI agents faster — would love feedback
▲ 4 r/LangGraph+1 crossposts

I built a LangGraph boilerplate kit for building AI agents faster — would love feedback

I’ve been working with LangGraph for building AI agents and noticed I kept repeating the same setup every time — state graph, memory, tool nodes, and streaming logic.

So I created a reusable boilerplate kit to speed this up.

GitHub: https://github.com/bhaskar511939/langgraph-boilerplate-kit

What it includes:

- Prebuilt LangGraph agent structure

- State management setup

- Streaming-ready execution flow

- FastAPI integration support

- Clean modular architecture for scaling agents

Why I built it:

To avoid rewriting the same LangGraph scaffolding and to make it easier to start production-grade agent systems quickly.

Would love feedback from people working with LangGraph:

- What’s missing?

- What would make this more useful in real production systems?

u/Mundane-Specific-721 — 5 days ago
▲ 8 r/LangGraph+4 crossposts

Need Help Choosing the Right AutoGen Teams Architecture

​

Hi everyone,

I'm currently working on a project where I need to migrate an existing multi-agent workflow to Microsoft AutoGen.

The current workflow is pretty simple:

- One node collects data from different sources.

- Multiple specialized node process that data in parallel (each has a different responsibility).

- A final validation node combines all the results and decides the final output based on some rules.

I first started using GraphFlow because it felt very similar to my existing graph-based workflow. However, my client wants the implementation to use AutoGen Teams instead.

I've gone through the documentation, but I'm still confused about which Team type is the best fit:

- Selector Group Chat

- Swarm

- Round Robin

- Or something else?

My goal is to keep the workflow efficient, allow parallel processing, and maintain the same quality of results.

If you've built projects using AutoGen Teams, I'd love to hear:

- Which Team would you choose for this kind of workflow?

- Any tips or common mistakes to avoid?

Thanks in advance for your help!

reddit.com
u/Ninjapakoda — 12 days ago
▲ 8 r/LangGraph+5 crossposts

Quick Survey: How Do You Build, Debug, and Reuse n8n Workflows?

Hi everyone,

My name is Zekun Wu, and I am a researcher at Saarland University, Germany.

I am currently conducting a short research survey on how people use workflow automation tools such as n8n. In particular, I’m interested in a simple but exciting idea: what if, after an AI helps complete a task, it could leave behind an editable workflow that users can inspect, fix, and reuse?

This survey helps us understand how real workflow users think about workflow understanding, debugging, and reuse in practice. It should only take about 5–10 minutes to complete.

Survey link:
https://forms.gle/uXmWdavWJuRqnFfr8

As a small thank-you, we will select up to 10 participants who provide especially thoughtful and relevant responses to receive a €10 Amazon eGift card. This is not based on whether your opinions are positive or negative — detailed and honest experiences are what we value most.

Your feedback would be very helpful for shaping our future research and prototype design. I would really appreciate it if you could take a few minutes to fill it out. Feel free to also share any thoughts or examples in the comments.

Thank you very much!

Best,
Zekun

u/Successful_Option561 — 13 days ago
▲ 4 r/LangGraph+1 crossposts

Drop self-correcting, prompt-optimizable nodes into your existing LangGraph without rewriting it (open source)

I kept writing the same defensive code around every LLM call. Parse the JSON, catch the field that didn't come back, re-prompt, cross my fingers. And every time I switched models, the prompt I'd spent an afternoon tuning would quietly break and I'd tune it again. dspyer is me getting tired of that.

Here's the idea. You wrap an LLM step in a Pydantic schema. When the model returns something that doesn't fit, malformed JSON, a missing field, a citation it made up, dspyer tells the model what was wrong and asks again until it conforms, or stops after however many retries you allow. It's one decorator on a normal typed function. No try/except, no glue code.

The part I actually care about is what that buys you. The step compiles down to a standard DSPy module, so instead of hand-editing prompts you point a DSPy optimizer at a few examples and let it tune them, then save the result and load it in production. That's the whole reason I went down this road. I wanted my prompts to stop being something I babysit.

It doesn't care which model you run. OpenAI, Claude, Gemini, or a local Ollama model with no API key at all. And if you're already on LangGraph, nothing gets rewritten. Your deterministic and tool nodes stay plain Python, only the reasoning nodes get wrapped.

There's a quickstart that runs in about 30 seconds offline, no key needed, if you just want to watch the self-correction loop fire. It's early, 0.3.5, Apache-2.0, on PyPI. I'd genuinely rather you tell me where it breaks than tell me it's neat. Here's the repo and docs

github.com
u/Traditional_Cut2853 — 12 days ago
▲ 4 r/LangGraph+1 crossposts

Subgraphs interruption handling

Hi guys im working on a production grade project where for each action of task i have created different subagents which all are routed based on identified intent in the main graph but each subagents have interruptions at diff levels and im also after every interruption again identifying is the user query aligned with the current intent or not

Have trouble with resume of multiple suagents and also my application is with fastapi and if I run it with multiple workers it is just breaking everything it's not able to resume properly getting same previous messages in loop.

Im using

Python

Langgraph

Aws bedrock for models

Valkey(redis memory store) for checkpointer storing with some tel

Any suggestions on this🙏🙏

reddit.com
u/Lowkey_Intro — 12 days ago