Proposal for navigator.models browser API to run local open-weight models
Start here
A WICG proposal called navigator.models would let web apps request a specific open-weight model ID and run it on-device in the browser, with no silent fallback to a different model. The API covers generate(), stream() and embed(), and the browser asks users to grant or revoke access per site and per model while sharing weights across sites. Access is tightly scoped: the first request must start with a user gesture, a grant applies to one top-level site, one requesting frame origin and one model ID, and a site can detect the API but cannot list the models on a device. Shared catalogs, model retirement and cross-browser compatibility tests remain open questions; the proposal is open for comments.
Generated from reports · updated 12 h ago
Report timeline
Follow the reports to see the event from different sides.
- Hacker News · AInavigator.models: A Proposed Browser API for Running Local Open-Weight Models
A proposal called navigator.models would let web apps request a specific open-weight model ID and run it on-device in the browser, with no silent fallback to a different model. The API covers generate(), stream() and embed(), and the browser asks users to grant or revoke per-site, per-model access while sharing weights across sites. Shared catalogs, model retirement and cross-browser compatibility tests remain open questions.
Heat for this event
- Current, comparable range
- 7
- Peak, comparable range
- 10November 16 05:00
- Change in 24 hours
- –
The trend compares the same participants over hours observed continuously, so its range can be narrower than the current heat count. Hover or tap the chart for hourly heat; the arrow keys move through it.