diff --git a/codex-rs/skills/src/assets/samples/openai-docs/references/latest-model.md b/codex-rs/skills/src/assets/samples/openai-docs/references/latest-model.md index d4fca8c4f0..fd065f5e2f 100644 --- a/codex-rs/skills/src/assets/samples/openai-docs/references/latest-model.md +++ b/codex-rs/skills/src/assets/samples/openai-docs/references/latest-model.md @@ -2,24 +2,14 @@ This is a compact, non-authoritative fallback, not a source for current availability, prices, aliases, or defaults. First search for and fetch current official model guidance at `https://developers.openai.com/api/docs/guides/latest-model` and the relevant official model page. The fetched official documentation wins if this snapshot has drifted. Disclose any use of this fallback. -## Model roles +## Source model descriptions -| Model ID | Documented workload to verify against the current model page | +| Model ID | Official source description | | --- | --- | -| `gpt-6` | GPT-6 family alias; verify its currently documented routing and availability. | -| `gpt-6-astra` | Quality-first flagship, reasoning, and difficult coding work. | -| `gpt-5.6-terra` | Balanced quality, latency, and cost. | -| `gpt-5.6-luna` | Primary choice for faster or cheaper workloads. | +| `gpt-6-astra` | For the most demanding reasoning, coding, and professional work. | +| `gpt-6.1-sol` | Near-Astra performance for complex work at a lower cost. | +| `gpt-6-luna` | Strong performance for focused, high-volume tasks. | Use `https://developers.openai.com/api/docs/guides/latest-model/gpt-6-astra.md#migration-quickstart` for an actual GPT-6 migration and `https://developers.openai.com/api/docs/guides/latest-model/gpt-6-astra.md#prompting-best-practices` for requested GPT-6 prompting. Open and read the relevant page before recommending a request shape, reasoning setting, endpoint, tool behavior, or migration. -## Explicitly requested existing models - -| Model ID | Boundary | -| --- | --- | -| `gpt-4.1` | Preserve only when the user explicitly requests this model or existing migration target; search and fetch its own current official guide. | -| `gpt-5.4` | Preserve only when the user explicitly requests this model or existing migration target; search and fetch its own current official guide. | - -Do not promote a legacy model as the current default, substitute it into an unrelated task, or replace an explicitly requested legacy target with GPT-6 Astra. Recommend a specialized image, audio, realtime, coding, moderation, or embedding model only after verifying the requested modality against current official documentation. - Verify GPT-6 Pro against current official Responses and model documentation before describing model IDs, reasoning modes, request parameters, or account availability; do not invent a separate `gpt-6-pro` model slug. diff --git a/codex-rs/skills/src/assets/samples/openai-docs/references/model-migration.md b/codex-rs/skills/src/assets/samples/openai-docs/references/model-migration.md index 934c5c1ec3..9144e35dbe 100644 --- a/codex-rs/skills/src/assets/samples/openai-docs/references/model-migration.md +++ b/codex-rs/skills/src/assets/samples/openai-docs/references/model-migration.md @@ -33,6 +33,7 @@ Treat returned guide URLs as opaque: fetch those exact URLs without deriving, su - Fetch `promptingGuideUrl` only when the user asks for prompting guidance or the migration requires a prompt change. Extract only `## Prompting best practices` through the next H2 heading. - For explicitly named-model prompting, fetch that model's official prompting guidance and extract only `## Prompting best practices` through the next H2 heading. Do not load a migration reference or run the resolver. - For an actual GPT-6 migration or implementation plan, fetch `https://developers.openai.com/api/docs/guides/latest-model/gpt-6-astra.md#migration-quickstart`. For specifically requested GPT-6 prompting, fetch `https://developers.openai.com/api/docs/guides/latest-model/gpt-6-astra.md#prompting-best-practices`. Read `references/upgrading-to-gpt-6-astra.md` only when fetched official guidance does not resolve needed compatibility gates, scoped code changes, tier-aware routing, validation, or other migration-specific judgment. Never load it for documentation-only questions about model tiers, the family alias, Pro mode, reasoning effort, or current guidance when the fetched official documentation already answers them. +- Verify current official guidance and account availability before recommending or selecting a model. Preserve the selected model and apply its own compatibility rules; do not copy a sibling's reasoning defaults, tool support, or regional availability. A newer family member does not change the model returned by the latest-model resolver. For an explicitly requested model whose public guidance is not yet available, keep the requested target and state the unresolved compatibility facts instead of silently substituting another model. - Read `references/prompting-guide.md` only when prompting guidance or prompt changes are actually needed and current official guidance is unavailable. - Read `references/upgrade-guide.md` only when current official migration guidance is unavailable. Disclose when a bundled fallback was used. diff --git a/codex-rs/skills/src/assets/samples/openai-docs/references/prompting-guide.md b/codex-rs/skills/src/assets/samples/openai-docs/references/prompting-guide.md index 2370a8a1ab..b6430d0d49 100644 --- a/codex-rs/skills/src/assets/samples/openai-docs/references/prompting-guide.md +++ b/codex-rs/skills/src/assets/samples/openai-docs/references/prompting-guide.md @@ -10,15 +10,15 @@ Treat the live section as the canonical model-specific prompting guidance. Use t ## Prompting best practices -GPT-6 Astra is more intelligent and capable than prior models like GPT-5.6 Sol, and also exhibits behavior patterns that can be optimized through prompting the model for your use case. +Use the following prompts as a starting point across the GPT-6 model family. They address behavior observed with GPT-6 Astra; evaluate them with your chosen model and workload. ### GPT-6 Astra behavior -- [Initiative and follow-through](#initiative-and-follow-through) – The model is designed to be a more effective collaborator and is thus more likely to ask the user a question when additional input could materially change the result. This can cause it to stop when the user may expect it to make reasonable assumptions and persist. -- [Instruction following](#instruction-following) – GPT-6 Astra is stronger at general instruction following than our previous models, giving you greater control over its behavior. It can be more sensitive to instructions contained in skills and other files, such as `AGENTS.md`. We **strongly recommend** auditing skills and other files accessible to your model for instructions that could influence its behavior. -- [Personality and writing style](#personality-and-writing-style) – The model tends toward detailed, formatted responses and may use recurring phrases across sessions. Specify the writing style and structure your application needs. -- [Subagent delegation](#subagent-delegation) – The model may delegate less often than desired for your workflow. Specify when and how much it should use subagents for parallel work. -- [Testing and verification](#testing-and-verification) – For coding tasks, the model tends to be thorough in testing before considering a task complete. For smaller tasks, this can result in broader tests than the task requires. +- [Initiative and follow-through](#initiative-and-follow-through): The model is designed to be a more effective collaborator and is thus more likely to ask the user a question when additional input could materially change the result. This can cause it to stop when the user may expect it to make reasonable assumptions and persist. +- [Instruction following](#instruction-following): GPT-6 Astra is stronger at general instruction following than our previous models, giving you greater control over its behavior. It can be more sensitive to instructions contained in skills and other files, such as `AGENTS.md`. We **strongly recommend** auditing skills and other files accessible to your model for instructions that could influence its behavior. +- [Personality and writing style](#personality-and-writing-style): The model tends toward detailed, formatted responses and may use recurring phrases across sessions. Specify the writing style and structure your application needs. +- [Subagent delegation](#subagent-delegation): The model may delegate less often than desired for your workflow. Specify when and how much it should use subagents for parallel work. +- [Testing and verification](#testing-and-verification): For coding tasks, the model tends to be thorough in testing before considering a task complete. For smaller tasks, this can result in broader tests than the task requires. ### Initiative and follow-through @@ -85,7 +85,7 @@ To reduce jargon and stock phrases in writing, start with this prompt: ```text Avoid using slop words or phrases like "Bottom Line:" in conclusions, "delve," "foster," "leverage," "it's worth noting," "importantly," "Question? Answer." or "This isn't about X. It's about Y.", "genuinely" or hyphenated compound descriptions and adjectives. Do not use concluding summary statements such as "In short:..", "The simplest mental model is:...". -State the intended action directly. Avoid adding what you won't do, what will remain unchanged, or how you'll separate or categorize results. Do not use contrastive framing such as "X, not Y" or "X—not Y" that introduces an unprompted alternative that the user didn't ask about. Avoid invented compound labels like "exact-head checks" and "editorial-row layouts", vague qualifiers, and canned transitions; use plain verbs and prepositions to state the actual relationship directly. +State the intended action directly. Avoid adding what you won't do, what will remain unchanged, or how you'll separate or categorize results. Do not use contrastive framing such as "X, not Y" that introduces an unprompted alternative that the user didn't ask about. Avoid invented compound labels like "exact-head checks" and "editorial-row layouts", vague qualifiers, and canned transitions; use plain verbs and prepositions to state the actual relationship directly. ``` ### Subagent delegation diff --git a/codex-rs/skills/src/assets/samples/openai-docs/references/upgrade-guide.md b/codex-rs/skills/src/assets/samples/openai-docs/references/upgrade-guide.md index c367ee4d52..4879ab724f 100644 --- a/codex-rs/skills/src/assets/samples/openai-docs/references/upgrade-guide.md +++ b/codex-rs/skills/src/assets/samples/openai-docs/references/upgrade-guide.md @@ -4,19 +4,20 @@ Use this file only as a bundled routing fallback when the live migration guide c For latest, current, default, or unspecified-model upgrades: -1. Run `scripts/resolve-latest-model-info`. -2. Fetch the returned `migrationGuideUrl` and `promptingGuideUrl` exactly. +1. Follow the platform-specific resolver instructions in `references/model-migration.md`. +2. Fetch the returned `migrationGuideUrl` exactly; fetch `promptingGuideUrl` only when prompting guidance or prompt changes are needed. 3. Treat the live guides as canonical. 4. If remote retrieval fails, disclose that bundled fallback guidance is being used. -For an explicit GPT-6 Astra migration: +For an explicitly requested GPT-6 model: 1. Preserve the user's explicit target; do not run the latest-model resolver. 2. Fetch the live GPT-6 model guidance: https://developers.openai.com/api/docs/guides/latest-model/gpt-6-astra.md -3. Read `references/upgrading-to-gpt-6-astra.md` for skill-specific migration judgment. -4. Read `references/prompting-guide.md` only when prompt changes are needed. +3. Verify the exact target's current official model page and compatibility rules; family examples do not establish support for every sibling. If availability or compatibility cannot be verified, preserve the requested target and report the blocker instead of substituting a model or implementing an unverified migration. +4. Read `references/upgrading-to-gpt-6-astra.md` only for unresolved skill-specific migration judgment. +5. Read `references/prompting-guide.md` only when prompt changes are needed. -For another explicit model target, preserve that target and fetch its current official guidance. Do not reuse GPT-6-specific defaults, API shapes, or compatibility rules for a different model. +For another explicit model target, preserve that target and fetch its current official guidance. Do not reuse another model's defaults, API shapes, or compatibility rules, including Astra-only restrictions for Sol or Luna. diff --git a/codex-rs/skills/src/assets/samples/openai-docs/references/upgrading-to-gpt-6-astra.md b/codex-rs/skills/src/assets/samples/openai-docs/references/upgrading-to-gpt-6-astra.md index 49d138ee29..a61f582e7d 100644 --- a/codex-rs/skills/src/assets/samples/openai-docs/references/upgrading-to-gpt-6-astra.md +++ b/codex-rs/skills/src/assets/samples/openai-docs/references/upgrading-to-gpt-6-astra.md @@ -1,8 +1,8 @@ -# Upgrading to GPT-6 Astra +# Upgrading to the GPT-6 model family -Use this guide when the user asks to migrate an existing OpenAI API integration, repository, prompt stack, agent, model router, or model picker to GPT-6 Astra. +Use this guide when the user asks to migrate an existing OpenAI API integration, repository, prompt stack, agent, model router, or model picker to GPT-6 Astra, GPT-6.1 Sol, GPT-6 Sol, or GPT-6 Luna after verifying the target's availability. -The default explicit target is `gpt-6-astra`. Verify the `gpt-6` family alias's currently documented routing and availability before using it. Do not treat every old model usage as an Astra candidate: retain Terra for balanced work and Luna as the primary faster or cheaper model. +Preserve an explicitly requested target. For an unspecified target, use the live model-selection or migration guidance rather than assuming every workload should use Astra. Before changing code, retrieve the current live GPT-6 model guidance using already-callable official documentation search and fetch, or immediately use official-domain web search and fetch: @@ -12,7 +12,9 @@ For prompt changes, also read only the `## Prompting best practices` section fro https://developers.openai.com/api/docs/guides/latest-model/gpt-6-astra.md#prompting-best-practices -Treat live docs as canonical for current model IDs, parameters, limits, pricing, and feature availability. The skill-specific workflow below covers repository inspection, scope preservation, and validation. The fallback after it includes all non-prompting guidance, including access notices, examples, caveats, and `## Migration quickstart`; the full prompting section is in `references/prompting-guide.md`. When refreshing, preserve all guide content unless it is specific to the website rather than useful to the skill, and record any omission. Remove website metadata and component markup while retaining their readable content. Resolve site-relative links against `https://developers.openai.com` and section-only links against the canonical model-guide URL above. +Treat live docs as canonical for current model IDs, parameters, limits, pricing, and feature availability. The skill-specific workflow below covers repository inspection, scope preservation, and validation. The fallback after it includes all non-prompting guidance, including access notices, examples, caveats, and `## Migration quickstart`; the full prompting section is in `references/prompting-guide.md`. When refreshing, preserve all guide content unless it is specific to the website rather than useful to the skill, and record any omission. Remove website metadata and component markup while retaining their readable content. Resolve site-relative links against `https://developers.openai.com`. Keep section-only links as local fragments when their intended target exists in the same reference file; use canonical absolute URLs for cross-document or absent targets and explicit fetch/source instructions. + +Verify the exact model, endpoint, service tier, and region; if support is unverified, report the unresolved requirement rather than infer support. ## Core principle @@ -20,7 +22,7 @@ Do not perform a blind model-string replacement. First preserve the behavior, latency class, cost class, reasoning level, endpoint contract, tool semantics, cache behavior, and output contract of each usage site. Then make the smallest safe migration. Adopt new GPT-6 capabilities only when they solve a measured problem or the user explicitly asks for them. -A model upgrade alone does not authorize adding reasoning fields, changing request schemas, or rewriting tests. Set a supported reasoning effort explicitly to preserve the source model's effective behavior; verify omitted defaults rather than guessing. +Set a supported reasoning effort explicitly to preserve the source model's effective behavior; verify omitted defaults rather than guessing. ## Migration posture @@ -33,7 +35,7 @@ Classify every usage site before editing: - No cache, vision, file, tool, or parser behavior needs implementation changes. 2. `tier-aware family migration` - The repository exposes multiple model roles, model choices, fallbacks, routers, pricing data, or capability metadata. - - Map each role to Astra, Terra, or Luna instead of replacing everything with Astra. + - Map each role to a verified suitable target instead of replacing everything with Astra. 3. `compatibility migration` - The safe move requires parameter, endpoint, cache, state, tool-loop, or multimodal-detail changes. - Make these changes only when implementation work is inside the user's requested scope. Otherwise report the exact blocker and smallest follow-up. @@ -77,32 +79,6 @@ For each usage site, record: - downstream parsers or user-visible contracts; - migration class and validation plan. -## Choose the target model by role - -Use this as a starting map, then validate against the repository's workload: - -| Existing role | Starting target | Reason | -| --- | --- | --- | -| GPT-5.6 Sol or an earlier flagship | `gpt-6-astra` | Astra is the flagship-equivalent tier. | -| Balanced quality, latency, and cost | `gpt-5.6-terra` | Terra is the balanced option. | -| Faster or cheaper work, classification, extraction, routing, high-volume, or strict-latency route | `gpt-5.6-luna` | Luna is the primary speed and cost option. | -| GPT-4.1 or GPT-4o latency-sensitive flow | Start with Luna; evaluate Terra or Astra if quality requires it | A flagship replacement can change latency and cost materially. | -| Reasoning-heavy or hardest quality-first flow | Start with Astra at the old effective effort | Preserve the reasoning contract before tuning. | -| Router, fallback, or model picker | Add the family by role | Do not collapse a multi-model design into Astra. | -| Third-party or provider-specific model | Leave unchanged unless the user explicitly requests provider migration | Model-name similarity is not a safe mapping. | - -Important limits to check in live docs: - -- Each model's context window and maximum output. -- Long-context pricing thresholds for each route. -- Token pricing for GPT-6. - -Do not invent prices, limits, or capability flags. Fetch them from current docs before updating a registry or UI. - -For model pickers and registries, preserve existing model entries by default. Add GPT-6 Astra and retain the existing Terra and Luna options unless the user explicitly asks to replace or remove them. Do not invent pricing, context limits, capabilities, or metadata unless confirmed from canonical docs. - -If using the `gpt-6` alias, record the returned `response.model` during validation. Do not assume an alias and an explicit Astra slug appear identically in dashboards, rate-limit configuration, analytics, or billing metadata. - ## Structured outputs, parsers, and tool contracts Keep output contracts explicit: @@ -116,14 +92,14 @@ Do not fix a failing migration by weakening a schema, deleting required behavior ## Prompt migration judgment -After the model and API baseline is working, run representative traces before editing prompts. Change prompts only for measured failures. Read `references/prompting-guide.md` for the exact canonical prompting section when prompt changes are needed. +After the model and API baseline is working, run representative traces before editing prompts. Change prompts for measured failures, documented migration requirements, or an explicit user request. Read `references/prompting-guide.md` for the exact canonical prompting section when prompt changes are needed. ## Upgrade workflow 1. Fetch current live GPT-6 docs. Fetch the Prompting Best Practices section only when prompt changes are needed. 2. Inventory every usage site and its adjacent prompt, config, registry, parser, and test surfaces. 3. Classify each usage by role and migration class. -4. Choose Astra, Terra, or Luna by the existing workload's role. +4. Choose the verified available target by the existing workload's role. Do not infer model availability merely because it appears in this fallback. 5. Preserve the old effective reasoning effort explicitly when supported; follow the canonical migration guidance for unsupported settings. 6. Run the compatibility gates: - endpoint and SDK support; @@ -145,9 +121,8 @@ Prefer a controlled comparison: 1. old model + old prompt + old settings; 2. GPT-6 target + same prompt + preserved effective reasoning; -3. GPT-6 target + same prompt + one lower supported effort; -4. GPT-6 target + the smallest prompt or API fix required by a measured failure; -5. optional feature treatment, isolated from the baseline. +3. GPT-6 target + the smallest prompt or API fix required by a measured failure; +4. optional feature treatment, isolated from the baseline. Measure what matters for the workflow: @@ -161,14 +136,14 @@ Measure what matters for the workflow: - image/PDF token use and visual/OCR accuracy; - completeness, preserved behavior, citations, and validation evidence. -For model routers and pickers, test at least one representative workload for each role. Verify that the cheapest or fastest tier is not accidentally used for quality-critical work and that Astra is not accidentally used for every workload. +For model routers and pickers, test at least one representative workload for each intended role against its quality, latency, and cost requirements. ## Required final report Return: - `Current usage inventory`: each model site, endpoint, role, prompt surface, and old effective reasoning. -- `Target mapping`: Astra, Terra, Luna, unchanged, or confirmation-needed, with the reason. +- `Target mapping`: the exact requested or resolved model, unchanged, or confirmation-needed, with the reason and any availability or compatibility blocker. - `Changes made`: model strings, reasoning settings, prompts, registries, metadata, tests, and API-shape changes. - `Compatibility checks`: Chat Completions/tools, caching, state replay, multimodal detail, context/cost, schemas, and mixed-model routing. - `Prompt changes`: each surgical edit and the failure mode it addresses. @@ -178,44 +153,84 @@ Return: Never say the migration is complete merely because model strings changed. It is complete only when the affected behavior and contracts have been validated or the remaining gaps are stated explicitly. -## Introduction +Choose a GPT-6 model based on the reasoning your task requires, speed, and cost. -GPT-6 Astra is our most intelligent model yet, with state-of-the-art performance in computer use, browsing, software engineering, science, and professional work. It excels at carrying out multistep workflows across code, browsers, and professional software. In several evaluations, Astra achieves stronger results while using substantially fewer output tokens—delivering a lower estimated API cost per task than earlier models despite its higher per-token pricing. +- [GPT-6 Astra](https://developers.openai.com/api/docs/models/gpt-6-astra) + + **Highest intelligence** + + For the most demanding reasoning, coding, and professional work. + +- [GPT-6.1 Sol](https://developers.openai.com/api/docs/models/gpt-6.1-sol) + + **Balanced speed, cost, and intelligence** + + Near-Astra performance for complex work at a lower cost. + +- [GPT-6 Luna](https://developers.openai.com/api/docs/models/gpt-6-luna) + + **Fastest and most cost-effective** + + Strong performance for focused, high-volume tasks. + +To get started, set `model` in a [Responses API](https://developers.openai.com/api/docs/guides/migrate-to-responses) request. If you already use [`gpt-6-sol`](https://developers.openai.com/api/docs/models/gpt-6-sol), review the [migration guidance](#migration-quickstart) before switching to GPT-6.1 Sol. + +### GPT-6 Astra + +GPT-6 Astra is our most intelligent model yet, with state-of-the-art performance in computer use, browsing, software engineering, science, and professional work. It can carry out multi-step workflows across code, browsers, and professional software. In [several evaluations](https://openai.com/index/gpt-6-astra/), Astra achieved stronger results using substantially fewer output tokens. Its estimated API cost per task was lower than earlier models despite its higher per-token pricing. GPT-6 Astra is also our most aligned model yet. It excels at exercising care, respecting task boundaries, and communicating transparently. When instructions leave room for interpretation, it uses the context it has to fill in routine gaps and asks focused questions when the answer could change the outcome. It incorporates new requirements, changes course when asked, and answers side questions without losing track of the broader task. -To build with Astra, set `model` to `gpt-6-astra` in a [Responses API](https://developers.openai.com/api/docs/guides/migrate-to-responses) request. +All GPT-6 Astra users also have access to [Fast mode](https://developers.openai.com/api/docs/guides/fast-mode) and the new [Ultrafast mode](https://developers.openai.com/api/docs/guides/ultrafast-mode) for our fastest API speeds. + +### GPT-6.1 Sol + +Use GPT-6.1 Sol for complex coding, computer use, and professional work when you +want near-Astra performance at a lower cost. Compare it with Astra on your tasks +to assess the tradeoff between quality and cost. + +Set `reasoning.effort` to `low`, `medium` (default), `high`, `xhigh`, or `max`. +Use the Responses API for tool calling. Chat Completions supports requests +without tools. The `none` and `minimal` reasoning efforts are not supported. + +See the [model page](https://developers.openai.com/api/docs/models/gpt-6.1-sol) for specifications, +pricing, and availability, or [model selection](https://developers.openai.com/api/docs/guides/model-selection#when-to-consider-gpt-61-sol) +for guidance on choosing a model. ## What's new -- **Async tool calling:** GPT-6 Astra can continue reasoning, call other tools, or answer independent parts of a request while your application runs a tool. Set `async: true` on a function or custom tool and return its result when ready using the original `call_id`. Your application still executes the tool and manages pending work. See [Async tool calling](https://developers.openai.com/api/docs/guides/async-tool-calling) for basic usage and a developer-defined wait-tool pattern. -- **Mid-turn steering:** Send additional user instructions while GPT-6 Astra is working, such as a correction or a change in requirements. Over a WebSocket connection, the Responses API preserves completed work and includes the update in a continuation. See [Mid-turn steering](https://developers.openai.com/api/docs/guides/steering) for the event flow and tool-result handling. +- **Async tool calling:** GPT-6 can continue reasoning, call other tools, or answer independent parts of a request while your application runs a tool. Set `async: true` on a function or custom tool and return its result when ready using the original `call_id`. Your application still executes the tool and manages pending work. See [Async tool calling](https://developers.openai.com/api/docs/guides/async-tool-calling) for basic usage and a developer-defined wait-tool pattern. +- **Mid-turn steering:** Send additional user instructions while GPT-6 is working, such as a correction or a change in requirements. Over a WebSocket connection, the Responses API preserves completed work and includes the update in a continuation. See [Mid-turn steering](https://developers.openai.com/api/docs/guides/steering) for the event flow and tool-result handling. - **Change reasoning mid-conversation while preserving cache:** Add a `configuration_update` input item to increase reasoning effort for difficult work or reduce it for routine follow-ups without rewriting the original prompt prefix. The updated reasoning effort applies until another `configuration_update` input item overrides it. See [Change reasoning mid-conversation](https://developers.openai.com/api/docs/guides/reasoning#change-reasoning-mid-conversation) for examples and compatibility. -- **Misalignment monitoring:** As part of our strengthened safeguards for GPT-6 Astra, our systems asynchronously monitor for misalignment and trigger alerts when necessary. See [Misalignment monitoring](https://developers.openai.com/api/docs/guides/safety-checks/misalignment-monitoring) for more information. -- **Limitations:** GPT-6 Astra does not support the `none` reasoning effort. [Fast mode](https://developers.openai.com/api/docs/guides/fast-mode) is unavailable for GPT-6 Astra with EU data residency. +- **Misalignment monitoring:** As part of our [strengthened safeguards](https://openai.com/index/path-to-astra/) for GPT-6 Astra, our systems asynchronously monitor for misalignment and trigger alerts when necessary. See [Misalignment monitoring](https://developers.openai.com/api/docs/guides/safety-checks/misalignment-monitoring) for more information. -GPT-6 Astra also supports the existing API capabilities available with GPT-5.6, including [computer use](https://developers.openai.com/api/docs/guides/tools-computer-use), [Structured Outputs](https://developers.openai.com/api/docs/guides/structured-outputs), [streaming](https://developers.openai.com/api/docs/guides/streaming-responses), [Programmatic Tool Calling](https://developers.openai.com/api/docs/guides/tools-programmatic-tool-calling), [multi-agent orchestration](https://developers.openai.com/api/docs/guides/responses-multi-agent), [prompt caching](https://developers.openai.com/api/docs/guides/prompt-caching), [persisted reasoning](https://developers.openai.com/api/docs/guides/reasoning#preserve-reasoning-across-calls), [compaction](https://developers.openai.com/api/docs/guides/compaction), and [pro mode](https://developers.openai.com/api/docs/guides/reasoning#reasoning-mode). +GPT-6 also supports the existing API capabilities available with GPT-5.6, including [computer use](https://developers.openai.com/api/docs/guides/tools-computer-use), [Structured Outputs](https://developers.openai.com/api/docs/guides/structured-outputs), [streaming](https://developers.openai.com/api/docs/guides/streaming-responses), [Programmatic Tool Calling](https://developers.openai.com/api/docs/guides/tools-programmatic-tool-calling), [multi-agent orchestration](https://developers.openai.com/api/docs/guides/responses-multi-agent), [prompt caching](https://developers.openai.com/api/docs/guides/prompt-caching), [persisted reasoning](https://developers.openai.com/api/docs/guides/reasoning#preserve-reasoning-across-calls), [compaction](https://developers.openai.com/api/docs/guides/compaction), and [pro mode](https://developers.openai.com/api/docs/guides/reasoning#reasoning-mode). + +## Limitations + +- GPT-6 Astra and GPT-6.1 Sol do not support the `none` reasoning effort; GPT-6 Sol and GPT-6 Luna do. +- Fast mode is not available with EU data residency for GPT-6 Astra, GPT-6 Sol, or GPT-6 Luna. [Ultrafast mode](https://developers.openai.com/api/docs/guides/ultrafast-mode) supports US data residency and global processing only. It does not support EU or other non-US regional processing endpoints. See [data residency eligibility](https://developers.openai.com/api/docs/guides/your-data#which-models-and-features-are-eligible-for-data-residency). ## Migration quickstart ### Migrate with Codex -Codex can apply the recommended changes in this guide with the OpenAI Docs skill. +Codex can apply the recommended changes in this guide with the [OpenAI Docs skill](https://github.com/openai/codex/tree/main/codex-rs/skills/src/assets/samples/openai-docs). ```text -$openai-docs migrate this project to GPT-6 Astra +$openai-docs migrate this project to the GPT-6 model family ``` -To use this skill in other coding agents, download it from the OpenAI skills repository. +To use this skill in other coding agents, download it from the [Codex repository](https://github.com/openai/codex/tree/main/codex-rs/skills/src/assets/samples/openai-docs). ### Update API and model parameters -Set `model` to `gpt-6-astra`, then check the following: +Set `model` to `gpt-6-astra`, `gpt-6.1-sol`, or `gpt-6-luna`, then check the following: -- **Reasoning effort:** If you currently use `none` or `minimal`, start with `low` and compare results. Otherwise, preserve your current effective [reasoning effort](https://developers.openai.com/api/docs/guides/reasoning#reasoning-effort). Use `reasoning.effort` in Responses or `reasoning_effort` in Chat Completions. -- **Tool calling:** Use the [Responses API](https://developers.openai.com/api/docs/guides/migrate-to-responses#migrating-from-chat-completions). GPT-6 Astra supports Chat Completions, but tool calling requires Responses. -- **Unsupported parameters:** Remove `temperature`, `top_p`, and `top_logprobs`. For Chat Completions, also remove `logprobs`. For Responses, remove `message.output_text.logprobs` from `include`. -- **Fast mode:** For EU data residency, use Standard processing. GPT-6 Astra does not support `service_tier: "fast"` or `service_tier: "priority"` with EU data residency. Fast mode for GPT-6 Astra does not include a latency SLA. See [Fast mode compatibility](https://developers.openai.com/api/docs/guides/fast-mode#is-fast-mode-compatible-with-data-residency-zero-data-retention-and-a-baa). +- **Reasoning effort:** Preserve your current effective [reasoning effort](https://developers.openai.com/api/docs/guides/reasoning#reasoning-effort) where supported. GPT-6 Astra and GPT-6.1 Sol do not support `none`; use `low` instead. GPT-6 Sol and GPT-6 Luna support `none`. If your existing request uses `minimal`, start with `low` and compare results on representative tasks. Use `reasoning.effort` in Responses or `reasoning_effort` in Chat Completions. +- **Tool calling:** Use the [Responses API](https://developers.openai.com/api/docs/guides/migrate-to-responses#migrating-from-chat-completions). GPT-6 Astra and GPT-6.1 Sol support Chat Completions, but tool calling requires Responses. GPT-6 Sol and GPT-6 Luna support function calling in Chat Completions only with `reasoning_effort: "none"`. Use Responses for reasoning with tools. +- **Unsupported parameters:** When reasoning effort is not `none`, remove `temperature`, `top_p`, and `top_logprobs`. For Chat Completions, also remove `logprobs`. For Responses, remove `message.output_text.logprobs` from `include`. +- **Data residency:** Fast mode is not available with EU data residency for GPT-6 Astra, GPT-6 Sol, or GPT-6 Luna. [Ultrafast mode](https://developers.openai.com/api/docs/guides/ultrafast-mode) supports US data residency and global processing only. It does not support EU or other non-US regional processing endpoints. Fast mode for GPT-6 Astra does not include a latency SLA. See [Fast mode compatibility](https://developers.openai.com/api/docs/guides/fast-mode#is-fast-mode-compatible-with-data-residency-zero-data-retention-and-a-baa). - **Changing reasoning effort:** If your application changes effort between responses, use `configuration_update` items in standard, single-agent requests. Keep request-level `reasoning.effort` unchanged to preserve the prompt prefix for caching. Check the [compatibility limits](https://developers.openai.com/api/docs/guides/reasoning#change-reasoning-mid-conversation) before adopting this feature. - **Prompt caching:** When migrating from GPT-5.5 or earlier, replace `prompt_cache_retention` with `prompt_cache_options.ttl` set to `"30m"`. Review the [prompt caching changes](https://developers.openai.com/api/docs/guides/prompt-caching#summary-of-model-differences), including cache boundaries and cache-write billing. - **Unnecessary approval pauses:** If you run into issues where the model keeps asking for approval before proceeding, use the [initiative and follow-through guidance](https://developers.openai.com/api/docs/guides/latest-model/gpt-6-astra.md#initiative-and-follow-through) to prompt for more autonomous execution. See the rest of [Prompting best practices](https://developers.openai.com/api/docs/guides/latest-model/gpt-6-astra.md#prompting-best-practices) for guidance on instruction following, writing style, subagent delegation, and testing.