anomalyco / anomalyco/models.dev

GitHub Copilot Business gpt-5.5 context differs from models.dev

Open
#2,033 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
6.9k
Forks
1.7k
Avg merge
3h 21m
Merged PRs (30d)
873

Description

Description

I noticed a context limit mismatch for github-copilot/gpt-5.5.

The local models.dev-derived cache used by OpenCode shows:

github-copilot/gpt-5.5
limit.context: 400000
limit.input: 272000
limit.output: 128000

But the live GitHub Copilot models endpoint for my account reports:

GET https://api.githubcopilot.com/models
model: gpt-5.5
max_context_window_tokens: 1050000
max_prompt_tokens: 922000
max_output_tokens: 128000
Account / plan context

This is from a GitHub Copilot Business account, not a personal Copilot account.

So this may be plan/account dependent rather than a universal Copilot limit.

Why I noticed

OpenCode TUI showed the session at around 10% used, which matched the live 1050000 context value.

However, reading the local models cache made it look like the same session was much fuller because models.json listed 400000 for the same model.

Related OpenCode issue

I also filed the OpenCode-side observability issue here:

https://github.com/anomalyco/opencode/issues/31064

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.

Research direction

Start by comparing the models.dev-derived cache entry with the live GET https://api.githubcopilot.com/models response for gpt-5.5, keeping the GitHub Copilot Business account context in mind. Determine whether the data should represent plan-specific limits or a documented canonical value, then verify that the resulting model metadata no longer creates the reported context mismatch.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
data
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.