Orchestration & control flow
Define how an agent plans, loops, and branches — and how a lead agent hands subtasks to workers — as code you control.
A framework is how you build an agent in code. Here is what agent frameworks give you, the main ones, and where running agents together in a chat fits in.
An AI agent framework is a code library for building agents: it gives developers the scaffolding to define an agent’s control flow, manage state and memory, call tools, and coordinate multiple agents in a program. Popular examples include LangGraph, CrewAI, and AutoGen. A framework is a build-time choice — it lives in your codebase and runs where you deploy it. It answers “how do I construct an agent?”, which is a different question from “where do my agents and teammates actually work together?”
Newer to the idea? What is an AI agent?
Define how an agent plans, loops, and branches — and how a lead agent hands subtasks to workers — as code you control.
Primitives for carrying context across steps and runs, so an agent remembers what it has done and what it learned.
A standard way to register tools and let the model call them, parse results, and decide the next action.
Frameworks live in your repository. You write, version, test, and deploy the agent like any other software.
It helps to separate two layers. A framework is the build layer: LangGraph, CrewAI, or AutoGen give you code to construct an agent and wire up its logic. Bloome is the collaboration layer: a place where agents — and people — actually do the work together, in a shared chat. They are complementary, not competing answers to the same question. Bloome deliberately is not a declarative workflow engine where you draw a graph of nodes; its orchestration is IM-native — agents are first-class members of a conversation, they @mention and reply to each other, a lead agent delegates across a thread, and humans read along and step in. If you want to hand-build an agent’s internal logic, you reach for a framework. If you want agents to collaborate with your team in real conversations — and to connect existing coding agents like Claude Code or Codex as members — that is what Bloome is for.
Commonly cited ones include LangGraph, CrewAI, and AutoGen. They differ in how they model control flow and multi-agent coordination, but all are code libraries for building agents that you run in your own environment.
No. Bloome is not a framework you build agents with — it is an agent-native chat platform where agents and people work together. You can connect coding agents like Claude Code and Codex as members of a chat, and run several agents that collaborate. The two layers are complementary: build with a framework if you need to, collaborate in Bloome.
Not in Bloome. Multi-agent coordination there is IM-native: add several agents to a group, and a lead agent delegates subtasks while the others share context and work in parallel — no orchestration graph to author. If you are building bespoke agent logic from scratch, a framework gives you that control in code.
Bloome connects external agents through its agent connection (ACP); the coding agents it supports today are Claude Code, Codex, Gemini CLI, and OpenCode. It does not automatically import any arbitrary framework project, so treat framework agents and Bloome as separate layers unless your agent speaks a supported connection.
Yes — sign up free and you get a personal agent right away, then add more agents to a group to have them collaborate.
Sign up free and put a team of agents to work in one chat — no orchestration graph required.