v0.7.1

Released 23 October 2026, with routing control updates on 25 October 2026. GitHub release.

Custom Auto and Full Auto profiles

Create several routing profiles in Settings → Model routing. Custom Auto uses your selected variants; Full Auto includes every visible, enabled and compatible variant, including variants added later.

Start from the editable Everyday and Thorough presets. Everyday matches the task requirements to configured model roles. Thorough prefers higher configured roles within the permitted pool.

Your models, rules and effort

Match rules to task type, complexity, language, purpose and capability requirements. Assign an exact model variant, set preferences, restrict a pool or exclude variants. Nested ALL/ANY conditions are supported.

An explicit assignment can send a routine task to a powerful model or a complex task to a smaller one. Select a default variant for uncertain classification. Access controls, capabilities, locality and shared limits continue to apply.

Connections store credentials and endpoints, models describe the configured API model, and variants hold effort and generation settings. Clone profiles, import/export their configuration without credentials, and bind profiles to chats or projects.

Personal settings and shared models

Ordinary users can create personal profiles and variants of visible shared models without an administrator role or their own API key. Personal connections follow the installation's BYOK setting. Administrators retain control of shared connections, models and mandatory restrictions.

These routing capabilities are included in open-source Core and are also available in Enterprise.

Routing settings controls

Profile import uses one themed button. Saved-policy and API alias menus use the application's dropdown styling. Action groups in connections, models, variants, profile import and editors have consistent spacing and wrap on narrow screens. Field labels remain associated with their controls.

The release also corrects production and test container build inputs.

Updating an installation

Use matching backend, ML and frontend components. Back up the installation, keep its .env and persistent volumes, and set APP_VERSION=0.7.1 in .env to pin this version.

docker compose pull
docker compose up -d

Existing 0.7.1 installations should also pull the images to receive the refreshed routing controls. Database migrations run during normal backend startup. The independently versioned desktop client keeps its existing version.

See Automatic model routing for profiles, setup and operational controls, and Upgrades & TLS for the deployment procedure.