LangGraph - Persistence & Human-in-the-Loop Workflow

[@bsarel]

Hands down the best simplified flow engineering channel out there ❤

[@codingcrashcourses8533]

thank you! ;-)

[@SavvasMohito]

Thank you so much, your LangGraph videos are very helpful!

[@say.xy_]

Great content as always 🦾

[@codingcrashcourses8533]

Thank you :)

[@b18181]

Yet another great video… agree that this is one of the best channels by far. Thanks for sharing your knowledge! Do you ever do contract work?

[@codingcrashcourses8533]

Thank you man! But no - I don´t do contract work

[@b18181]

@@codingcrashcourses8533 - thanks for letting me know! In addition to your LangChain courses, will you be releasing a LangGraph course on Udemy as well? Thanks again!

[@codingcrashcourses8533]

@@b18181 Probably yes, but I will first update my other two courses. Maybe in september if I find enough time

[@lbasavaraj]

Good one again, looking forward for the Postgres checkpointing

[@codingcrashcourses8533]

will be released on wednesday :)

[@doe-v4y]

Great Video! I want to ask your opinion on the ROI for building out Agentic systems using Langgraph. Many of these frameworks roll out updates regularly. An issue most people dealt with when using Langchain was that as the system got more complex, they figured out that building it from scratch was a lot easier. My project started out similarly and we have now built out the initial PoC with just python and the simpler Langchain abstractions. Now we are looking to build out this HITL functionality but it comes at the cost of migrating to Langgraph. I'm trying to figure out if the migration is worth it or if we should build our own state machine framework. I understand that providing insights without details about the use case might be challenging, but I'm open to any insights you may have on this.

[@codingcrashcourses8533]

LangChain is great and easy to use. I want to see these guy´s codebase. I would bet 100$ that it is spaghetti code.

[@doe-v4y]

@@codingcrashcourses8533 XD Fair enough. Thanks for the feedback

[@ramishelh9998]

Best of the best. Thanks a lot! super helpful and clear.

[@Lirim_K]

So if one was to deploy a chatbot on a website, how should one handle the thread IDs? Obviously each new customer should have a fresh ID when they start, and after the chat completes and the user closes the dialogbox, that ID should be flushed and available for a new customer?

[@codingcrashcourses8533]

I would just use UUIDs, ensure they are unique and not really care about other users being able to reuse an id. I would create an endpoint (open chat interface) which creates a thread ID and on close I would do nothing at all. Just keep the history for 6 weeks or so.