Skip to main content

    · covers Oct 26 – Nov 2, 2026

    ivy suggests next steps instead of running them, and stop reaches jobs

    Ivy offers follow-up steps as one-click suggestions, Stop cancels the jobs and code runs a turn started, and a turn pauses when credits run out.

    provenance: agent (anthropic/claude-opus-5.5) from commit history; reviewed in PR before publishing.

    Ivy now offers follow-up steps as one-click suggestions instead of running tools you didn't ask for, and Stop reaches everything a turn started: the reply, a running code cell and any job it submitted. When credits run out mid-answer, the turn pauses so you can top up and carry on.

    chat#

    • After a tool finishes, Ivy offers the next steps as one-click suggestions rather than running them. The workflow a chat follows includes the tools you asked for and holds through the whole answer, and guests get suggestions limited to tools they can run.
    • Stop ends the turn even when the model has stopped responding, halts a sandbox code run that is still going, and cancels any job the turn submitted. This works the same in guest chats.
    • An answer from a background job appears in a chat you already have open, without reloading, and always in the chat that started the job. A reply that finishes in a background tab is saved as soon as it completes.
    • A reply that retries partway through shows only the final attempt, and numbers in scientific notation such as 2.6e-10 come through intact. Answers stop saying jobs are still running once every job has finished.
    • Sending a message in a shared chat you can only read offers to fork it. If you sign in partway through a chat, it switches to your account's tools and limits once the current reply finishes, with no reload.

    plans & billing#

    • When your credits run out mid-answer, the turn pauses with a card that opens the credits page in a new tab. Add credits there and the answer continues where it stopped.
    • Usage history, credit exports and CLI invoices list cost corrections as their own lines, and credit summaries, usage trends and monthly limits net them out.

    jobs#

    • Failed job cards show the reason the job failed. Retry is offered for a job that failed on a dropped connection or a timeout, and not for one whose input file is missing.
    • Job cards in saved chats show the finished result after you reopen, reload or export the chat, instead of staying pending.

    canvas#

    • Humatch scores a heavy and light chain as a pair, and scoring by antibody name uses both chains when both are known. The humanness card shows each chain and the paired score.
    • Expanded IgBLAST cards say which gene segments a query searched. Protein queries search the V gene only, so an empty D or J field means not searched, not a negative result.

    tools#

    • Generated reports include a drawing of the job's molecule, so a report reads on its own without opening the canvas.

    api, cli & site#

    • The sessions and sandbox API is documented under /api/v1, and the previous paths keep working. In the ivybloom terminal chat, tool calls that were blocked or skipped show as failed instead of pending.
    • A new audit trail section in the docs explains how to verify a chat's record yourself, and guests can check their own chat's record on the verify page while their session lasts. The models page maps the folding, docking, ADMET, design and omics models Ivy runs, and the plan comparison shows which workflows each plan opens.
    Loading...