Track GPT-5.6 model metadata and defaults readiness

[cbusillo]

Objective

Track GPT-5.6 availability and update Every Code static model defaults, routing, metadata, tests, and docs once official/backend model IDs and capabilities are available.

Current Status

State: Waiting
Next action: When the Codex backend /models endpoint lists gpt-5.6 or official OpenAI sources confirm exact model IDs/capabilities, update the static defaults/routing/docs that intentionally do not move from backend discovery alone.
Blocked by: No native issue blocker; waiting for GPT-5.6 to appear in backend or official model sources.
Waiting for: Codex backend /models entry and/or official OpenAI model docs/news for GPT-5.6.
Last verified: 2026-05-29. The live Codex backend model list did not include gpt-5.6; it listed codex-auto-review, gpt-5.2, gpt-5.3-codex, gpt-5.3-codex-spark, gpt-5.4, and gpt-5.4-mini.

Scope

• Check official OpenAI model docs/news and the Codex backend /models listing.
• Identify exact model IDs, aliases, capabilities, token limits, reasoning settings, priority, visibility, and recommended defaults.
• Update Every Code static defaults and routing where appropriate, including model defaults, review defaults, Auto Drive routing, docs, and tests.
• Preserve compatibility with existing GPT-5.x defaults and aliases during transition.

Acceptance Criteria

• GPT-5.6 availability and model IDs are confirmed from the Codex backend or primary official sources.
• Every Code static defaults/routing are updated where appropriate for confirmed GPT-5.6 models.
• Docs and release notes describe GPT-5.6 only after confirmed availability.
• Focused tests or metadata checks cover new entries/aliases/default behavior.
• ./build-fast.sh passes on the implementation PR.

Relationships

Related to #177 for Claude Opus 4.8 model metadata refresh work.
Related to #205, which added regression coverage that newly listed backend GPT models can appear and be prioritized without a new local preset.
Related to #124 for upstream changes that may already carry model metadata updates.

Notes

Do not add speculative GPT-5.6 IDs or aliases. Every Code can already surface newly listed backend models through remote model discovery when the backend marks them visible. This issue is for the static follow-up work that still requires an intentional release: defaults, routing, docs, release notes, and any new metadata semantics.

[cbusillo]

Verification update (2026-05-29): checked official OpenAI model docs, ChatGPT release notes, and OpenAI recent news. I did not find an official GPT-5.6 model ID or release note yet. Current official model docs still say to start with gpt-5.5 for complex reasoning/coding, and the latest ChatGPT release notes mention a GPT-5.5 Instant update rather than GPT-5.6.\n\nDecision: keep Every Code defaulting to gpt-5.5; do not add speculative GPT-5.6 IDs or aliases until official release evidence exists.\n\nSources checked:\n- https://developers.openai.com/api/docs/models\n- https://help.openai.com/en/articles/6825453-chatgpt-release-notes\n- https://openai.com/news/company-announcements/