Skip to content

feat: add gpt-5.5 and gpt-5.5-pro to static model registry#412

Open
maxnoller wants to merge 3 commits intomainfrom
feat/gpt-5.5-support
Open

feat: add gpt-5.5 and gpt-5.5-pro to static model registry#412
maxnoller wants to merge 3 commits intomainfrom
feat/gpt-5.5-support

Conversation

@maxnoller
Copy link
Copy Markdown
Member

Summary

  • Register gpt-5.5 and gpt-5.5-pro (OpenAI's GPT-5.5 family, released 2026-04-23) in STATIC_VISION_CAPABLE_MODELS and STATIC_MODEL_CONTEXT_WINDOWS.
  • Context windows set to 1,000,000 tokens per the GPT-5.5 API docs; both models are vision-capable like the rest of the gpt-5 family.
  • Also register gpt-5.5-chat-latest at 128k to mirror the existing gpt-5.{N}-chat-latest entries.

This lets HybridAI resolve the new model IDs (e.g. hybridai/gpt-5.5) without a discovery round-trip and correctly flag them as multimodal. No default model change.

Test plan

  • npx vitest run tests/hybridai-models.test.ts (8/8 passing, including new gpt-5.5 cases)
  • npx biome check clean on touched files
  • Pre-existing tsc errors in src/observability/otel.ts from missing optional @opentelemetry/* dev deps are unrelated to this change (reproduce on main).

Register the OpenAI GPT-5.5 family (released 2026-04-23) so HybridAI
can resolve their context windows and vision capability without a
discovery round-trip. Both models report a 1M token context window
per OpenAI's release notes.
GPT-5.5 also rolled out to Codex on 2026-04-23. Register it as a
forward-compat entry templated on gpt-5.4 / gpt-5.3-codex so existing
Codex users pick it up automatically, and seed it into the default
codex model list for fresh installs.
Forward-compat now appends openai-codex/gpt-5.5 whenever gpt-5.4 (or
another template) is in the discovered set, so the existing exact-list
and modelCount assertions need to reflect the extra entry.
@maxnoller maxnoller requested a review from furukama April 26, 2026 18:04
Copy link
Copy Markdown
Contributor

@furukama furukama left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please fix merge conflicts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants