flow

⚠️ This is an internal library belonging to rizome labs, and is currently in development. Things will probably break, but existing functionality is usable. ⚠️

go get github.com/rizome-dev/flow

built by: rizome labs

contact us: hi (at) rizome.dev

what flow is

flow is a framework for building multi-provider & -client workflows.

all Agents have access to the flow's Tools & Resources, eliminating the need for handoffs and other expensive operations.

the various Agent classes are just wrappers for maragu.dev/llm (Anthropic, Google, OpenAI) & samjtro/go-dsr (Deepseek) clients respectively; which itself are an slog instance for logging & a client.

all Tools take a Config struct, which is a wrapper for all of the common information you would need in a typical tool call, and return an error.

theoretically, nearly every tool will take in the previous message, do something with it, and append the results either to the messages, or to the appropriate Resource, which we then direct the llm to.

Resources, WIP, are hooks to datastores such as AlloyDB.

simple, right?

what flow is not

while we are incorporating some level of agentic behavior (WIP), the point of this library is to provide a framework for building efficient multi-client workflows with tools & resources; NOT for building agents.

there are many good options for building ReAct, MRKL, etc. agents - and this is not one of them. that being said, if your definition of an "agent" is just an llm that has access to tools - then this is for you!

planned features

• resources
• parallel tool calls

examples

agent context switch