v157 · built-in ai · intent routing
Semantic-If command router
The explainer's second use case, built: a command palette that should understand “let my coworkers view this file” means share_link even though no keyword matches. The route button attempts the real three-step workflow — availability(), create(), decide() — and renders real probabilities when a model answers. When none exists, you get the honest absence, plus a look at why the pre-API workaround is not good enough.
No released Chrome exposes window.DecisionModel yet (implementation CLs in review — see the surface probe for the exact flag steps once a build carries them). The WebAI extension polyfill provides the same surface today and this page will drive it for real if installed. Nothing below ever shows model output that did not come from a model.
Route a goal
Try phrasings with no overlapping keywords: “get this to legal as a document”, “bin it”, “who else can see this?”.
The pre-API workaround (labelled as such — this is NOT DecisionModel output)
A keyword matcher is what sites ship today: fast and local, but it scores “let my coworkers view this file” as zero for every command above, and one typo kills an exact match. That gap — not this matcher — is the argument for the API.
The exact schema this page sends
acting on confidence
The result is not just a winner: every option gets a calibrated probability and the question a confidence. The explainer's guidance, which this page applies when a model answers: act automatically above a threshold (here 0.85), offer suggestion chips when uncertain, and never treat confidence as authorization for a destructive action — archive_doc here would still confirm with the user at any confidence. A WebMCP-style agent could use the same schema to pick page tools; that composition needs an agent host, so this page stops at the routing decision itself.