Repository navigation
Arbiter 0.1.2 (pre-release)
Pre-release
Pre-release
v0.1.2
An update to the 0.1.1 pre-release: a first install gets its local model without a command line, and Claude
seats on plans with a weekly limit only (Ultra) are forecast and handled like the others, with a usage
forecast that checks itself against what really happened.
Security
- Arbiter's own HTTPS connections now distrust the eMudhra intermediate certificates whose keys were disclosed
on 2026-10-20 (CVE-2026-111943). Earlier versions, 0.1.0 and 0.1.1, trusted certificates issued with those
keys, so someone on your network path holding them could have impersonated the services Arbiter connects to.
No misuse has been reported. Updating to 0.1.2 is recommended.
Fixed
- A first install could leave the local brain without its model and point you to a command line. The model
is a separate download of about 5 to 7 GB (Gemma 4, Apache 2.0 license, from Hugging Face; no account is
needed). The Windows setup now offers it at the end, once, when your graphics card can run it; say yes and
it downloads when Arbiter starts, with the progress shown in the app. Until the model is in place, every page
of the app says so and downloads it with one click, as do Config, Brain and a "Brain not downloaded" chip at
the top.arbiter setup-llmstill downloads it on a machine without the app. - On a machine without Memory (Curator), the MCP page no longer lists it as down, and adding a project with a
memory domain no longer reports a failure: the project keeps the domain name. - The daemon's log no longer names a separate product's command on machines where that product was never
installed. - Keep timers warm no longer starts a session on a seat whose plan has no 5-hour window. Such a seat was
started every 30 minutes for nothing. - "Next free" on the Seats page and in the Telegram report now judges a seat by its most used account window
against the rotation percentage. A seat whose week was past that percentage, or one with a weekly limit only,
used to read as free while rotation refused it.
Changed
- Claude seats on a plan with a weekly limit only (no 5-hour window, such as Ultra) are forecast in week
points: when the week fills at your pace, who takes over and when everything pauses, instead of "no pace
yet". The top bar, the Overview tile, the brief and the rotation reply name the week when it is the limit. - The usage forecast checks itself. It replays its candidate paces (recent slopes, averages over hours and
days, the average since the reset, and a model of how many terminals and agents are working against your
usual load at that hour) over the last 7 days, scores how far each was off 1 to 72 hours later, and projects
with the blend that did best, or keeps its previous rule where nothing beat it. The panel says how far off
it was, for example "missed the week by about 8 points 24 hours ahead". - Model weekly limits such as Fable's are forecast with their seat: when the model runs out on each seat and
across all of them, and when it is back. - Seats on different plans count the same work at their own size: measured once a seat has been in use,
otherwise estimated from the plan (an Ultra week is 10 Pro weeks), and said so. Each seat shows how long it
would last on its own. - Tickets record their share of the week on every seat, are fitted in the unit of the seat in use, and say how
long they take at their own terminals' pace.
Build
Built from commit a6e3d32e4dfdd95d6e61dfd9e0334893381cdcfe of Arbiter's source. Every download is listed with its SHA256 in arbiter-0.1.2-<os>-x64.SHA256SUMS, signed with the Code Reality Labs release key (fingerprint 0CF6 23D6 6975 AC42 EF02 A1EA 98F3 6798 1E68 D3E3).