Live data from Hacker News

We chose LangGraph to build our coding agent

qodo.ai

21–23 of 23 posts

Re: We chose LangGraph to build our coding agent

#21

Earlier quoted context omitted.

I think the main thing LangGraph adds is a state machine framework for human in the loop with time travel. So if you have an authoring workflow where a doc goes through a bunch of steps, and at some steps the analyst might want to fix some LLM output manually, and try a couple of things and then go back to the way it was before and try again, it will do that and you won't have to make your own state machine.

Now is it actually a state machine or is it just well logged?

LangGraph implements a variant of the Pregel/BSP algorithm for orchestrating workflows with cycles (ie. not DAGs) and parallelism without data races. You can design your graph as a state machine if you so desire

Re: We chose LangGraph to build our coding agent

#22
post #6

I found that the PydanticAI [0] framework strikes a perfect balance between control and abstraction. I’m building a non trivial AI app and the validation and dependency injection is such a great addition compared to using the LLM libraries directly. [0] https://ai.pydantic.dev/

The one thing I wish was better developed is persistence and streaming - they give sample code to stream, but it’s essentially a complete implementation of streaming that every client needs to implement.

Re: We chose LangGraph to build our coding agent

#23
post #6

I found that the PydanticAI [0] framework strikes a perfect balance between control and abstraction. I’m building a non trivial AI app and the validation and dependency injection is such a great addition compared to using the LLM libraries directly. [0] https://ai.pydantic.dev/

Thanks, this looks great. I've been playing with Huggingface's Smolagents, which is fun to tinker with and relatively easy to read through. But it is so tightly coupled to its two agent implementations - ToolAgent and CodeAgent - that it's not trivial at all to add your own state transformations. This framework looks really well designed, I'm going to take it for a spin.

The main problem that I found playing with smolagents is the lack of documentation and examples. Anyway the framework has potential
Post reply on HN