MicrosoftEdge / MicrosoftEdge/MSEdgeExplainers

[Prompt API] Restricting the Phi-4-mini-instruct model to a 9216 token context window makes no sense given the hardware required to run it.

Open
#1,224 1 comment 0 reactions 1 assignee View on GitHub

@sohchatt is already working on this.

Since Jan 8, 2026.

Prompt API
Dominant language
HTML
Stars
1.4k
Forks
286
Avg merge
3d 1h
Merged PRs (30d)
8

Description

In the current Prompt API implementation in the Chrome Dev and Edge Dev browser versions, the context window is restricted in both to a fixed 9216 tokens. I can understand why this is harmonized between browsers but Gemini Nano can run on much less capable hardware (just 16GB of RAM) whereas Phi-4-mini-instruct requires quite powerful hardware (5.5GB VRAM, essentially a mid-range gaming PC). So we're saying: ' Edge must run on very capable hardware but at the same time we're handicapping the Edge model so it's no better than the Chrome model'. In my specific use case I want Phi-4-mini to be able to analyze movie screenplays in Fountain format. Any feature screenplay will be at least 80 pages but 9216 tokens accommodates only 20 to perhaps 30 pages at best - a fairly short movie , yet Microsoft documents the incredibly useful 128K context window its model could offer.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.