api runs return their tool calls, and shared chats show images

HTTP API runs return what Ivy called, the jobs it started and what it cited. Shared chats show their images and downloads, and R scripts and notebooks run in signed-in chats.

http api#

• A response carries each tool call's id and arguments, the job ids it started, and its citations. You can trace an answer back to the runs behind it.
• A request can name the tools Ivy may use, or the tools to leave out.
• A names-only tool catalogue lists what you can ask for.
• Download links for a finished job's files are one call away, so you don't need the CLI to fetch outputs.
• A turn ends when the caller disconnects.

sharing#

• A shared chat shows its images and offers its files as downloads.
• A share link shows only the cards from the chat you shared.

sandbox#

• R scripts and notebooks run in signed-in chats, and Octave runs in guest chats.
• R and Octave errors come with hints written for those languages.

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.

tools#

• AlphaFold DB ids resolve to structures.
• GWAS Catalog lookups use the current catalogue, and very small p-values stay marked significant.
• A PheWAS source failure reports as an error rather than an empty result.

canvas#

• LigandMPNN designs render on their canvas cards.