Mozilla filed a standards-position opposing Chrome’s Prompt API after Blink published an intent-to-prototype, citing structural concerns with the spec.
Key Takeaways
The Prompt API is a proposed browser-native interface for querying language models, authored by @domenic and tracked under the WebMachinelearning WICG group.
Blink’s intent-to-prototype triggered Mozilla’s formal opposition via the mozilla/standards-positions repo.
Mozilla’s core objections: prompts are too tightly coupled to specific models, and model-neutrality is not enforced in the terms of use.
No WebKit standards position has been filed, leaving the proposal without multi-engine support required for standardization.
Hacker News Comment Review
Commenters largely support Mozilla’s stance; the tight prompt-to-model coupling is seen as a real engineering problem, not just a political objection, with a concrete system-prompt locale example cited.
Debate exists over whether browser-native LLM access is desirable at all; skeptics question the premise that browsers and OSes are “increasingly expected” to embed language models.
WebLLM via WebGPU is flagged as a working alternative that already ships more capability than the Prompt API would provide, suggesting the spec may be solving a problem that the ecosystem is routing around.
Notable Comments
@jaffathecake: Posted the issue and notes the key content is in the latest comment on the GitHub thread, not the issue opener.
@ilaksh: Points to WebLLM (mlc-ai/web-llm) over WebGPU as a more capable drop-in that bypasses the stalled spec.
