what shipped in FY26 Q3.

Failed jobs explain their cause in plain language, and HTTP API callers get one clean answer, streamed or not. Lab-automation tools run in the chat sandbox.

jobs#

• A failed job's card shows the cause in plain language, so you can decide whether to change the input or try again.
• Batch status lists the error for each failed row.

http api#

• Streaming and non-streaming calls return the same answer text, once. A stream carries only answer text and ends on exactly what a non-streaming call returns.

tools#

• Octave, Opentrons protocol generation and PyLabRobot run in the chat sandbox, alongside your other code and files.
• ProteinMPNN keeps the structure you named through to the run.
• ClinPGx filters match on the variant fields in the data, and RxNorm lookups return the identifiers and ingredient concepts.

chat#

• A tool call that has already returned its result shows as finished, not in progress.
• The quick-action chips on the homepage show only actions a guest can run.

exports#

• Markdown chat exports label each source, so merged sources stay distinguishable.

site#

• Public pages have wider text columns, page titles keep their written casing, and prices group thousands.

A canvas card now shows when a job's result came back empty or unusable, and answers that contain SMILES strings or tables arrive whole.

canvas#

• A card for a job that returned an empty, placeholder or implausible result shows the failure message and a failed state, instead of a green status and a metric chip. You can tell at a glance which results to trust.
• The small preview a card shows when it first appears uses the same failed state.

chat#

• Lists of SMILES strings and markdown tables arrive intact. Short answers full of bond and ring notation are no longer replaced by a cut-off notice.
• An answer that is cut short gives the right reason for it.
• Long turns that chain several tools keep running when a background job reports back partway through.
• The end-of-turn summary counts the analysis that ran, and says when a turn was interrupted.

If you name a tool and the result came from a different method, the answer says so. A reply cut short by your next message is marked as partial.

chat#

• When you name a tool, it isn't run, and another method produces the result, the answer adds a note saying so. You know which method the result actually came from.
• A reply that ended early because you sent your next message is marked "reply ended early - partial answer preserved", so it doesn't read as a finished answer.
• Queued prompts are editable before they send.

file explorer#

• Chat cards stay steady while the list updates, so clicks land where you aim them.
• A chat card shows as selected after a single click.

tools#

• PROTAC and degrader requests take the fields the tool expects, so a request phrased in your own terms reaches the tool intact.

exports#

• Exported transcripts no longer repeat tool-call blocks.

A notification arrives when a job completes or fails, and the terminal app shows tool results as tables you can search and sort.

jobs#

• A bell notification marks each job that completes or fails. You can leave a long job running and come back when the bell shows it's done.
• A finished job reports its completion in the chat once, rather than repeatedly.

terminal app#

• Lists of records render as tables, with a summary line for each numeric column, so you can read a result set without scrolling raw output.
• The sessions, memory and other list panels have a cursor, search and sort.
• The command palette shows argument hints and keyboard shortcuts beside each command, and runs commands that take no argument as soon as you press Enter.
• Headless mode is a single option and prints the answer once.

chat#

• The plan progress card shows only the workflow you asked for, not a different one that matched equally well.
• Clinical trial results keep their canvas preview when you reopen a chat.

exports#

• Exported transcripts match what you saw on screen. Text that was visible is included, and drafts that were never delivered are left out.

tools#

• ColabDock takes receptor and binder chains by chain id.

IgBLAST cards show the full germline picture, ThermoMPNN takes standard mutation shorthand, and the terminal remembers what you typed.

canvas#

• IgBLAST cards show V identity, framework mutations, and the candidate V, D and J germline hits. They used to show only the top hit, so you can now compare close alternatives on the card.

tools#

• ThermoMPNN accepts mutations written as S31A, or with a chain prefix as H:S31A.
• ddG and mutation-scan requests go to binding ddG and ThermoMPNN rather than a general tool.
• Antibody, peptide and vaccine lookups go to sources that hold biologics, instead of a small-molecule database that can't answer them.

terminal app#

• Prompt history carries across sessions, so the up arrow brings back what you asked yesterday.
• /attach with no path opens a file browser to pick from.
• Diffs can show side by side.
• A stream that drops on a brief connection fault retries on its own. Errors show a short explanation next to their code.

chat#

• Older chats that contain an incomplete tool record open and continue normally.
• When a response is cut off, a toast names the tool calls that never started.
• Tool results that arrive late attach to the answer that was already saved.
• Exported transcripts count every tool that ran in a step.

Stop ends the run, even with a second message queued. Chats and canvases pick up again after a dropped connection, and the mobile site has its full navigation back.

chat#

• Stop ends the run when you have sent a second message while the first was still going. A queued prompt waits for you rather than sending itself after you press Stop.
• Live chat updates resume after a dropped connection. The message list catches up on its own, without a reload.
• Streaming text stays in place as it arrives instead of being wiped and repainted.
• Delivered answers no longer contain unfilled template placeholders.

canvas#

• Live canvas updates resume after a dropped connection, and the card list refreshes once the link is back.

web#

• On phones the top navigation stays pinned while you scroll, and the sign-up button is back on phones, tablets and narrow laptops.
• The mobile menu lists every destination again.
• Dead links on the resources page are fixed, and the login page loads faster.

cli#

• The install command on the CLI page works.

Running jobs show how long they have left, and a reloaded chat brings back what Ivy ran, not only the reply text.

chat#

• Reloading a chat restores its tool calls and their results along with the replies. Ivy continues with the full history, and you can reopen any earlier result.
• An approve or deny click made after a pause registers. You can step away from an approval card and come back to it.
• Returning to a tab no longer drops a message that hadn't finished saving.
• The final answer appears without a short planning paragraph flashing first.

jobs#

• Running jobs show time remaining, estimated from their progress so far.

canvas#

• P2Rank cards show pocket scores and pocket counts, and AiZynthFinder cards show route counts, when the job returns a summary.
• Antibody and omics cards that used to show no metrics now show completion counts.
• Very large results keep their canvas cards instead of the card disappearing.

cli#

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

tools#

• ClinicalTrials.gov searches accept recruitment statuses such as "active" and "not yet recruiting".
• A decimal in a field that takes whole numbers returns a clear message with the allowed range, instead of being quietly treated as zero.

The terminal app now works much like an editor: search commands, attach local files, resume a session, and read code and diffs in colour. Large campaigns list their jobs again.

terminal app#

• Ctrl+P opens a command palette with fuzzy matching. Type a few letters from anywhere in a command's name and the best matches come first.
• /settings opens a preferences panel, including a theme palette that previews as you move through it.
• /attach reads a local file into your message, so you can ask about a CSV or a PDB on your machine without pasting it.
• A session picker resumes an earlier session by id, with its history intact.
• A multi-line composer keeps longer prompts readable while you type them.
• Expanded tool cards show code with syntax highlighting and diffs with a +/- gutter.
• When several tools run at once, a progress view shows each one. Notifications appear as toasts that don't block typing.
• Your model choice, with recent and favourite models, carries across restarts.

jobs#

• Campaigns with thousands of jobs list and page correctly, with the right counts.
• A job whose results are already saved shows as finished, even if its status hasn't caught up.
• A run that finishes with no items says so, including AiZynthFinder runs that find no routes. You see an empty result instead of a guess.

canvas#

• Generic canvas cards show result values in their metric slots instead of bookkeeping fields such as the tool name or parameter list.

Reload a chat or switch back to it and Ivy still has the whole conversation, earlier tool results included. Jobs that finish in the background make it into the answer, even with the tab closed.

chat#

• Reloading the page, switching chats or coming back to a tab restores the full conversation for Ivy. The next turn carries on from where you were instead of starting cold.
• Earlier tool results stay available after a reload. Ivy works from data it already fetched rather than asking for it again.
• Ivy plans every tool you name in your message, not only the first one.
• An answer stays on screen while Ivy revises it. You no longer see it replaced by a "Revising response..." placeholder or flash and redraw with the same text.

jobs#

• Jobs that finish while your tab is closed get a follow-up answer the next time you open the chat.
• Results from jobs that complete on their own, such as batch rows and parallel runs, are included in the answer instead of being reported as missing.
• A repeated docking request in a later turn reuses the earlier job rather than starting a second identical one.

tools#

• Free energy perturbation runs when you ask for it by name, on 2 to 20 compounds.
• Pocket prediction runs on a PDB or UniProt id. Structure, docking and design tools accept a PDB you just downloaded in the same chat, so a pipeline can go straight from download to design.
• 4DN file and experiment-set accessions pasted into a message go to the right lookup.

exports#

• Exported transcripts show plain labels with links to the job viewer, and keep the real answer when a short stub was saved after it.

Batch runs deliver their results into the chat, and switching models partway through keeps the conversation. Tools you name are ready from the first turn, and a run you decline stays declined.

jobs#

• Finished batch runs deliver every result to the chat, including runs whose status lagged behind the work. If you submit a panel of four antibodies and all four succeed, all four appear in the answer.
• Jobs that time out or fail say so in the answer. You no longer see "still running" for a job that has already stopped.

chat#

• Switching models mid-chat keeps the earlier turns. The next answer knows what you asked before, so you don't have to restate it.
• Free tools run without a $0.00 approval card. When free and paid tools run together, only the paid ones ask for approval.
• A costly run you decline is not requested again in the same turn. The chat moves on instead of waiting on another approval card.
• Tools you name in your message are available from the first turn, even when they belong to a different kind of task. Ivy no longer replies that a tool you just named is unavailable.
• Antibody design requests go to antibody tools rather than small-molecule ones.

tools#

• Clinical entity extraction, clinical summarisation, ICD coding, and flow cytometry gating and differential analysis are available in chat. Ask for them by name or describe the task.
• A 4DN experiment search that returns nothing says so plainly, instead of continuing to a Hi-C step with no input files.

exports#

• Chat exports work for chats that contain jobs. They used to come out as "No items to export".

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.