krawczstef

FYI - Burr is designed with recursion in mind, i.e. the ability to kick off Burr within Burr. So you could have an action that is managing several Burr subgraphs... Or you write your own management layer here.

yep - here's something cool an end user wrote with Burr - https://github.com/msradam/phoebe

Burr just helps you, the engineer, to really control the primitives. Then adds some cool features you don't have to think about -- like observability :)

no. more lower level.

user contributed :)

Cause I submitted it. Learning the Apache process and cranking on other things has been a slow process. But we've got some momentum and beginning more regular releases.

I agree with this post.

Otherwise the larger picture is that MCP is a land grab for building an eco-system around integrations to get access to data. Your LLM agent is not valuable if it can't access things for you... and from a market perspective enterprise pays a lot for this stuff already, and yes MCP is not thought out at all for Enterprise really... At least thankfully they added stateless connections to the spec...

Unfortunately their blog doesn't have the example they have on x.com - https://x.com/ZyphraAI/status/1888996367923888341 - which I think is more illustrative.

your comment made me think I read it wrong, but it's not closed source, they're just moving to a source available license...

yep, agreed. I think that's another way to view the current state of "GenAI" tooling (e.g. all those complicated frameworks that received $M in funding) and why things like https://www.anthropic.com/research/building-effective-agents fall on deaf ears...

+1 for vanilla code without LangChain.

Interesting! I feel like this is a cross between https://github.com/dagworks-inc/burr (switch state for context) and https://github.com/Netflix/metaflow because the output of the "task" declares its next hop...

The challenge with this approach though is that you need to run the actual code to see what it does, or as a developer build up a mental model of the code ... but it does shine in certain use cases -- and also reminds me of https://github.com/insitro/redun because it takes this approach too.

This is reminiscent of themes brought up in https://news.ycombinator.com/item?id=42253735 and most famously in https://news.ycombinator.com/item?id=36645575...

Forgot to mention, on the roadmap we have pluggable executors, e.g. delegating parallelism to whole agents/subgraphs to systems like "ray". Would love to collaborate with folks if that's interesting.

Looks great. But being burned by other "abstractions", e.g. LangChain, I'm weary of the oversimplification. How are you not going to make those same mistakes?

Does this compete with Minio?

@staranjeet we should get you plugged in as part of persistence with https://github.com/dagworks-inc/burr !

Yep. When I was designing https://github.com/dagworks-inc/hamilton part of the idea was to make it easy to understand what and where. That is, enable one to grep for function definitions and their downstream use easily, and where people can't screw this up. You'd be surprised how easy it is to make a code base where grep doesn't help you all that much (at least in the python data transform world) ...

Wow. Implemented pregel to run a 3 node graph... Jokes aside, that's an interesting thesis to have in there...

Really? Can you point to code for that? To me it's just a way to describe a graph and execute it, exactly like https://github.com/dagworks-inc/burr (I'm an author).

Here's a blog post that I just pushed that doesn't use them at all - https://blog.dagworks.io/p/building-a-conversational-graphdb (we have more on our blog - search for RAG).

[disclaimer I created Hamilton & Burr - both whitebox frameworks] See https://www.reddit.com/r/LocalLLaMA/comments/1d4p1t6/comment... for comment about Burr.

getting into enterprise is hard, so probably trying open source to help with that.

What would you like to do, but can't?

BSD-3 Clear Clause is very permissive - which covers the majority of the code.

What isn't BSD-3 is around features that are targeted at enterprises, e.g. auth. But you don't need to use them to get value from the project & UI; you can deploy to production without them.

Awesome! Great to hear! Would love to get your thoughts on the UI :) Feel free to file issues.

thank you!

Thanks!

This is what I use google keep (https://keep.google.com/) for -- though it's not as fully featured as yours, but it is free. In your opinion, what would be the main feature over that you'd say?