v0.1.10
Tempest v0.1.10
A small bug-fix release. The one user-facing change: turning on Atlas semantic search from Settings no longer fails silently — if the model download breaks, the reason shows up inline so it's actually fixable.
What's in this release
Semantic search: real errors instead of "Download failed"
Enabling Semantic code search in Settings spawns a short-lived Node subprocess that fetches the ~25 MB embedding model. When that subprocess failed — node not on PATH, offline, disk permissions, model host unreachable — the toggle just flipped back off and said "Download failed", with no way to tell what actually broke. Retrying was pointless because nothing about the environment had changed.
Now the toggle shows the real error underneath it: the Rust command's return message plus the last few stderr lines from the Node subprocess. That's enough to distinguish "Node isn't installed" from "the model host timed out" from "I can't write to the app-data folder" — so the next click is an informed one, not another blind retry.
Release pipeline (carried in from the 0.1.9 point fixes)
Along the way, the release workflow itself got the hardening it needed to actually deliver builds to every supported platform: macOS ships as separate arm64 and x86_64 artifacts (unsigned, documented), Linux arm64 pulls the correct Tauri and rollup native binaries, the AppImage runs cleanly on Wayland, the installer pulls in xdg-utils, and the site's release-notes fetch is hardened against upstream flakiness.
Platform Support
| Platform | Status |
|---|---|
| Windows 11 (x64) | Supported. Pre-built binary available. MSI and NSIS installers. |
| macOS | Supported. Separate arm64 and x86_64 builds. |
| Linux | Supported. x86_64 and arm64 AppImage + deb. |
Windows requires WebView2 (bundled automatically when necessary).
Database Branches (from v0.1.5) additionally require Docker; without it the feature stays dormant and everything else works normally.
What's next
Unchanged from v0.1.9 — Live quota and Automations triggers and scheduling remain the carried-forward commitments.