batch results land in the chat, and a declined run stays declined

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".