Skip to content

Add constraints and future outlook for speed preference #103

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jaewon078 wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Add constraints and future outlook for speed preference #103

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
15aa9c6
Add constraints and future outlook for speed preference
jaewon078 May 4, 2026
3ee855e
address offline comments
jaewon078 May 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions explainers/summarizer-preference-param.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,14 @@ dictionary SummarizerCreateCoreOptions {
* **`"speed"`:** The implementation SHOULD prioritize low latency and fast execution. This approach prioritizes performance, which may limit the summarization capability, potentially resulting in less nuanced extraction or simpler synthesis of the source text.
* **`"capability"`:** The implementation SHOULD prioritize the comprehensiveness and coherence of the summarization, and a model that offers more flexibility in terms of summary types and other configurable options. This approach focuses on accurately capturing subtle context and producing highly refined summaries, which may result in higher latency and slower execution speeds.

> [!NOTE]
> **Implementation Note (Non-Normative):** The following constraints apply specifically to **Chrome's current implementation** of the `"speed"` preference and are not part of the API specification itself:
> * **Language:** `en` (English)
> * **Output Format:** `"plain-text"`
> * **Output Type:** `"tldr"` or `"key-points"`
> * **Output Length:** `"short"` or `"medium"`
> These constraints represent initial implementation limitations in Chrome. It is anticipated that future iterations will expand support to a wider range of options as optimized models evolve.

## Conflicting Constraints and Routing Fallbacks
The preference parameter acts as a strong hint to the implementation, rather than a strict guarantee. In scenarios where a developer's performance preference conflicts with a hard functional requirement, the implementation MUST prioritize the functional requirement.

Expand Down
Loading