Distill 2.0.0

What’s new

• A guided four-step onboarding experience for first use, available again with
  /onboarding, with model selection, optional worker configuration,
  keyboard and mouse navigation, persistence feedback, and recovery for
  narrow terminals.
• Clearer active model and effort attribution across reasoning, worker,
  fallback, retry, cancellation, and child-session activity.
• More consistent routing and child-session handling for explicit model and
  effort choices, compatibility checks, persistence, resume, and recovery.
• Updated Distill branding and tool-contract names across current product
  surfaces, with compatibility aliases retained for existing configurations
  and serialized data.
• Jev remains an optimization layer, while tool authorization continues to be
  controlled by Distill’s permission system.

Compatibility

Existing connected accounts, provider configuration, permission modes, and
legacy environment or serialized values remain readable. New writes and
current documentation use the canonical Distill names.

OpenRouter can provide additional model and routing choices; a less-expensive
model may lower cost for a suitable workload, but OpenRouter alone does not
reduce token usage and no fixed savings percentage is promised. Onboarding
keeps authentication and external actions user-controlled and never follows
an account automatically.