Extend
Decision judge
The judge is a small model that answers with probabilities, not text. You give it a situation and a closed list of options, and it returns which one it picks and how sure it is ("the Search field, 95 %"). It takes a fraction of a second and costs a fraction of the main model.
It is a Lampson setting, like the model provider: you choose it once and whatever needs it uses it. Today computer use does:
- The
actaction: instead of the main model reading every element of a window and choosing one, Lampson builds the list of controls (buttons, checkboxes, fields, links) and the judge picks the one for the step. When it is sure, Lampson runs it; when it hesitates, it hands its best candidates to the main model to decide. - Dropdowns: when the option you asked for is not written the same way ("6 to 10 people" vs "6-10"), the judge picks which one it is.
The judge never decides that the task is done (the main model checks that) and never sees submit, delete, buy or close buttons.
Jev or Laya§
| Jev (TypeSafe) | Laya (local) | |
|---|---|---|
| where it runs | in TypeSafe's cloud | on your machine |
| speed | ~0.3 s per decision | ~1-2 s per decision on CPU (the first one ~11 s: it loads the model) |
| languages | English, Spanish and more: 30 out of 30 right in our tests in both | the English checkpoint gets non-English interfaces wrong, sometimes very confidently |
| cost | pay per use, with your API key | free |
| privacy | receives the requested step, the page title and the controls' names | nothing leaves your machine |
| what you need | an API key from console.typesafe.ai | the Laya checkpoint folder (~840 MB, you download it) |
Recommended: Jev. Laya is for when nothing may leave your machine and your applications are in English.
Set it up§
- Web: ⚙ → Decision judge → pick Jev (paste the API key) or Laya (the checkpoint folder) → Save. The workspace restarts by itself in a few seconds and the page reloads with the judge live.
- Terminal:
- /judge jev — asks for the TypeSafe API key if none is saved yet. - /judge laya C:\Users\you\models\laya — or /judge laya and it asks for the folder. - /judge off — turns it off. /judge alone shows the status. - In the terminal it applies the next time you come in: /exit and open lampson again.
.env:
LAMPSON_JUDGE=jev # jev | laya | off
TYPESAFE_API_KEY=… # Jev's key
LAMPSON_JUDGE_MODEL=… # with laya: the checkpoint folder; with jev: a pinned model (optional)
The API key is stored in ~/lampson/.lampson/config.json with your other keys and never goes back to the browser.
Why it needs a restart§
Synsema's engine reads the judge provider when the process starts. That is why the web UI restarts the workspace when you save, and the terminal asks you to leave and come back. /judge and the ⚙ section tell you when it is configured but the running session does not have it yet.