OpenAI: value can now return "gpt-6-rosalind"

OpenAI's published API specification now lists "gpt-6-rosalind" as a possible value on the BetaModelIdsResponses and ModelIdsResponses enums, reachable from 4 OpenAI operations. The addition is producer-side additive but breaks exhaustive switches, strict parsers and generated client enums that lack a branch for the new value, which now sits alongside existing entries such as "gpt-5.6-cyber" and "gpt-rosalind-research".

What changed Producer-side tools call this additive. It breaks exhaustive switches, strict parsers and generated client enums. Affects this value on BetaModelIdsResponses reachable from 4 operations. New value: gpt-6-rosalind . can now return "gpt-6-rosalind" Who is affected Code that reads OpenAI's BetaModelIdsResponses objects, used by 4 OpenAI operations. Before and after | Where | Before | After | |---|---|---| | BetaModelIdsResponses | "computer-use-preview", "computer-use-preview-2025-03-11", "gpt-5-codex", "gpt-5-pro", "gpt-5-pro-2025-10-06", "gpt-5.1-codex-max", "gpt-5.5-pro", "gpt-5.5-pro-2026-04-23", "gpt-5.6-cyber", "gpt-daybreak-blue-latest", "gpt-daybreak-red-latest", "gpt-rosalind-research", "o1-pro", "o1-pro-2025-03-19", "o3-deep-research", "o3-deep-research-2025-06-26", "o3-pro", "o3-pro-2025-06-10", "o4-mini-deep-research", "o4-mini-deep-research-2025-06-26" | "computer-use-preview", "computer-use-preview-2025-03-11", "gpt-5-codex", "gpt-5-pro", "gpt-5-pro-2025-10-06", "gpt-5.1-codex-max", "gpt-5.5-pro", "gpt-5.5-pro-2026-04-23", "gpt-5.6-cyber", "gpt-6-rosalind", "gpt-daybreak-blue-latest", "gpt-daybreak-red-latest", "gpt-rosalind-research", "o1-pro", "o1-pro-2025-03-19", "o3-deep-research", "o3-deep-research-2025-06-26", "o3-pro", "o3-pro-2025-06-10", "o4-mini-deep-research", "o4-mini-deep-research-2025-06-26" | | ModelIdsResponses | "computer-use-preview", "computer-use-preview-2025-03-11", "gpt-5-codex", "gpt-5-pro", "gpt-5-pro-2025-10-06", "gpt-5.1-codex-max", "gpt-5.5-pro", "gpt-5.5-pro-2026-04-23", "gpt-5.6-cyber", "gpt-daybreak-blue-latest", "gpt-daybreak-red-latest", "gpt-rosalind-research", "o1-pro", "o1-pro-2025-03-19", "o3-deep-research", "o3-deep-research-2025-06-26", "o3-pro", "o3-pro-2025-06-10", "o4-mini-deep-research", "o4-mini-deep-research-2025-06-26" | "computer-use-preview", "computer-use-preview-2025-03-11", "gpt-5-codex", "gpt-5-pro", "gpt-5-pro-2025-10-06", "gpt-5.1-codex-max", "gpt-5.5-pro", "gpt-5.5-pro-2026-04-23", "gpt-5.6-cyber", "gpt-6-rosalind", "gpt-daybreak-blue-latest", "gpt-daybreak-red-latest", "gpt-rosalind-research", "o1-pro", "o1-pro-2025-03-19", "o3-deep-research", "o3-deep-research-2025-06-26", "o3-pro", "o3-pro-2025-06-10", "o4-mini-deep-research", "o4-mini-deep-research-2025-06-26" | Code that breaks switch response { // existing branches … // no branch for "gpt-6-rosalind" default: throw new Error "unexpected value" ; } Based on OpenAI’s published API specification. How severity is decided https://driftwatch.et/method .