Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

BYOK model limits catalog is missing gpt-5.5

Closed Beginner friendly
#3,118 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
shell
Domain
ai, cli

Research direction

Locate the built-in BYOK model limits catalog and its lookup, then compare the nearby gpt-5.4, gpt-5.4-mini, and gpt-5.4-nano entries. Re-run the provided Copilot CLI reproduction without manual token overrides; done when gpt-5.5 resolves catalog limits without the fallback warning.

Written by the indexing model from the issue text.

Description

area:configuration area:models
Describe the bug

When using BYOK / a custom OpenAI-compatible provider with gpt-5.5, Copilot CLI treats the model as missing from the built-in limits catalog and falls back to default token limits.

This appears to be a catalog mismatch: gpt-5.5 can be listed/used by the provider, but the BYOK limits catalog does not include an entry for it. As a result, context/compaction uses a much smaller default prompt budget unless users manually set COPILOT_PROVIDER_MAX_PROMPT_TOKENS and COPILOT_PROVIDER_MAX_OUTPUT_TOKENS.

Affected version

GitHub Copilot CLI 1.0.40

Steps to reproduce the behavior

Use an OpenAI-compatible BYOK provider that exposes gpt-5.5, then run Copilot CLI with the model selected but without manual token limit overrides:

export COPILOT_PROVIDER_TYPE=openai
export COPILOT_PROVIDER_BASE_URL=<redacted>/v1
export COPILOT_PROVIDER_API_KEY=<redacted>
export COPILOT_PROVIDER_MODEL_ID=gpt-5.5
export COPILOT_PROVIDER_WIRE_API=responses
unset COPILOT_PROVIDER_MAX_PROMPT_TOKENS
unset COPILOT_PROVIDER_MAX_OUTPUT_TOKENS

copilot --log-level debug -p 'Reply with exactly OK and nothing else.'

Observed debug log excerpts:

[WARNING] Model "gpt-5.5" is not in the built-in catalog. Using defaults for: prompt tokens (COPILOT_PROVIDER_MAX_PROMPT_TOKENS), output tokens (COPILOT_PROVIDER_MAX_OUTPUT_TOKENS). Run `copilot help providers` for configuration details.
[INFO] Using custom provider: type=openai, wireApi=responses
[DEBUG] Using model: gpt-5.5
[DEBUG] Listed models: [gpt-5.5,gpt-5.5]
"max_prompt_tokens": 128000,
"max_context_window_tokens": 200000,
CompactionProcessor: Utilization 15.4% (19674/128000 tokens) below threshold 80%

If manual overrides are provided, they do take effect:

export COPILOT_PROVIDER_MAX_PROMPT_TOKENS=400000
export COPILOT_PROVIDER_MAX_OUTPUT_TOKENS=128000

Then the compaction log uses the manual prompt limit:

CompactionProcessor: Utilization 4.9% (19666/400000 tokens) below threshold 80%
Expected behavior

gpt-5.5 should either:

  1. be included in the BYOK built-in model limits catalog with appropriate prompt/context/output limits, or
  2. have a documented way to inherit/resolve limits for this model without falling back to the generic defaults.
Actual behavior

gpt-5.5 is usable from the provider model list, but the BYOK model limits lookup misses it and falls back to defaults:

max_prompt_tokens: 128000
max_context_window_tokens: 200000
Additional context

The nearby GPT-5.x entries in the BYOK catalog appear to include models such as gpt-5.4, gpt-5.4-mini, and gpt-5.4-nano with larger limits. The issue seems specific to gpt-5.5 being absent from the built-in BYOK limits catalog.

Dominant language
Shell
Stars
11.2k
Forks
1.9k
Avg merge
14h 16m
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

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.

More from github/copilot-cli

All issues in github/copilot-cli

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.