what changed in cli, week by week.

cli#

• ivybloom can stop a running turn and quote a job's credit cost before you submit it.
• Duplicating a campaign with its children copies its chats.
• The CLI stream's final frame reports the turn's usage, including for turns you stopped.

cli#

• ivybloom run shows the real error when a submit fails, and a retried submit returns the same job instead of creating a second one.

cli#

• The install command on the CLI page works.

cli#

• The CLI lists your storage roots, uploads files into a project folder, and pages through large folders when you preview them.

This post covers January to mid-July 2026, the months before the weekly changelog started. It summarises what you could do with .bloom* by July rather than listing every change, and the weekly posts pick up from here.

the workspace#

• Results land on a canvas as cards instead of scrolling away in the chat. You can arrange cards, open a card for more detail, drag a result from the chat onto the canvas, and click a result to add it as a card.
• Cards show a result in layers: the headline number first, the values that qualify it next, and the full record when you open it. A docking card, for example, leads with the score and keeps the poses and inputs one click away.
• Every chat has its own code sandbox with a terminal panel and a file tree. Ivy can write and run code there, and a table your code prints can become a canvas card.
• Studio runs a single tool from a form when you already know what you want, with a history of past runs and a resubmit button.
• A file explorer and Files panel organise chats, campaigns and project storage, so results from earlier work are easy to reopen.

working with ivy#

• Answers link what they cite. Accession numbers, PDB ids, variants, pathways and papers in an answer become links to their source records.
• Runs that cost credits ask for approval first and show an estimate, so nothing expensive starts without you.
• Jobs that finish after a turn has ended come back with a follow-up answer in the same chat, and a tray shows what is still running.

tools#

• The tool catalogue grew across single-cell and spatial analysis, genomics and pharmacogenomics, clinical and regulatory data, proteomics, crystallography and lab automation. Examples include clinical trial search, adverse-event signal scans, gnomAD variants, pharmacogene star alleles, GEO and PRIDE datasets, ENCODE, L1000 signatures, P2Rank pockets and ZINC22 compounds.
• Reports and documents compile to PDF from a chat, with templates for common write-ups.

sharing and access#

• Chats can be shared by link, and guests can try Ivy without an account on a smaller set of tools.
• The ivybloom CLI streams chat, submits jobs and browses project files from the terminal, with install options for each platform.
• The docs moved to /docs, with search and navigation organised by drug-development workflow.