LizzyDocs

Product updates

Changelog

Contract, workflow, and safety changes that affect how people and copilots run Distill end to end.

13 August 2026

Workflow

Durable copilot journeys

Copilot work now persists across reconnects with explicit phases, blockers, resource references, bounded watches, human handoffs, and resume or abandon controls.

Safety

Dry-run proof and plan hash

Live training can reference a successful validation run and its immutable plan hash, making approval specific to the exact version, rewards, recipe, compute, and budget.

Data

Durable connector pulls

Connector pulls now return a persistent pull resource with progress, row count, dataset version, and recoverable error state.

Contract

OpenAPI 3.1 at /v1/openapi.json

The public contract now records workflow stage, prerequisites, idempotency, async terminal states, recovery guidance, and human-only boundaries. Internal routes stay private.

Experience

One copilot, everywhere

The full copilot page and in-product dock share the same session, transcript, proposals, and page context.

Compatibility policy

Existing live run creation remains accepted when validation references are omitted. New clients should supply validated_dry_run and plan_hash for the safer approval flow. New fields are additive; removals or semantic changes require a dated migration note.

Stay informed

Check this page before upgrading generated clients or production automation. Machine consumers should diff the OpenAPI document and fail closed when a mutation is not classified.

Built for humans and copilots.

Every risky action has an explicit handoff, validation, or approval boundary.

Recovery guide