Repository navigation
Arbiter 0.1.1 (pre-release)
Pre-release
Pre-release
v0.1.1
An update to the 0.1.0 pre-release: the local model now fits itself to your graphics card, so a card with
8 GB runs it, and its answers no longer drift after a long request.
Changed
- The local model fits itself to your graphics card. At start Arbiter reads how much memory the card has and
picks the model and the largest context window that still leave room for your desktop. A card with 10 GB or
more runs Gemma 4 12B at the full 65,536-token window. An 8 GB card runs the same model at a smaller
quantization (Q3_K_S, about 6.3 GB on the card), which matched or beat the full-size file on every job in
Arbiter's own benchmark. Config, Brain andarbiter doctorshow the card's memory and why the model and
window were chosen, andarbiter setup-llmand the app's Get started download the model this card runs. A
model or window you choose yourself is kept, with a warning when it looks too large for the card. - On a card with less than 8 GB, the local model no longer tries to start and fails: Arbiter says how much
memory the model needs and how much the card has, and everything else keeps working.
Fixed
- The local model's answers no longer drift after a long request. With Gemma 4 the brain kept part of the
previous request's working memory that its sliding-window layers had already overwritten, so a call that
followed a long chat step could come back wrong: approvals, routing, titles and Curator's extraction on the
shared brain. A call on such a model now starts from a fresh context, or from a point saved exactly where
its prompt stops matching a recent one, so a chat step re-reads only what changed since the step before:
about 5.9 s a step for Gemma 4 12B on a 16 GB card, with the same scores on Arbiter's own benchmark. - The app,
arbiter mode statusand Config, Brain said the local model was loaded when it had failed to
load, for example before the model was downloaded. They now say loaded only once the model is in memory. - On Windows, closing Arbiter from another program now ends it while it is hidden in the tray. An installer,
a script ortaskkillused to leave it running there, with its program file locked; your own close still
hides it.
Build
Built from commit 7393bb24bb91967f32f200dd4f1da491e4a18492 of Arbiter's source. Every download is listed with its SHA256 in arbiter-0.1.1-<os>-x64.SHA256SUMS, signed with the Code Reality Labs release key (fingerprint 0CF6 23D6 6975 AC42 EF02 A1EA 98F3 6798 1E68 D3E3).