01 · Describe
Tell SyntheticBrew what you need. Write a plain-English brief and the AI builder proposes the agents, tools, and flows — or skip the prompt and configure everything visually on the canvas.
Visual and prompt-driven
Describe the outcome in plain English. SyntheticBrew proposes agents, tools, flows, gates, and memory—then lets your team inspect and refine every part in a visual canvas.
Describe. Brew. Run.
From a plain-English brief to a production endpoint — without stitching together agent plumbing in between.
Tell SyntheticBrew what you need. Write a plain-English brief and the AI builder proposes the agents, tools, and flows — or skip the prompt and configure everything visually on the canvas.
Agents assemble themselves: a supervisor plus specialists, tool bindings, confirmation gates, and memory scope. Each agent runs a ReAct reasoning loop out of the box — no framework code to write.
Ship to production behind a REST API with structured SSE streaming, the included web client, or an embeddable widget. Memory persists across sessions and every step stays inspectable.
One prompt, a working system
Give the builder a brief like “a support agent that answers from our docs, looks up orders, and escalates refunds.” It generates:
confirm_before, so it pauses for explicit approval before anything irreversible runs.Want the concept-level walkthrough first? Read how to build an AI agent, step by step.
name: support-supervisor model: claude-sonnet # any provider, per agent max_steps: 12 max_turn_duration: 120s # engine default tools: - search_docs # knowledge base (RAG) - lookup_order # MCP: orders API - escalate_refund # MCP: billing API confirm_before: - escalate_refund # pauses for approval memory: enabled: true max_entries: 50 # per-agent cap
Every generated agent is plain configuration you can read, diff, and version — not a black box.
Inspect and override
The canvas is not a diagram of the system — it is the system. Click any agent to inspect or override what was generated: system prompt, model choice, tool access, spawn rules, memory configuration. The admin dashboard puts every knob of the engine in one place, and the same configuration exports and imports as YAML for review in a pull request.
That is the difference from drag-and-drop tools that stop at the prototype: generated agents run a real ReAct loop with per-agent step limits and a 120-second default turn duration, per-tool timeouts, and full session persistence. See how that compares in SyntheticBrew vs Flowise.
Agents that build agents
The AI builder is itself a SyntheticBrew agent running on the same runtime it configures: the same ReAct loop, the same tool execution, the same streaming protocol. When you brief it, you are watching the platform use itself — which means the builder exercises every code path your agents will depend on in production.
Product teams use this loop to go from an idea in a sprint-planning doc to a reviewable agent system the same day. If that is your situation, see SyntheticBrew for SaaS and product teams.
Keep exploring
Questions
Yes. Describe what you need in plain English and the AI builder proposes the agents, tools, flows, and gates — or configure everything on the visual canvas. When your team wants config-as-code, export any agent as YAML and check it into your repo.
Real runtime configuration: a supervisor and specialist agents, tool bindings scoped per agent, confirmation gates on consequential actions, memory scope, and the flow edges that connect them. Nothing is a mockup — click any agent on the canvas to inspect or override what was generated.
The canvas edits the same configuration the production engine runs. Generated agents execute a ReAct loop with per-agent step limits and a 120-second default turn duration, expose a REST API with structured SSE streaming, and persist memory and session history in PostgreSQL.
OpenAI, Anthropic, Google Gemini, Azure OpenAI, Ollama, OpenRouter, or any OpenAI-compatible provider such as DeepSeek and Mistral — and you can pick a different model for each agent in the system.
Brief the builder in Cloud, self-host the open-source engine, or book a call and have us deliver the implementation.