From single chat to multi-agent pipeline

Chat is the front door. Pipelines are how teams turn a winning prompt into something repeatable — same stages, same quality bar, every time.

Start in chat

Prototype the goal in a thread. Tune memory keywords, attachments, and model routes until the merged output matches what you need. The task graph you see live is the blueprint.

Attach an assistant

Sample templates in the gallery encode role, variables, and output structure — ABM campaign plans, release bundles, support macros. Attach one to a chat when you want a specialist guiding that run without rebuilding the prompt from scratch.

Scale to a pipeline

When the same decomposition appears every week, save it as a pipeline: defined inputs, agent roles, merge rules, and deliverables (Markdown, CSV, slide outlines). Execute from the workspace or trigger via API — the status stream works the same way.