BenchLocal releases v0.2.6 with offline-skip runs for tight-VRAM tests
BenchLocal v0.2.6 adds reachability checks so offline local models are skipped and resumed instead of breaking side-by-side tests. The update is aimed at tight-VRAM setups where creators and tinkerers load providers one after another on the same machine.

TL;DR
- BenchLocal v0.2.6 adds reachability checks, so an offline model or provider gets skipped instead of killing a side by side benchmark run, according to stevibe's v0.2.6 announcement.
- The workflow target is tight-VRAM setups, where users cannot keep every local model loaded at once and instead bring servers up one after another, as stevibe's thread describes.
- BenchLocal says those interrupted comparisons can now resume as providers come online, a small but very practical quality-of-life fix for local eval tinkering per stevibe's earlier post and the main release post.
- The same release also bundles unspecified fixes plus UI and UX improvements, with the changelog linked from stevibe's announcement.
You can jump straight to the v0.2.6 release notes, browse the BenchLocal site, and the core change is unusually specific: stevibe's launch post is about not having enough VRAM to load every model at once, then letting the benchmark keep moving anyway.
Reachability checks
BenchLocal now checks whether a model or provider is actually reachable before trying to run it. If that endpoint is offline, the run skips it temporarily instead of failing the whole comparison, according to stevibe's post.
That makes this release more about benchmark continuity than raw scoring. The useful part is the skip behavior itself, because local model setups break most often at the plumbing layer, not the prompt layer.
Sequential loading
The release is aimed at the common one-GPU reality where you cannot keep every candidate model loaded at the same time. stevibe's thread says users can start model servers one after another and resume the same test as each provider comes online.
For people comparing local models on a single machine, that turns a side by side benchmark into a staggered workflow instead of an all-or-nothing one.
Release notes
The published release description is short: reachability checks, temporary skipping for offline providers, resumed testing, and additional fixes plus UI and UX enhancements via the GitHub release page.
BenchLocal also supports in-app updating, while stevibe's announcement points new users to the official site.