Burr FrameworkFrameaçiune opent source pentru Python pentru crearea aplicațiilor și agent-ilor cu decizii și state persoanelor în control

Why the name Burr?

Apache Burr is named after Aaron Burr, founding father, third Vice President of the United States, and historical opponent of Alexander Hamilton. The name reflects the project's origins as a harness to handle state between executions of Apache Hamilton DAGs (because DAGs don’t have cycles). Over time, Burr proved useful for a wide array of applications, leading to its broader release.

Asked by Naomi Suzuki · Nov 13, 2025

What can you do with Apache Burr?

Apache Burr can be used to power a variety of applications, including: 1. A simple GPT‑like chatbot. 2. A stateful RAG‑based chatbot. 3. An LLM‑based adventure game. 4. An interactive assistant for writing emails. It also supports non‑LLM use‑cases such as time‑series forecasting simulations and hyperparameter tuning. Using hooks and integrations you can integrate with any of your favorite vendors (LLM observability, storage, etc.) and build custom actions that delegate to your favorite libraries (like Apache Hamilton). Burr does not build models, query APIs, or manage data for you; it helps you tie these components together in a scalable, logical way. It includes out‑of‑the‑box integrations and tooling to build a UI in Streamlit and watch your state machine execute.

Asked by Valentina Marino · Nov 1, 2025

How does Apache Burr work?

With Apache Burr you express your application as a state machine (i.e. a graph/flowchart). You can (and should!) use it for anything in which you have to manage state, track complex decisions, add human feedback, or dictate an idempotent, self-persisting workflow. The core API is simple – the Burr hello-world looks like this (plug in your own LLM, or copy from the docs for gpt‑X). Apache Burr includes: 1. A dependency‑free low‑abstraction Python library that enables you to build and manage state machines with simple Python functions. 2. A UI you can use to view execution telemetry for introspection and debugging. 3. A set of integrations to make it easier to persist state, connect to telemetry, and integrate with other systems.

Asked by Carlos Mendoza · Oct 27, 2025