Connect agents

A connection is a directed edge from one agent to another. It tells the orchestrator: "after the source finishes, the target reads its output and runs next." Drawing a connection Hover over an agent. Two small handles appear on its left and right edges. Click and drag from the right edge of the source agent to the left edge of the target. A connection line draws between them. Connections are always left-to-right ; they imply ordering. If you try to draw a connection going backward, Cerevisor blocks it. (Loops are a separate connection type, see Control flow .) Smart auto-connect By default, when you add an agent to a new column, Cerevisor automatically wires every agent in the previous column to your new agent. This is auto-connect , and it works because most workflows want every upstream agent to feed every downstream one in the next wave. Auto-connections render with dashed lines . Manual connections are solid . If you draw a manual connection between two agents that auto-connect would have made, your manual wire wins (the dashed line disappears). You can disable auto-connect per workflow in Settings → Workflow → Auto-connection exclusions by checking off roles you never want auto-wired. Handoff formats Click a connection (or double-click) to open the Connection Config popup. The most important field is Handoff format : Format What downstream sees Summary A short LLM-generated summary of the upstream agent's output. Useful when the full output is long and you only need the gist. Structured JSON The upstream output coerced into a JSON schema you define in Handoff schema . Use when the downstream agent needs specific fields. File reference The upstream agent's outputFiles[] — by name, not content. The downstream agent reads them via the read_file tool. Useful when output is large; keeps context lean. Full output The upstream agent's complete output, verbatim. The default. Use when downstream needs everything. The right format depends on context budget. Long workflows with chatty agents benefit from Summary or File reference; short workflows can stick with Full output. Data description A free-text field on the connection. Describes what data flows over this edge. The text is included in the generated prompt so downstream agents understand the intent. Example: "Vetted candidate sources with confidence scores." You don't have to fill it. Cerevisor generates a sensible default from the source agent's output definition. Selecting and editing connections Click an edge to select it. Shift-click to multi-select. Double-click to open Connection Config. Right-click for the connection context menu (Configure / Flow Type / Delete). Delete / Backspace with edges selected removes them. Auto-connection patterns Three common patterns the harness handles automatically: One-to-many fan-out: one upstream agent feeds N downstream agents in the next column. All N start in parallel. Many-to-one fan-in: N upstream agents feed one downstream. The downstream waits for al

Back to docs