Catalog / LLM routing & guardrails
Akihito Koriyama's Semantic Browser follows HAL _links by what ALPS says they mean. Laya-MLX returns a probability per link and the browser takes the winner.
Independent Jev vs Laya measurements plus a cascade: Laya decides first, high confidence executes, low confidence escalates to Jev. At a 0.60 threshold it matched Jev's 78%.
@yibie · LLM routing & guardrails · lower than pure Jev
@yibie
GitHub
LLM routing & guardrails
lower than pure Jev
-
A port of the jev-ultrafast browser agent that decides with laya-mlx instead of the hosted Jev API. DOM snapshot, executor, safety checks and inspector are the originals.
@ipenywis · LLM routing & guardrails · free, local
@ipenywis
GitHub
LLM routing & guardrails
free, local
-
Two routers behind one endpoint, measured on 180 labelled requests. Laya answers small/medium/powerful routing in one forward pass, against a GPT-5 nano router.
@glukicov · LLM routing & guardrails · free, local
@glukicov
GitHub
LLM routing & guardrails
free, local
-
Local decider for the browser-agent loop: hand it a numbered table of page controls and it picks the operation and element. Playwright/CDP driver, speaks /v1/systemone.
@ChenneyZhuang · LLM routing & guardrails · free, local, no screenshots
@ChenneyZhuang
GitHub
LLM routing & guardrails
free, local, no screenshots
-
Built a hypermedia browser on Laya-MLX — a small model that, like Jev, doesn’t generate text; it just returns a probability for each option you give it. The next link is chosen from HAL’s _links and what ALPS declares those links mean. No routes defined up front. cc/ @mamund
Semantic Browser — PoC Stage 1 github.com/koriym/semanti… Browses hyperlinks by what they mean, not by routes — and measures whether an application declares enough for that to be possible.