OpenLoop v0.2.0 — Backend Auto-Provisioning
What's New
Backend Auto-Provisioning
The ACE-Step Python backend is now automatically downloaded and installed on first launch. Previously, users had to manually git clone the backend repository into the runtime directory — a step that made the app unusable for non-developers.
- Automatic download: Backend code is fetched from GitHub as a zip archive, extracted, and version-tracked via a local manifest
- Update support: Check for and apply backend updates from the CLI (
openloop backend update) or Settings UI - Migration: Existing git-cloned backends are detected and tracked automatically
- Setup wizard: Engine download integrated into the model step (no extra wizard step)
CLI Improvements
openloop backend provision— Download and install the ACE-Step backend codeopenloop backend update— Update backend to the latest versionopenloop backend status— Now shows backend code version (tag or commit)openloop doctor— New backend-code health check- Progress display adapts to TTY vs piped output
openloop models listsyncs downloaded models from manifest for DB consistency- HTTP timeout (300s) added to prevent hung requests
Settings UI
- Backend Engine section shows installed version and update availability
- Update button when a newer version is detected
- Check for updates button
Upgrade Notes
No breaking changes. Existing installations will detect the current backend code and write a manifest automatically on first run.
File Changes
New files:
src-tauri/src/services/backend_provisioner.rs— Core provisioning service (~1200 lines)src-tauri/src/commands/provisioner.rs— Tauri IPC commands
Key modifications:
- Backend manager now checks provisioning before starting
- Model bootstrap status extended with
provisioning_backendstate - Setup wizard shows engine download progress
- i18n strings added for EN and ZH-CN