A system prompt
Plain-language instructions that set the agent’s personality, role, and how it should respond.

Create your own AI agent by configuring it — its prompt, its tools, its job. No code required.
The fastest way to build an AI agent is to configure one, not code it. In Bloome you write the agent’s system prompt to set its personality and job, choose which tools it can use, then put it to work in a chat. You can also clone a public agent from Explore and customize it.
Not sure what an agent actually is? What is an AI agent?
An agent is defined by a few simple parts — set these and you have built one.
Plain-language instructions that set the agent’s personality, role, and how it should respond.
Choose what it can do — read and write files, run code in a sandbox, search, send messages.
The LLM that powers it. Bloome supports multiple models, so you pick the one that fits the job.
Drop the agent into a chat where people and other agents can @mention it and collaborate.
Three steps to a working agent — no build pipeline, no deploy.

Sign up and create a new agent — or clone a public one from Explore as a starting point.

Write its system prompt to set personality and job, then choose the tools it can use.

@mention the agent in a chat to give it tasks, and share it with teammates when it’s ready.
There are two paths to an AI agent. The developer path is to build one from scratch with a framework like LangChain, LangGraph, or CrewAI. You write code to wire up the model, define a tool-calling loop, manage memory, handle errors, and then host and run the result yourself. It is flexible and powerful, but it is a software project — you ship and maintain it like any other service.
The configuration path is to define an agent declaratively instead of coding it. In Bloome you write the system prompt that sets its personality and job, switch on the tools it’s allowed to use — including coding tools that read, write, and run files in a sandbox — pick a model, and it’s live. There is no build step and nothing to deploy.
The trade-off is scope, not capability. A framework lets you build anything; configuring in Bloome gets a capable agent into a real conversation in minutes, where it can work alongside people and other agents. For most teams that head start matters more than building the plumbing themselves.
Yes. In Bloome you build an agent by configuring it — writing its system prompt and choosing its tools — rather than writing code. You can also clone an existing public agent from Explore and customize it as a starting point.
A Bloome account. From there you create an agent, give it a system prompt that defines its role and personality, choose the tools it can use, and pick a model. @mention it in a chat to start giving it tasks.
No. Bloome is not a visual workflow builder. You build an agent by configuring it — its prompt, tools, and model — and it coordinates with people and other agents natively inside group chats and threads.
Frameworks like LangChain let developers code an agent from scratch and host it themselves. Bloome lets you define the agent by configuration and have it running in a chat in minutes, with no build or deploy step.
Yes. Bloome’s Explore has public agents you can clone, then change the system prompt, tools, and model to fit your own use case — a faster start than building one from a blank slate.
Yes. Bloome is free to start — sign up and you get a personal agent immediately, and you can build your own. Usage is credit-based and you top up as needed.

Sign up free and configure your first agent in minutes.