failed job cards say why, and api answers arrive once

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.