Ivy

Chat is the browser way to start a run; curl, the CLI, and MCP reach the same tools. You describe a scientific goal in plain language — "fold this sequence and find its pockets," "compare the safety of two drugs" — and the orchestrator selects the tools, chains the steps, and streams results back as interactive canvas cards with inline citations. You never have to name a tool or wire a pipeline; the request reads like a sentence, and the work happens underneath it.

Reach for Chat when the shape of your work is a question rather than a project. It is the fastest path from "I want to know X" to a grounded answer, because the routing, the multi-step chaining, and the result rendering are all handled for you. When you instead want direct control over files, parameters, and layout, the .bloom* studio is the project-based surface onto the same backend — same tools, same job history, different way to drive them.

What this section covers

The pages below move from first message to organizing a body of work. Read them in roughly this order.

Where to start

New to the surface? Begin with the Quickstart, then read Chat Features to learn what you can steer (response style, thinking mode, file references). Once results start arriving, Canvas explains how a job becomes a card you can expand and export. When your work outgrows a single thread, Campaigns groups related chats into one project.

Read next