From 55acf23c8f97ecd76ac0ddf701be43dc3f8b9327 Mon Sep 17 00:00:00 2001 From: JUN <243035832+lidge-jun@users.noreply.github.com> Date: Tue, 27 Oct 2026 08:26:50 +0900 Subject: [PATCH 1/9] feat(providers): add GPT-6.1 Terra alongside existing models --- scripts/test-layout/layout.json | 2 +- src/adapters/devin/live-models.ts | 4 + src/adapters/kiro/reasoning.ts | 2 + src/providers/codebuddy-models.ts | 6 + src/providers/kiro-models.ts | 3 + src/providers/registry/entries-core.ts | 6 +- src/providers/registry/entries-extended.ts | 21 ++- src/providers/registry/model-seeds.ts | 7 +- structure/providers-and-adapters.md | 1 + tests/fixtures/test-layout-expected.json | 1 + .../digitalocean-scaleway-provider.test.ts | 9 +- tests/providers/gpt61-terra-rows.test.ts | 156 ++++++++++++++++++ tests/providers/modelflare-provider.test.ts | 4 +- .../provider-registry-parity.test.ts | 2 +- tests/providers/tokenlab-protocols.test.ts | 2 +- 15 files changed, 206 insertions(+), 20 deletions(-) create mode 100644 tests/providers/gpt61-terra-rows.test.ts diff --git a/scripts/test-layout/layout.json b/scripts/test-layout/layout.json index e4b15eb7c8e..20f93f9e0ec 100644 --- a/scripts/test-layout/layout.json +++ b/scripts/test-layout/layout.json @@ -1367,7 +1367,7 @@ "openrouter-provider-routing.test.ts": "providers", "openrouter-quota-reset-cooldown-4024.test.ts": "providers", "opper-provider.test.ts": "providers", "modelflare-provider.test.ts": "providers", "aistupidlevel-provider.test.ts": "providers", - "tokenlab-protocols.test.ts": "providers", + "tokenlab-protocols.test.ts": "providers", "gpt61-terra-rows.test.ts": "providers", "tokenlab-provider.test.ts": "providers", "optional-shutdown-hooks.test.ts": "lib", "orca-import.test.ts": "codex-integration", diff --git a/src/adapters/devin/live-models.ts b/src/adapters/devin/live-models.ts index 9295b58026c..a9893e5b35d 100644 --- a/src/adapters/devin/live-models.ts +++ b/src/adapters/devin/live-models.ts @@ -27,6 +27,8 @@ export const DEVIN_STATIC_MODELS = [ // 260930 preemptive: GPT-6.1 Sol (devin.ai/blog/gpt-6-1-sol says it is live; the uid is not published). // Spelled the way Devin spells gpt-5.6-sol; live discovery replaces this seed once a credential is present. "gpt-6-1-sol", + // 261027 preemptive: GPT-6.1 Terra (mirrors Devin's GPT-6.1 Sol seed; uid unverified). + "gpt-6-1-terra", "claude-opus-4-8", "claude-fable-5-1", "claude-sonnet-5", @@ -66,6 +68,8 @@ export const DEVIN_MODEL_CONTEXT_WINDOWS: Record = { "gpt-6-luna": 1_000_000, // 260930 preemptive: unmeasured; mirrors the GPT-6 Sol row Cognition serves. "gpt-6-1-sol": 1_000_000, + // 261027 preemptive: GPT-6.1 Terra (unmeasured; mirrors Devin's GPT-6.1 Sol window). + "gpt-6-1-terra": 1_000_000, "claude-opus-4-8": 1_000_000, // 260923: read from the live catalog (devin/claude-opus-5-5 context_length 1_000_000). "claude-opus-5-5": 1_000_000, diff --git a/src/adapters/kiro/reasoning.ts b/src/adapters/kiro/reasoning.ts index 55a9c1ca192..c8f865b8d54 100644 --- a/src/adapters/kiro/reasoning.ts +++ b/src/adapters/kiro/reasoning.ts @@ -28,6 +28,8 @@ export const KIRO_NATIVE_EFFORT_FIELDS: Record = { "gpt-6-sol": 1_000_000, "gpt-6-luna": 1_000_000, "gpt-6.1-sol": 1_000_000, + "gpt-6.1-terra": 1_000_000, "gpt-5.5": 1_000_000, "gpt-5.4": 272_000, "gpt-5.3-codex": 272_000, @@ -105,6 +108,7 @@ export const CODEBUDDY_GLOBAL_MODEL_MAX_OUTPUT_TOKENS: Record = "gpt-6-sol": 128_000, "gpt-6-luna": 128_000, "gpt-6.1-sol": 128_000, + "gpt-6.1-terra": 128_000, "gpt-5.5": 72_000, "gpt-5.4": 128_000, "gpt-5.3-codex": 128_000, @@ -124,6 +128,7 @@ export const CODEBUDDY_GLOBAL_MODEL_REASONING_EFFORTS: Record "gpt-6-sol": ["low", "medium", "high", "xhigh"], "gpt-6-luna": ["low", "medium", "high", "xhigh"], "gpt-6.1-sol": ["low", "medium", "high", "xhigh"], + "gpt-6.1-terra": ["low", "medium", "high", "xhigh"], "glm-5.3": ["low", "high", "max"], "glm-5.2": ["high", "xhigh"], }; @@ -135,6 +140,7 @@ export const CODEBUDDY_GLOBAL_MODEL_DEFAULT_REASONING_EFFORTS: Record = { "gpt-6-sol": 272_000, "gpt-6-luna": 272_000, "gpt-6.1-sol": 272_000, + "gpt-6.1-terra": 272_000, "claude-sonnet-5.5": 1_000_000, "claude-sonnet-5": 1_000_000, "claude-opus-5.5": 1_000_000, diff --git a/src/providers/registry/entries-core.ts b/src/providers/registry/entries-core.ts index 61cad3e3344..827e11a1105 100644 --- a/src/providers/registry/entries-core.ts +++ b/src/providers/registry/entries-core.ts @@ -251,7 +251,8 @@ export const PROVIDER_REGISTRY_CORE: readonly ProviderRegistryEntry[] = [ // (it is the current catalog, so its default ordering wins), then the ids // only the old devin entry carried. Degraded-mode seed only either way — // `liveModels` discovers the account's real roster. - models: ["swe-2", "swe-1-7", "gpt-5-6-sol", "gpt-6-astra", "gpt-6-1-sol", "gpt-6-sol", "gpt-6-luna", "claude-opus-5-5", "claude-opus-5", "claude-fable-5-1", "claude-sonnet-5-5", "claude-haiku-5-5", "claude-sonnet-5", "glm-5-3", "kimi-k3", "gemini-3-8-flash", "grok-4-6", "grok-4-7", "swe-1-7-lightning", "gpt-5-6-luna", "gpt-5-6-terra", "claude-opus-4-8", "glm-5-2", "kimi-k2-7", "grok-4-5"], + // 261027 preemptive: GPT-6.1 Terra (same degraded seed policy as GPT-6.1 Sol). + models: ["swe-2", "swe-1-7", "gpt-5-6-sol", "gpt-6-astra", "gpt-6-1-sol", "gpt-6-1-terra", "gpt-6-sol", "gpt-6-luna", "claude-opus-5-5", "claude-opus-5", "claude-fable-5-1", "claude-sonnet-5-5", "claude-haiku-5-5", "claude-sonnet-5", "glm-5-3", "kimi-k3", "gemini-3-8-flash", "grok-4-6", "grok-4-7", "swe-1-7-lightning", "gpt-5-6-luna", "gpt-5-6-terra", "claude-opus-4-8", "glm-5-2", "kimi-k2-7", "grok-4-5"], liveModels: true, defaultModel: "swe-2", modelContextWindows: DEVIN_MODEL_CONTEXT_WINDOWS, @@ -757,6 +758,8 @@ export const PROVIDER_REGISTRY_CORE: readonly ProviderRegistryEntry[] = [ ...OPENAI_DAYBREAK_REASONING_EFFORTS, "gpt-6-astra": ["low", "medium", "high", "xhigh", "max"], ...Object.fromEntries(OPENAI_GPT6_MODELS.map(id => [id, ["low", "medium", "high", "xhigh", "max"]])), + // OpenAI API model page (2026-10-27): Terra also accepts none; Sol does not. + "gpt-6.1-terra": ["none", "low", "medium", "high", "xhigh", "max"], }, virtualModels: OPENAI_API_GPT56_VIRTUAL_MODELS, }, @@ -1098,6 +1101,7 @@ export const PROVIDER_REGISTRY_CORE: readonly ProviderRegistryEntry[] = [ "openai/gpt-6-luna": true, // Listed 2026-09-29 as an OpenAI-backed route like GPT-6 Sol. "openai/gpt-6.1-sol": true, + "openai/gpt-6.1-terra": true, }, // Deliberately no OpenRouter route pin: it bills the endpoint actually used and reports the // actual service_tier. B0 confirmation therefore owns downgrade safety. Forcing `only` plus diff --git a/src/providers/registry/entries-extended.ts b/src/providers/registry/entries-extended.ts index 68c6adc5c81..f4816921a72 100644 --- a/src/providers/registry/entries-extended.ts +++ b/src/providers/registry/entries-extended.ts @@ -1246,10 +1246,11 @@ export const PROVIDER_REGISTRY_EXTENDED: readonly ProviderRegistryEntry[] = [ liveModels: true, preserveCustomDestination: true, defaultModel: "gpt-5.6-terra", - models: ["gpt-5.6-terra"], - modelContextWindows: { "gpt-5.6-terra": 1_050_000 }, - modelMaxOutputTokens: { "gpt-5.6-terra": 128_000 }, - modelInputModalities: { "gpt-5.6-terra": ["text", "image"] }, + // 261027 preemptive: GPT-6.1 Terra (OpenAI API limits; TokenLab listing unverified). + models: ["gpt-5.6-terra", "gpt-6.1-terra"], + modelContextWindows: { "gpt-5.6-terra": 1_050_000, "gpt-6.1-terra": 1_050_000 }, + modelMaxOutputTokens: { "gpt-5.6-terra": 128_000, "gpt-6.1-terra": 128_000 }, + modelInputModalities: { "gpt-5.6-terra": ["text", "image"], "gpt-6.1-terra": ["text", "image"] }, // Per-model wires from `tokenlab.accepted_request_formats` (GET /v1/models/{id}, 2026-09-30). // The provider stays on Chat, the released and end-to-end verified path, and every model // accepts it. Models that also declare Responses use it for Codex (Responses inbound) only, @@ -1258,7 +1259,8 @@ export const PROVIDER_REGISTRY_EXTENDED: readonly ProviderRegistryEntry[] = [ // gemini-3.8-flash declares Chat + Gemini native and stays on Chat. No delivery-policy // header is sent: the API key's own policy stays authoritative. modelWireDefaults: Object.fromEntries([ - "gpt-6-astra", "gpt-6.1-sol", "gpt-6-sol", "gpt-6-luna", "grok-4.7", + // 261027 preemptive: GPT-6.1 Terra (mirrors TokenLab's GPT-6.1 Sol wire). + "gpt-6-astra", "gpt-6.1-sol", "gpt-6.1-terra", "gpt-6-sol", "gpt-6-luna", "grok-4.7", "deepseek-v4.1-flash", "deepseek-v4-pro", "kimi-k3", "glm-5.3", ].map(id => [id, { wire: "openai-responses", inbound: ["responses"] }])), modelDiscovery: { @@ -1289,8 +1291,9 @@ export const PROVIDER_REGISTRY_EXTENDED: readonly ProviderRegistryEntry[] = [ dashboardUrl: "https://modelflare.dev", preserveCustomDestination: true, defaultModel: "glm-5.3-flash", - models: ["glm-5.3-flash", "claude-sonnet-5-5", "gpt-6.1-sol", "deepseek-v4-flash"], - note: "OpenAI-compatible relay for Claude, GPT, GLM and DeepSeek chat models. The seeded models were verified with chat, streaming and tool calls; deepseek-v4.1-flash is listed upstream but currently answers 503 and is left out. An ordinary key only reaches its own routing group's models; a Smart key reaches all seeded models. Image and video models are not served through this Chat preset. Upstream latency varies widely (a few seconds to about 30 s) with occasional transient 503s.", + // 261027 preemptive: GPT-6.1 Terra (mirrors Modelflare's GPT-6.1 Sol seed; provider listing unverified). + models: ["glm-5.3-flash", "claude-sonnet-5-5", "gpt-6.1-sol", "gpt-6.1-terra", "deepseek-v4-flash"], + note: "OpenAI-compatible relay for Claude, GPT, GLM and DeepSeek chat models. The original four seeded models were verified with chat, streaming and tool calls; GPT-6.1 Terra is a preemptive seed pending provider verification. deepseek-v4.1-flash is listed upstream but currently answers 503 and is left out. An ordinary key only reaches its own routing group's models; a Smart key reaches the verified seeded models. Image and video models are not served through this Chat preset. Upstream latency varies widely (a few seconds to about 30 s) with occasional transient 503s.", }, { // AI Stupid Level Smart Router, operated by S.C. Studio Platforms S.R.L. Contract checked @@ -1452,7 +1455,7 @@ export const PROVIDER_REGISTRY_EXTENDED: readonly ProviderRegistryEntry[] = [ featured: false, dashboardUrl: "https://github.com/settings/copilot", liveModels: true, - models: ["gpt-4o", "gpt-4.1", "gpt-4.1-mini", "claude-sonnet-4", "gemini-2.5-pro", "gpt-5-mini", "gpt-5.3-codex", "gpt-5.4", "gpt-5.4-mini", "gpt-5.5", "gpt-5.6-luna", "gpt-5.6-sol", "gpt-5.6-terra", "gpt-6.1-sol", "gpt-6-sol", "gpt-6-luna"], + models: ["gpt-4o", "gpt-4.1", "gpt-4.1-mini", "claude-sonnet-4", "gemini-2.5-pro", "gpt-5-mini", "gpt-5.3-codex", "gpt-5.4", "gpt-5.4-mini", "gpt-5.5", "gpt-5.6-luna", "gpt-5.6-sol", "gpt-5.6-terra", "gpt-6.1-sol", "gpt-6.1-terra", "gpt-6-sol", "gpt-6-luna"], defaultModel: "gpt-4o", // Copilot fronts a mixed-wire catalog: these models reject /chat/completions for // real Codex-agent traffic (function tools + reasoning), so every inbound wire @@ -1474,6 +1477,8 @@ export const PROVIDER_REGISTRY_EXTENDED: readonly ProviderRegistryEntry[] = [ "gpt-6-luna": "openai-responses", // GPT-6.1 Sol: GA in Copilot 2026-09-29 (github.blog changelog); rides Responses like GPT-6 Sol. "gpt-6.1-sol": "openai-responses", + // GPT-6.1 Terra: GA in Copilot 2026-10-26; rides Responses like GPT-6.1 Sol. + "gpt-6.1-terra": "openai-responses", "grok-4.5": "openai-responses", "grok-4.6": "openai-responses", "mai-code-1.1-flash": "openai-responses", diff --git a/src/providers/registry/model-seeds.ts b/src/providers/registry/model-seeds.ts index 4d6ddcd28d4..b60594f8226 100644 --- a/src/providers/registry/model-seeds.ts +++ b/src/providers/registry/model-seeds.ts @@ -222,7 +222,8 @@ export const OPENAI_API_GPT56_REASONING_EFFORTS = ["low", "medium", "high", "xhi * 1,050,000 context, 922,000 max input, 128,000 max output, efforts low..max * (https://developers.openai.com/api/docs/models/gpt-6.1-sol, checked 2026-09-30). */ -export const OPENAI_GPT6_MODELS = ["gpt-6.1-sol", "gpt-6-sol", "gpt-6-luna"]; +// GPT-6.1 Terra (2026-10-26): same API limits; its none..max ladder is set per model. +export const OPENAI_GPT6_MODELS = ["gpt-6.1-sol", "gpt-6.1-terra", "gpt-6-sol", "gpt-6-luna"]; /* * Meta Model API (https://api.meta.ai/v1) — published ladder, deliberately NOT the * house set. dev.meta.ai/docs/reasoning lists "none", "minimal", "low", "medium", @@ -330,6 +331,8 @@ export const OPENROUTER_GPT56_CONTEXT_WINDOWS = { "openai/gpt-6-luna": OPENROUTER_GPT56_CONTEXT_WINDOW, // Live /api/v1/models on 2026-09-30: context_length 1,050,000, max_completion_tokens 128,000. "openai/gpt-6.1-sol": OPENROUTER_GPT56_CONTEXT_WINDOW, + // OpenRouter listing checked 2026-10-27: context_length 1,050,000. + "openai/gpt-6.1-terra": OPENROUTER_GPT56_CONTEXT_WINDOW, }; /** @@ -987,6 +990,8 @@ export const DIGITALOCEAN_CHAT_COMPLETION_MODELS = [ "arcee-trinity-large-thinking", "openai-gpt-5.6-sol", "openai-gpt-5.6-terra", + // 261027 preemptive: GPT-6.1 Terra (mirrors the GPT-6 Sol seed; provider listing unverified). + "openai-gpt-6.1-terra", "openai-gpt-5.6-luna", // 260923 preemptive: GPT-6 Sol/Luna ahead of DigitalOcean's model list. "openai-gpt-6-sol", diff --git a/structure/providers-and-adapters.md b/structure/providers-and-adapters.md index 516db4b1191..a4230c3477b 100644 --- a/structure/providers-and-adapters.md +++ b/structure/providers-and-adapters.md @@ -330,6 +330,7 @@ rows. A supplied key scopes the catalog to its model permissions and delivery po anonymous catalog does not establish authentication. Newly promoted preset collision protection preserves an older same-named custom destination. `tests/providers/tokenlab-provider.test.ts` covers derived entry points, scoped discovery, destination preservation and model routing. +GPT-6.1 Terra's preemptive seed uses OpenAI API limits and GPT-6.1 Sol's wire; GPT-5.6 Terra stays selectable and default. `tests/providers/gpt61-terra-rows.test.ts` covers its limits and wires. Per-model wires follow TokenLab's declared `accepted_request_formats`: registry `modelWireDefaults` send the Responses-capable GPT-6, Grok, DeepSeek, Kimi and GLM ids over Responses for Responses inbound only, and an endpoint-bound `claude-` prefix pin in diff --git a/tests/fixtures/test-layout-expected.json b/tests/fixtures/test-layout-expected.json index 7e5022b3319..2d9d35496e3 100644 --- a/tests/fixtures/test-layout-expected.json +++ b/tests/fixtures/test-layout-expected.json @@ -1007,6 +1007,7 @@ "openrouter-provider-routing.test.ts": "providers", "openrouter-quota-reset-cooldown-4024.test.ts": "providers", "opper-provider.test.ts": "providers", "tokenlab-protocols.test.ts": "providers", "modelflare-provider.test.ts": "providers", + "gpt61-terra-rows.test.ts": "providers", "aistupidlevel-provider.test.ts": "providers", "tokenlab-provider.test.ts": "providers", "optional-shutdown-hooks.test.ts": "lib", "orca-import.test.ts": "codex-integration", "orcarouter-provider.test.ts": "providers", diff --git a/tests/providers/digitalocean-scaleway-provider.test.ts b/tests/providers/digitalocean-scaleway-provider.test.ts index c1d39a1940f..0bf919103c2 100644 --- a/tests/providers/digitalocean-scaleway-provider.test.ts +++ b/tests/providers/digitalocean-scaleway-provider.test.ts @@ -14,6 +14,7 @@ import { } from "../../src/providers/derive"; import { FREE_PROVIDER_DIRECTORY } from "../../src/providers/free-directory"; import { PROVIDER_REGISTRY, type ProviderRegistryEntry } from "../../src/providers/registry"; +import { DIGITALOCEAN_CHAT_COMPLETION_MODELS } from "../../src/providers/registry/model-seeds"; import { routedSlug } from "../../src/providers/slug-codec"; import { routeModel } from "../../src/router"; import type { OcxConfig, OcxProviderConfig } from "../../src/types"; @@ -107,11 +108,9 @@ describe("DigitalOcean and Scaleway providers", () => { }, }); const digitaloceanModels = discoveryAllowlist(registryEntry("digitalocean")); - // 29 since #5584 seeded openai-gpt-6-sol/-luna. An earlier seeding commit added - // glm-5.3-flash to both the DigitalOcean and Scaleway lists and moved neither length - // assertion; Scaleway's happened to still match, so only this one went red - and it - // stayed red on dev, which is how a broken shard reached the branch that noticed it. - expect(digitaloceanModels).toHaveLength(29); + // Derive membership from the canonical seed so model additions cannot stale a count. + expect(digitaloceanModels).toEqual([...DIGITALOCEAN_CHAT_COMPLETION_MODELS]); + expect(digitaloceanModels).toContain("openai-gpt-6.1-terra"); expect(digitaloceanModels).toContain("glm-5.3-flash"); expect(digitaloceanModels).toContain("openai-gpt-5.6-sol"); expect(digitaloceanModels).toContain("meta-llama/Meta-Llama-3.1-8B-Instruct"); diff --git a/tests/providers/gpt61-terra-rows.test.ts b/tests/providers/gpt61-terra-rows.test.ts new file mode 100644 index 00000000000..9e4b7bb2b79 --- /dev/null +++ b/tests/providers/gpt61-terra-rows.test.ts @@ -0,0 +1,156 @@ +import { afterEach, describe, expect, test } from "bun:test"; +import { DEVIN_MODEL_CONTEXT_WINDOWS, DEVIN_STATIC_MODELS } from "../../src/adapters/devin/live-models"; +import { kiroNativeEffortField, kiroReasoningMode } from "../../src/adapters/kiro/reasoning"; +import { providerConfigSeed } from "../../src/providers/derive"; +import { getProviderRegistryEntry, PROVIDER_REGISTRY } from "../../src/providers/registry"; +import { resolveWireProtocolOverride } from "../../src/server/adapter-resolve"; +import { handleResponses } from "../../src/server/responses/core"; +import type { OcxConfig } from "../../src/types"; +import { acquireOwnedSpendHome } from "../helpers/owned-spend-home"; + +const TERRA = "gpt-6.1-terra"; +const SOL = "gpt-6.1-sol"; +const INBOUNDS = ["responses", "chat", "anthropic"] as const; + +describe("GPT-6.1 Terra provider rows", () => { + test("every non-Cursor Terra/Sol seed retains its predecessor and adds Terra", () => { + for (const entry of PROVIDER_REGISTRY) { + if (entry.id === "cursor") continue; + for (const id of entry.models ?? []) { + if (!/gpt-(5[.-]6-terra|6[.-]1-sol)$/.test(id)) continue; + const terra = id.replace(/gpt-(5[.-]6-terra|6[.-]1-sol)$/, matched => + matched.includes(".") ? TERRA : "gpt-6-1-terra"); + expect(entry.models, `${entry.id}: ${id}`).toContain(terra); + } + } + }); + + test("OpenAI API declares the API window, modalities and none..max ladder", () => { + const entry = getProviderRegistryEntry("openai-apikey")!; + expect(entry.models).toContain(TERRA); + expect(entry.models).toContain("gpt-5.6-terra"); + expect(entry.modelContextWindows?.[TERRA]).toBe(1_050_000); + expect(entry.modelMaxInputTokens?.[TERRA]).toBe(922_000); + expect(entry.modelMaxOutputTokens?.[TERRA]).toBe(128_000); + expect(entry.modelInputModalities?.[TERRA]).toEqual(["text", "image"]); + expect(entry.modelReasoningEfforts?.[TERRA]).toEqual(["none", "low", "medium", "high", "xhigh", "max"]); + expect(entry.modelReasoningEfforts?.[SOL]).toEqual(["low", "medium", "high", "xhigh", "max"]); + expect(entry.virtualModels?.[`${TERRA}-pro`]).toBeUndefined(); + }); + + test("OpenRouter advertises the 1.05M OpenAI route and Fast eligibility", () => { + const entry = getProviderRegistryEntry("openrouter")!; + expect(entry.models).toContain(`openai/${TERRA}`); + expect(entry.modelContextWindows?.[`openai/${TERRA}`]).toBe(1_050_000); + expect(entry.modelSupportsServiceTier?.[`openai/${TERRA}`]).toBe(true); + }); + + test.each(["codebuddy", "kiro"])("%s mirrors its own Sol metadata", provider => { + const entry = getProviderRegistryEntry(provider)!; + expect(entry.models).toContain(TERRA); + for (const field of ["modelContextWindows", "modelMaxOutputTokens", "modelReasoningEfforts", + "modelDefaultReasoningEfforts", "modelInputModalities"] as const) { + expect(entry[field]?.[TERRA], field).toEqual(entry[field]?.[SOL]); + } + expect(entry.modelContextWindows?.[TERRA]).toBe(provider === "kiro" ? 272_000 : 1_000_000); + }); + + test("Kiro uses the Sol native effort field, including xhigh", () => { + for (const effort of ["low", "medium", "high", "xhigh", "max"]) { + expect(kiroNativeEffortField(`kiro/gpt-6-1-terra-${effort}`, effort)).toBe("reasoning"); + expect(kiroReasoningMode(TERRA, effort)).toBe(kiroReasoningMode(SOL, effort)); + } + expect(kiroNativeEffortField("gpt-5.6-terra", "xhigh")).toBeUndefined(); + }); + + test("Devin uses its dashed degraded seed and provider-specific 1M window", () => { + expect(DEVIN_STATIC_MODELS).toContain("gpt-6-1-terra"); + expect(DEVIN_STATIC_MODELS).toContain("gpt-5-6-terra"); + const entry = getProviderRegistryEntry("devin")!; + expect(entry.models).toContain("gpt-6-1-terra"); + expect(DEVIN_MODEL_CONTEXT_WINDOWS["gpt-6-1-terra"]).toBe(1_000_000); + expect(entry.modelReasoningEfforts?.["gpt-6-1-terra"]) + .toEqual(entry.modelReasoningEfforts?.["gpt-6-1-sol"]); + }); + + test.each(["github-copilot", "tokenlab"])("%s mirrors Sol wire selection and explicit overrides", provider => { + const entry = getProviderRegistryEntry(provider)!; + const seed = providerConfigSeed(entry); + expect(entry.models).toContain(TERRA); + for (const inbound of INBOUNDS) { + const expected = provider === "github-copilot" || inbound === "responses" ? "openai-responses" : "openai-chat"; + expect(resolveWireProtocolOverride(provider, TERRA, seed, inbound).adapter).toBe(expected); + expect(resolveWireProtocolOverride(provider, TERRA, { + ...seed, modelAdapters: { [TERRA]: "openai-chat" }, + }, inbound).adapter).toBe("openai-chat"); + } + expect(resolveWireProtocolOverride("unrelated", TERRA, { + adapter: "openai-chat", baseUrl: "https://example.test/v1", + }, "responses").adapter).toBe("openai-chat"); + }); + + test("TokenLab retains the 5.6 default and seeds Terra limits", () => { + const entry = getProviderRegistryEntry("tokenlab")!; + expect(entry.defaultModel).toBe("gpt-5.6-terra"); + expect(entry.models).toContain("gpt-5.6-terra"); + expect(entry.modelContextWindows?.[TERRA]).toBe(1_050_000); + expect(entry.modelMaxOutputTokens?.[TERRA]).toBe(128_000); + expect(entry.modelInputModalities?.[TERRA]).toEqual(["text", "image"]); + }); + + test("Terra is never a provider default and Cursor has no Terra 6.1 seed", () => { + for (const entry of PROVIDER_REGISTRY) { + expect(entry.defaultModel ?? "").not.toMatch(/gpt-6[.-]1-terra/); + } + expect(getProviderRegistryEntry("cursor")!.models).not.toContain(TERRA); + expect(getProviderRegistryEntry("openai-apikey")!.defaultModel).toBe("gpt-5.5"); + expect(getProviderRegistryEntry("github-copilot")!.defaultModel).toBe("gpt-4o"); + }); +}); + +describe("GPT-6.1 Terra provider wires through handleResponses", () => { + const originalFetch = globalThis.fetch; + let releaseSpendHome: (() => void) | undefined; + + afterEach(() => { + releaseSpendHome?.(); + releaseSpendHome = undefined; + globalThis.fetch = originalFetch; + }); + + async function upstream(provider: string, inboundWire: typeof INBOUNDS[number], effort?: string) { + const seen: Array<{ url: string; body: Record }> = []; + globalThis.fetch = (async (input, init) => { + seen.push({ url: String(input), body: JSON.parse(String(init?.body)) }); + return new Response("data: [DONE]\n\n", { headers: { "content-type": "text/event-stream" } }); + }) as typeof fetch; + releaseSpendHome = acquireOwnedSpendHome(); + const config = { providers: { [provider]: { + ...providerConfigSeed(getProviderRegistryEntry(provider)!), authMode: "key", apiKey: "test-key", + } } } as unknown as OcxConfig; + await handleResponses(new Request("http://localhost/v1/responses", { + method: "POST", headers: { "content-type": "application/json" }, + body: JSON.stringify({ model: `${provider}/${TERRA}`, input: "ping", stream: true, + ...(effort ? { reasoning: { effort } } : {}) }), + }), config, { model: "", provider: "" }, { inboundWire }); + expect(seen).toHaveLength(1); + return seen[0]!; + } + + for (const provider of ["github-copilot", "tokenlab"]) { + test.each(INBOUNDS)(`${provider} Terra reaches the correct endpoint on %s inbound`, async inbound => { + const seen = await upstream(provider, inbound); + const responses = provider === "github-copilot" || inbound === "responses"; + const base = provider === "github-copilot" ? "https://api.githubcopilot.com/v1" : "https://api.tokenlab.sh/v1"; + expect(seen.url).toBe(`${base}/${responses ? "responses" : "chat/completions"}`); + expect(seen.body.model).toBe(TERRA); + }); + } + + test.each(["none", "ultra"])("API Terra sends %s effort using the API wire ladder", async effort => { + const seen = await upstream("openai-apikey", "responses", effort); + expect(seen.url).toBe("https://api.openai.com/v1/responses"); + expect(seen.body.model).toBe(TERRA); + expect(seen.body.reasoning).toMatchObject({ effort: effort === "ultra" ? "max" : "none" }); + }); +}); diff --git a/tests/providers/modelflare-provider.test.ts b/tests/providers/modelflare-provider.test.ts index 14d89deee44..8383c5c9ee8 100644 --- a/tests/providers/modelflare-provider.test.ts +++ b/tests/providers/modelflare-provider.test.ts @@ -40,10 +40,10 @@ describe("Modelflare provider", () => { expect(KEY_LOGIN_PROVIDERS.modelflare?.defaultModel).toBe("glm-5.3-flash"); }); - test("seeds only the verified chat models and leaves the 503-only DeepSeek V4.1 Flash out", () => { + test("seeds verified chat models plus preemptive Terra and leaves the 503-only DeepSeek V4.1 Flash out", () => { const seeded = config().providers.modelflare!; expect(seeded).toMatchObject({ adapter: "openai-chat", baseUrl, defaultModel: "glm-5.3-flash" }); - expect(entry().models).toEqual([...VERIFIED_MODELS]); + expect(entry().models).toEqual([...VERIFIED_MODELS.slice(0, 3), "gpt-6.1-terra", ...VERIFIED_MODELS.slice(3)]); expect(entry().models).not.toContain("deepseek-v4.1-flash"); expect(seeded.liveModels).not.toBe(true); }); diff --git a/tests/providers/provider-registry-parity.test.ts b/tests/providers/provider-registry-parity.test.ts index 30f8170c7bc..0ee42da3376 100644 --- a/tests/providers/provider-registry-parity.test.ts +++ b/tests/providers/provider-registry-parity.test.ts @@ -323,7 +323,7 @@ describe("provider registry parity", () => { expect(KEY_LOGIN_PROVIDERS.umans.modelContextWindows?.["umans-glm-5.2"]).toBe(405_504); expect(KEY_LOGIN_PROVIDERS.umans.modelInputModalities?.["umans-coder"]).toEqual(["text", "image"]); expect(KEY_LOGIN_PROVIDERS.umans.modelInputModalities?.["umans-glm-5.2"]).toEqual(["text"]); - expect(KEY_LOGIN_PROVIDERS["openai-apikey"].models).toEqual(["gpt-5.5", "gpt-5.6", "gpt-5.6-sol", "gpt-5.6-terra", "gpt-5.6-luna", "gpt-5.6-sol-pro", "gpt-5.6-terra-pro", "gpt-5.6-luna-pro", "daybreak-red-latest", "daybreak-blue-latest", "gpt-6-astra", "gpt-6.1-sol", "gpt-6-sol", "gpt-6-luna"]); + expect(KEY_LOGIN_PROVIDERS["openai-apikey"].models).toEqual(["gpt-5.5", "gpt-5.6", "gpt-5.6-sol", "gpt-5.6-terra", "gpt-5.6-luna", "gpt-5.6-sol-pro", "gpt-5.6-terra-pro", "gpt-5.6-luna-pro", "daybreak-red-latest", "daybreak-blue-latest", "gpt-6-astra", "gpt-6.1-sol", "gpt-6.1-terra", "gpt-6-sol", "gpt-6-luna"]); expect(KEY_LOGIN_PROVIDERS["openai-apikey"].modelContextWindows?.["gpt-6-astra"]).toBe(1_050_000); expect(KEY_LOGIN_PROVIDERS["openai-apikey"].modelMaxInputTokens?.["gpt-6-astra"]).toBe(922_000); expect(KEY_LOGIN_PROVIDERS["openai-apikey"].modelMaxOutputTokens?.["gpt-6-astra"]).toBe(128_000); diff --git a/tests/providers/tokenlab-protocols.test.ts b/tests/providers/tokenlab-protocols.test.ts index fe8c9d0acfc..b893904fe2f 100644 --- a/tests/providers/tokenlab-protocols.test.ts +++ b/tests/providers/tokenlab-protocols.test.ts @@ -19,7 +19,7 @@ import { acquireOwnedSpendHome } from "../helpers/owned-spend-home"; const BASE_URL = "https://api.tokenlab.sh/v1"; const RESPONSES_MODELS = [ - "gpt-6-astra", "gpt-6.1-sol", "gpt-6-sol", "gpt-6-luna", "grok-4.7", + "gpt-6-astra", "gpt-6.1-sol", "gpt-6.1-terra", "gpt-6-sol", "gpt-6-luna", "grok-4.7", "deepseek-v4.1-flash", "deepseek-v4-pro", "kimi-k3", "glm-5.3", ] as const; const CLAUDE_MODELS = [ From ce62db912b00f80d8d726b04c21c93b6767387ec Mon Sep 17 00:00:00 2001 From: JUN <243035832+lidge-jun@users.noreply.github.com> Date: Tue, 27 Oct 2026 08:32:21 +0900 Subject: [PATCH 2/9] docs(models): document GPT-6.1 Terra across locales --- .../docs/fr/getting-started/quickstart.md | 2 + .../docs/fr/guides/codex-app-models.md | 7 ++- .../content/docs/fr/guides/model-ordering.md | 2 + .../src/content/docs/fr/guides/providers.md | 7 ++- .../src/content/docs/fr/reference/adapters.md | 2 + .../fr/reference/configuration/providers.md | 12 +++- .../fr/reference/configuration/routing.md | 2 + .../docs/getting-started/quickstart.md | 2 + .../content/docs/guides/codex-app-models.md | 9 ++- .../src/content/docs/guides/model-ordering.md | 2 + .../src/content/docs/guides/providers.md | 18 ++++-- .../docs/ja/getting-started/quickstart.md | 2 + .../docs/ja/guides/codex-app-models.md | 7 ++- .../content/docs/ja/guides/model-ordering.md | 2 + .../src/content/docs/ja/guides/providers.md | 7 ++- .../src/content/docs/ja/reference/adapters.md | 2 + .../ja/reference/configuration/providers.md | 12 +++- .../ja/reference/configuration/routing.md | 2 + .../docs/ko/getting-started/quickstart.md | 2 + .../docs/ko/guides/codex-app-models.md | 7 ++- .../content/docs/ko/guides/model-ordering.md | 2 + .../src/content/docs/ko/guides/providers.md | 7 ++- .../src/content/docs/ko/reference/adapters.md | 2 + .../ko/reference/configuration/providers.md | 12 +++- .../ko/reference/configuration/routing.md | 2 + .../src/content/docs/reference/adapters.md | 2 + .../docs/reference/configuration/agents.md | 2 +- .../docs/reference/configuration/providers.md | 13 ++++- .../docs/reference/configuration/routing.md | 2 + .../docs/ru/getting-started/quickstart.md | 2 + .../docs/ru/guides/codex-app-models.md | 7 ++- .../content/docs/ru/guides/model-ordering.md | 2 + .../src/content/docs/ru/guides/providers.md | 7 ++- .../src/content/docs/ru/reference/adapters.md | 2 + .../ru/reference/configuration/providers.md | 12 +++- .../ru/reference/configuration/routing.md | 2 + .../docs/tr/getting-started/quickstart.md | 2 + .../docs/tr/guides/codex-app-models.md | 7 ++- .../content/docs/tr/guides/model-ordering.md | 2 + .../src/content/docs/tr/guides/providers.md | 7 ++- .../src/content/docs/tr/reference/adapters.md | 2 + .../tr/reference/configuration/providers.md | 12 +++- .../tr/reference/configuration/routing.md | 2 + .../docs/zh-cn/getting-started/quickstart.md | 2 + .../docs/zh-cn/guides/codex-app-models.md | 7 ++- .../docs/zh-cn/guides/model-ordering.md | 2 + .../content/docs/zh-cn/guides/providers.md | 7 ++- .../content/docs/zh-cn/reference/adapters.md | 2 + .../reference/configuration/providers.md | 12 +++- .../zh-cn/reference/configuration/routing.md | 2 + .../docs/zh-tw/getting-started/quickstart.md | 2 + .../docs/zh-tw/guides/codex-app-models.md | 7 ++- .../docs/zh-tw/guides/model-ordering.md | 2 + .../content/docs/zh-tw/guides/providers.md | 7 ++- .../docs/zh-tw/guides/sub-agent-surface.md | 4 +- .../content/docs/zh-tw/reference/adapters.md | 2 + .../reference/configuration/providers.md | 12 +++- .../zh-tw/reference/configuration/routing.md | 2 + scripts/test-layout/layout.json | 2 +- tests/ci-workflows/docs-gpt61-terra.test.ts | 56 +++++++++++++++++++ tests/fixtures/test-layout-expected.json | 1 + 61 files changed, 311 insertions(+), 40 deletions(-) create mode 100644 tests/ci-workflows/docs-gpt61-terra.test.ts diff --git a/docs-site/src/content/docs/fr/getting-started/quickstart.md b/docs-site/src/content/docs/fr/getting-started/quickstart.md index fa96c775b52..4036591dbb9 100644 --- a/docs-site/src/content/docs/fr/getting-started/quickstart.md +++ b/docs-site/src/content/docs/fr/getting-started/quickstart.md @@ -5,6 +5,8 @@ description: Configurez votre premier fournisseur et acheminez OpenAI Codex via Ce guide part d’une installation neuve et vous conduit jusqu’à l’exécution de Codex sur un modèle autre qu’OpenAI. +Vous pouvez aussi choisir `gpt-6.1-terra` aux côtés de `gpt-5.6-terra`, sans modifier le modèle par défaut ni la liste des sous-agents. Voir les [limites, le raisonnement et le mode Fast de GPT-6.1 Terra](/fr/reference/configuration/providers/#gpt-61-terra). + ## 1. Exécutez l'assistant de configuration ```bash diff --git a/docs-site/src/content/docs/fr/guides/codex-app-models.md b/docs-site/src/content/docs/fr/guides/codex-app-models.md index 0e69068a714..23c959d0288 100644 --- a/docs-site/src/content/docs/fr/guides/codex-app-models.md +++ b/docs-site/src/content/docs/fr/guides/codex-app-models.md @@ -89,6 +89,8 @@ cp ~/.opencodex/config.json.pre-openai-tiers-v2.bak ~/.opencodex/config.json Les anciennes configurations v1 à trois fournisseurs migrent automatiquement vers l'unique ligne tenant compte de l'option choisie. +Vous pouvez aussi choisir `gpt-6.1-terra` aux côtés de `gpt-5.6-terra`, sans modifier le modèle par défaut ni la liste des sous-agents. Voir les [limites, le raisonnement et le mode Fast de GPT-6.1 Terra](/fr/reference/configuration/providers/#gpt-61-terra). + ## Limitation de la liste d'autorisation distante de Desktop Si `codex debug models` et `model/list` du serveur d'application contiennent un modèle routé que Desktop @@ -138,11 +140,12 @@ approximation fondée sur un ancien modèle d'entrée. | Route | Identifiants du sélecteur et métadonnées du catalogue | | --- | --- | -| Connexion Codex (lignes qualifiées par compte désactivées) | Identifiants natifs non qualifiés comme `gpt-5.6-sol`, `gpt-5.6-terra` et `gpt-5.6-luna` ; Pool ou Direct est choisi avec `codexAccountMode`. Les lignes GPT-5.6 utilisent une fenêtre de catalogue de 372 000 jetons. | +| Connexion Codex (lignes qualifiées par compte désactivées) | Identifiants natifs non qualifiés comme `gpt-5.6-sol`, `gpt-5.6-terra` et `gpt-5.6-luna` ; Pool ou Direct est choisi avec `codexAccountMode`. Les lignes GPT-5.6 utilisent une fenêtre de catalogue de 372 000 jetons. `gpt-6.1-terra` : contexte par défaut 500,000 / étendu 872,000. | | Connexion Codex (lignes qualifiées par compte activées avec des sélecteurs admissibles) | Une ligne `/` par sélecteur admissible et modèle natif pris en charge ; chaque ligne utilise exclusivement le compte associé, et les lignes natives non qualifiées sont masquées dans le sélecteur. Les métadonnées natives et les fenêtres de contexte sont préservées. | | Connexion Codex (ligne Daybreak transférée explicitement) | `openai/gpt-daybreak-blue-latest` uniquement lorsque l'entrée `customModels` exacte est configurée sur le fournisseur canonique `openai`. Elle conserve l'identifiant Daybreak transmis et utilise l'instantané de capacités Sol épinglé (contexte de 372 000 jetons ; compactage automatique à 334 800 jetons). | -| OpenAI (clé API) | Exactement dix lignes avec espace de noms : `gpt-5.5`, `gpt-5.6`, Sol/Terra/Luna, les trois identifiants virtuels `*-pro` et les deux alias Daybreak (contexte de 1 050 000 jetons ; entrée maximale de 922 000 jetons pour les dix) | +| OpenAI (clé API) | Les modèles avec espace de noms comprennent `gpt-5.5`, `gpt-5.6`, Sol/Terra/Luna, les identifiants virtuels `*-pro` et les alias Daybreak (contexte de 1,050,000 ; entrée maximale de 922,000). `openai-apikey/gpt-6.1-terra` ajoute un contexte de 1,050,000 et une sortie maximale de 128,000. | | OpenRouter | `openrouter/openai/gpt-5.6-sol`, `openrouter/openai/gpt-5.6-terra`, `openrouter/openai/gpt-5.6-luna` (1 050 000) | +| OpenRouter | `openrouter/openai/gpt-6.1-terra` (1,050,000) | | Cursor | Le repli statique comprend `cursor/gpt-5.6-sol`, `cursor/gpt-5.6-terra` et `cursor/gpt-5.6-luna` (1 000 000), ainsi que des lignes ordinaires/rapides pour Grok 4.5, 4.6 et 4.7 (500 000) ; 4.6 et 4.7 ajoutent `xhigh`, et la découverte dynamique propre au compte détermine quelles lignes restent visibles. | | xAI | La découverte dynamique fait autorité. Le catalogue de secours comprend `xai/grok-4.6` et `xai/grok-4.7` et utilise `xai/grok-4.5` par défaut ; les trois ont une fenêtre de 500 000 jetons. Grok 4.6 et 4.7 proposent `low` / `medium` / `high` / `xhigh` (valeur amont par défaut : `high`), tandis que Grok 4.5 s’arrête à `high`. | diff --git a/docs-site/src/content/docs/fr/guides/model-ordering.md b/docs-site/src/content/docs/fr/guides/model-ordering.md index fab755afdf4..52fa03cf3d1 100644 --- a/docs-site/src/content/docs/fr/guides/model-ordering.md +++ b/docs-site/src/content/docs/fr/guides/model-ordering.md @@ -7,6 +7,8 @@ Le sélecteur de modèles Codex ne conserve ni l’ordre de déclaration des fou configuration opencodex. L’ordre final découle des priorités du catalogue ; les modèles routés qui partagent la même priorité sont classés selon un ordre alphabétique déterministe. +Vous pouvez aussi choisir `gpt-6.1-terra` aux côtés de `gpt-5.6-terra`, sans modifier le modèle par défaut ni la liste des sous-agents. Voir les [limites, le raisonnement et le mode Fast de GPT-6.1 Terra](/fr/reference/configuration/providers/#gpt-61-terra). + ## La règle Codex s'applique Le gestionnaire de modèles de Codex trie les entrées de catalogue visibles dans le sélecteur par `priority`, dans l’ordre croissant. Il diff --git a/docs-site/src/content/docs/fr/guides/providers.md b/docs-site/src/content/docs/fr/guides/providers.md index 59b7a72c46b..dc1cab71246 100644 --- a/docs-site/src/content/docs/fr/guides/providers.md +++ b/docs-site/src/content/docs/fr/guides/providers.md @@ -7,6 +7,8 @@ Un **fournisseur** associe un point de terminaison LLM en amont à la façon de une URL de base, un mode d'authentification et, facultativement, une liste de modèles. Les fournisseurs sont définis sous `providers` dans `~/.opencodex/config.json`. +Vous pouvez aussi choisir `gpt-6.1-terra` aux côtés de `gpt-5.6-terra`, sans modifier le modèle par défaut ni la liste des sous-agents. Voir les [limites, le raisonnement et le mode Fast de GPT-6.1 Terra](/fr/reference/configuration/providers/#gpt-61-terra). + ## Modes de compte OpenAI | Identifiant du fournisseur | Utilisation | Règle relative aux identifiants et aux comptes | @@ -624,6 +626,9 @@ maintenir leur visibilité même lorsque les catalogues en direct ne sont pas en | Connexion Codex (Pool ou Direct) | `gpt-5.6-*` | 372 000 | | OpenAI (clé API) | `openai-apikey/gpt-5.6-*` plus `*-pro` | 1 050 000 (entrée maximale de 922 000) | | OpenRouter | `openrouter/openai/gpt-5.6-sol`, `openrouter/openai/gpt-5.6-terra`, `openrouter/openai/gpt-5.6-luna` | 1 050 000 | +| Codex | `gpt-6.1-terra` | 500,000 / 872,000 | +| OpenAI API | `openai-apikey/gpt-6.1-terra` | 1,050,000 (128,000 max output) | +| OpenRouter | `openrouter/openai/gpt-6.1-terra` | 1,050,000 | | Cursor | `cursor/gpt-5.6-sol`, `cursor/gpt-5.6-terra`, `cursor/gpt-5.6-luna` | 1 000 000 | Les entrées natives GPT-5.6 conservent les niveaux de raisonnement fixés en amont — Luna propose par exemple @@ -644,7 +649,7 @@ reste une passerelle à clé ou jeton d'abonnement sur son point de terminaison **Cloudflare AI Gateway** exige que les identifiants de votre compte et de votre passerelle figurent dans l'URL. Copilot présente un catalogue qui utilise plusieurs protocoles : ces modèles (`gpt-5.3-codex`, `gpt-5.4`, -`gpt-5.4-mini`, `gpt-5.5`, `gpt-5.6-luna`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`) rejettent +`gpt-5.4-mini`, `gpt-5.5`, `gpt-5.6-luna`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-6.1-sol`, `gpt-6.1-terra`, `gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`) rejettent `/chat/completions` pour le trafic d'agent. opencodex route donc ces modèles sur l'API Responses par défaut, tandis que tous les autres modèles Copilot restent sur Chat Completions. L'ordre de priorité est le suivant : verrouillage explicite du protocole → entrée [`modelAdapters`](/fr/reference/configuration/providers/) définie diff --git a/docs-site/src/content/docs/fr/reference/adapters.md b/docs-site/src/content/docs/fr/reference/adapters.md index d45e12b48a1..8f22a99a5b8 100644 --- a/docs-site/src/content/docs/fr/reference/adapters.md +++ b/docs-site/src/content/docs/fr/reference/adapters.md @@ -20,6 +20,8 @@ interface ProviderAdapter { `incoming` est un `IncomingMeta` obligatoire qui transporte notamment les en-têtes, le signal d’abandon et le budget de traduction. Le contexte facultatif de `fetchResponse` est un `AdapterFetchContext`. Les méthodes d’analyse reçoivent elles aussi un `TranslatorBudget` obligatoire afin de borner les données traduites. +Vous pouvez aussi choisir `gpt-6.1-terra` aux côtés de `gpt-5.6-terra`, sans modifier le modèle par défaut ni la liste des sous-agents. Voir les [limites, le raisonnement et le mode Fast de GPT-6.1 Terra](/fr/reference/configuration/providers/#gpt-61-terra). + ## `openai-chat` **Cibles :** l’API **Chat Completions** d’OpenAI (`POST {baseUrl}/chat/completions` ; un suffixe `/chat/completions` ou `/` est d’abord retiré de `baseUrl`) et tous les fournisseurs compatibles — xAI, Kimi, DeepSeek, GLM, Groq, OpenRouter, Ollama (local), entre autres. diff --git a/docs-site/src/content/docs/fr/reference/configuration/providers.md b/docs-site/src/content/docs/fr/reference/configuration/providers.md index 031ce647b2b..a46a4f89add 100644 --- a/docs-site/src/content/docs/fr/reference/configuration/providers.md +++ b/docs-site/src/content/docs/fr/reference/configuration/providers.md @@ -12,6 +12,16 @@ En l’absence de fenêtre déclarée ou configurée, OpenCodex utilise les mét Cette estimation est désactivée par défaut : activez-la par fournisseur avec `inferContextWindow: true`. Sans ce réglage, une fenêtre absente utilise le Context cap activé, puis 128k. +## GPT-6.1 Terra + +[GPT-6.1 Terra](https://openai.com/index/introducing-gpt-6-1-terra/), sorti le 26 octobre 2026, succède à GPT-5.6 Terra. `gpt-6.1-terra` reste disponible aux côtés de `gpt-5.6-terra`, sans changement de modèle par défaut ni de liste de sous-agents. GitHub Copilot utilise Responses ; OpenRouter propose `openai/gpt-6.1-terra` avec un contexte de 1,050,000 tokens et des tarifs de $1.00 en entrée / $5.00 en sortie par million de tokens. + +Codex natif : contexte par défaut de 500,000 tokens, plafond étendu de 872,000, effort par défaut `low` et niveaux `low`, `medium`, `high`, `xhigh`, `max`, `ultra`. Le niveau natif `ultra` est envoyé sous la forme `max` sur le réseau. La ligne native propose uniquement Fast. + +[API OpenAI](https://developers.openai.com/api/docs/models/gpt-6.1-terra) : contexte de 1,050,000 tokens, sortie maximale de 128,000 ; entrée texte/image, sortie texte ; connaissances arrêtées au 2026-06-01. Efforts : `none`, `low`, `medium` (par défaut), `high`, `xhigh`, `max`. Points de terminaison : `v1/responses` et `v1/chat/completions` ; les appels d’outils nécessitent Responses. + +Par million de tokens : $1.00 en entrée, $0.05 en lecture du cache, $1.25 en écriture du cache (30 minutes), $5.00 en sortie. Au-delà de 272,000 tokens d’entrée, toute la requête est facturée à 2× pour l’entrée et le cache, et 1.5× pour la sortie : respectivement $2.00 / $0.10 / $2.50 / $7.50. Le mode Fast coûte 2×. + ## Sélection des modèles à l’inscription Une nouvelle connexion sans OAuth attend une liste de modèles fiable avant de les exposer. Si l’onglet Models contient au moins 20 lignes distinctes, tous les interrupteurs de modèles sont initialement OFF ; le fournisseur reste ACTIVE. Les connexions utilisant effectivement OAuth ou la connexion ChatGPT conservent leurs valeurs par défaut. @@ -133,7 +143,7 @@ sauvegarde dont le contenu diffère, puis réécrit en identifiants sans préfix | `modelReasoningEfforts?` | `Record` | Libellés propres à chaque modèle. Une liste vide masque le contrôle de l'effort. Comme pour `reasoningEfforts`, chaque échelle configurée avec l'adaptateur `google` déclare la capacité `thinkingLevel` ; les requêtes directes et Vertex sans image utilisent le chemin Gemini à plat, tandis que Cloud Code Assist l'envoie dans son enveloppe de requête. | | `modelSupportsReasoningSummaries?` | `Record` | Définissez un modèle sur `false` pour arrêter la publicité des résumés et supprimer les champs de livraison du résumé. | | `modelReasoningSummaryDelivery?` | `Record` | Énumération de livraison des réponses par modèle ; réécrit un champ de livraison existant. | -| `modelAdapters?` | `Record` | Remplacement du protocole `openai-chat` ou `openai-responses` par modèle pour les passerelles multiprotocoles. Les entrées explicites priment sur les valeurs par défaut du registre. Le préréglage OpenCode Go sélectionne Responses pour `gpt-5.6-luna` tout en laissant les modèles apparentés sur leurs protocoles documentés ; DeepSeek peut sélectionner Responses natif pour `deepseek-v4-flash` ; GitHub Copilot déclare des valeurs par défaut limitées à Responses pour ces modèles (`gpt-5.3-codex`, `gpt-5.4`, `gpt-5.4-mini`, `gpt-5.5`, `gpt-5.6-luna`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`), car ces modèles rejettent `/chat/completions` pour le trafic des agents. Les modèles sans valeur intégrée par défaut, comme `gpt-5.4-nano`, peuvent être activés ici. Les services en amont à protocole unique et le transfert canonique ChatGPT rejettent ces remplacements. | +| `modelAdapters?` | `Record` | Remplacement du protocole `openai-chat` ou `openai-responses` par modèle pour les passerelles multiprotocoles. Les entrées explicites priment sur les valeurs par défaut du registre. Le préréglage OpenCode Go sélectionne Responses pour `gpt-5.6-luna` tout en laissant les modèles apparentés sur leurs protocoles documentés ; DeepSeek peut sélectionner Responses natif pour `deepseek-v4-flash` ; GitHub Copilot déclare des valeurs par défaut limitées à Responses pour ces modèles (`gpt-5.3-codex`, `gpt-5.4`, `gpt-5.4-mini`, `gpt-5.5`, `gpt-5.6-luna`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-6.1-sol`, `gpt-6.1-terra`, `gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`), car ces modèles rejettent `/chat/completions` pour le trafic des agents. Les modèles sans valeur intégrée par défaut, comme `gpt-5.4-nano`, peuvent être activés ici. Les services en amont à protocole unique et le transfert canonique ChatGPT rejettent ces remplacements. | | Activation Responses xAI (tableau de bord) | interrupteur | Pour `xai` uniquement, définit ou efface atomiquement les entrées `modelAdapters` de `grok-4.5` et `grok-4.6`. Une seule entrée apparaît comme un état mixte jusqu’à la prochaine écriture. Les autres remplacements et le comportement des tiers restent inchangés. Grok 4.7 utilise Responses par défaut sur OAuth via le registre et peut passer à Chat avec une entrée explicite `modelAdapters["grok-4.7"] = "openai-chat"`. | | `xaiResponsesXSearch?` | `boolean` | Désactivé par défaut. Sur une destination xAI Responses, ajoute la déclaration `x_search` hébergée par le fournisseur uniquement lorsqu’un outil `web_search` actif subsiste après la normalisation finale de la requête. Les déclarations existantes ne sont pas dupliquées, les sélecteurs `tool_choice`/`allowed_tools` de l’appelant ne sont jamais élargis, et cette option est distincte des options `search.xSearch` du service auxiliaire de recherche web. | | `modelPreferHostedTools?` | `Record` | Activation explicite par modèle exact pour les passerelles Responses hors transfert qui réservent un espace de noms aux outils hébergés. Seul `["image_generation"]` est actuellement accepté ; le modèle correspondant doit utiliser le protocole `openai-responses` et prendre en charge cet outil hébergé. Le proxy supprime les déclarations clientes `image_gen` en conflit et réécrit leurs sélecteurs afin de préserver le choix d'outil de l'appelant. Pour les modèles virtuels `-pro` de l'API OpenAI, l'identifiant public sélectionné est comparé en premier et l'identifiant résolu du modèle de base sur le protocole sert de repli. `modelAdapters` résout d'abord l'identifiant public, puis celui de base ; la seconde résolution détermine le protocole final. Les autres modèles conservent le comportement normal des alias. | diff --git a/docs-site/src/content/docs/fr/reference/configuration/routing.md b/docs-site/src/content/docs/fr/reference/configuration/routing.md index 3b0fc9e6cf9..6179222454f 100644 --- a/docs-site/src/content/docs/fr/reference/configuration/routing.md +++ b/docs-site/src/content/docs/fr/reference/configuration/routing.md @@ -5,6 +5,8 @@ description: Sélection du fournisseur par défaut, ordre de résolution des mod Le routage transforme l’identifiant de modèle envoyé par un client en un fournisseur concret et un modèle en amont. +Vous pouvez aussi choisir `gpt-6.1-terra` aux côtés de `gpt-5.6-terra`, sans modifier le modèle par défaut ni la liste des sous-agents. Voir les [limites, le raisonnement et le mode Fast de GPT-6.1 Terra](/fr/reference/configuration/providers/#gpt-61-terra). + ## Champs de routage de premier niveau | Champ | Type | Valeur par défaut | Signification | diff --git a/docs-site/src/content/docs/getting-started/quickstart.md b/docs-site/src/content/docs/getting-started/quickstart.md index ed39e7005e5..4dbe7a150d7 100644 --- a/docs-site/src/content/docs/getting-started/quickstart.md +++ b/docs-site/src/content/docs/getting-started/quickstart.md @@ -5,6 +5,8 @@ description: Configure your first provider and route OpenAI Codex through openco This guide takes you from a fresh install to running Codex against a non-OpenAI model. +You can also select `gpt-6.1-terra` alongside `gpt-5.6-terra`; it does not replace any default or sub-agent roster entry. See [GPT-6.1 Terra limits, reasoning and Fast](/reference/configuration/providers/#gpt-61-terra). + ## Standalone binary (no npm) You can also use a release archive containing the `ocx` binary and Bun runtime without npm. diff --git a/docs-site/src/content/docs/guides/codex-app-models.md b/docs-site/src/content/docs/guides/codex-app-models.md index 2a04b4dcc19..b7dac9a0a70 100644 --- a/docs-site/src/content/docs/guides/codex-app-models.md +++ b/docs-site/src/content/docs/guides/codex-app-models.md @@ -118,6 +118,8 @@ cp ~/.opencodex/config.json.pre-openai-tiers-v2.bak ~/.opencodex/config.json Earlier v1 three-provider configurations migrate automatically into the single option-aware row. +You can also select `gpt-6.1-terra` alongside `gpt-5.6-terra`; it does not replace any default or sub-agent roster entry. See [GPT-6.1 Terra limits, reasoning and Fast](/reference/configuration/providers/#gpt-61-terra). + ## Desktop remote-allowlist limitation If `codex debug models` and app-server `model/list` contain a routed model but Desktop does not show @@ -221,11 +223,12 @@ metadata instead of an older-template approximation. | Route | Picker ids and catalog metadata | | --- | --- | -| Codex login (account-qualified rows disabled) | Bare native ids such as `gpt-5.6-sol`, `gpt-5.6-terra`, and `gpt-5.6-luna`; Pool or Direct is selected through `codexAccountMode`. GPT-5.6 rows use a 922,000-token catalog window. | +| Codex login (account-qualified rows disabled) | Bare native ids such as `gpt-5.6-sol`, `gpt-5.6-terra`, and `gpt-5.6-luna`; Pool or Direct is selected through `codexAccountMode`. GPT-5.6 rows use a 922,000-token catalog window. `gpt-6.1-terra`: 500,000 default / 872,000 long context. | | Codex login (account-qualified rows enabled with eligible selectors) | One `/` row per eligible selector and supported native model; each row uses only its mapped account, and bare native rows are hidden from the picker. Native metadata and context windows are preserved. | | Codex login (explicit Daybreak forward row) | `openai/gpt-daybreak-blue-latest` only when the exact `customModels` row is configured on the canonical `openai` provider. It keeps the Daybreak wire id and uses the pinned Sol capability snapshot (922,000 context; 829,800 automatic compaction). | -| OpenAI (API key) | Exactly ten namespaced rows: `gpt-5.5`, `gpt-5.6`, Sol/Terra/Luna, the three `*-pro` virtual ids, and the two Daybreak aliases (1,050,000 context; 922,000 max input for all ten) | +| OpenAI (API key) | Namespaced models include `gpt-5.5`, `gpt-5.6`, Sol/Terra/Luna, the `*-pro` virtual ids and the Daybreak aliases (1,050,000 context; 922,000 max input). `openai-apikey/gpt-6.1-terra` adds 1,050,000 context and 128,000 max output. | | OpenRouter | `openrouter/openai/gpt-5.6-sol`, `openrouter/openai/gpt-5.6-terra`, `openrouter/openai/gpt-5.6-luna` (922,000) | +| OpenRouter | `openrouter/openai/gpt-6.1-terra` (1,050,000) | | Cursor | Static fallback includes `cursor/gpt-5.6-sol`, `cursor/gpt-5.6-terra`, and `cursor/gpt-5.6-luna` (1,000,000), plus regular/Fast rows for Grok 4.5, 4.6, and 4.7 (500,000); 4.6 and 4.7 add `xhigh`, and live account discovery decides which rows remain visible. | | xAI | Live discovery is authoritative. The fallback catalog includes `xai/grok-4.6` and `xai/grok-4.7` and defaults to `xai/grok-4.5`; all three have 500,000-token windows. Grok 4.6 and 4.7 expose `low` / `medium` / `high` / `xhigh` (upstream default: `high`), while Grok 4.5 stops at `high`. | @@ -279,7 +282,7 @@ On the wire, routed adapters map or clamp unsupported tiers. For older native mo ladder stops at `xhigh`, `nativeEffortClamp` maps a direct `max` or an `ultra` selection to `xhigh` (for example, GPT-5.5). Sol, Terra, and Luna have a real `max` rung. The ChatGPT backend itself accepts `none` through `max`, so a native ChatGPT request never forwards `ultra` as-is: -native models with a real `max` rung receive `max`, including Astra and GPT-6.1 Sol whose ladders +native models with a real `max` rung receive `max`, including Astra, GPT-6.1 Sol and GPT-6.1 Terra whose ladders list `ultra`, while older models such as GPT-5.5 receive `xhigh` as above. This applies to `/v1/responses` and `/v1/chat/completions` alike. The native clamp does not apply to routed model IDs: a routed OpenAI Chat passthrough can copy a declared `reasoning_effort: "ultra"` to its provider unchanged, diff --git a/docs-site/src/content/docs/guides/model-ordering.md b/docs-site/src/content/docs/guides/model-ordering.md index b3ca4772592..49a33e52732 100644 --- a/docs-site/src/content/docs/guides/model-ordering.md +++ b/docs-site/src/content/docs/guides/model-ordering.md @@ -7,6 +7,8 @@ The Codex model picker does not preserve the order of provider declarations or m opencodex configuration. Its final order comes from catalog priorities, with a deterministic alphabetical order for routed models that share the same priority. +You can also select `gpt-6.1-terra` alongside `gpt-5.6-terra`; it does not replace any default or sub-agent roster entry. See [GPT-6.1 Terra limits, reasoning and Fast](/reference/configuration/providers/#gpt-61-terra). + ## The rule Codex applies Codex's models-manager sorts picker-visible catalog entries by `priority` in ascending order. It diff --git a/docs-site/src/content/docs/guides/providers.md b/docs-site/src/content/docs/guides/providers.md index 0238f96993b..806964cda7d 100644 --- a/docs-site/src/content/docs/guides/providers.md +++ b/docs-site/src/content/docs/guides/providers.md @@ -13,6 +13,8 @@ These links preserve the preset's referral parameters. Sponsor information is sh the configured provider name, adapter and endpoint match the preset; it never changes routing, account selection or defaults. +You can also select `gpt-6.1-terra` alongside `gpt-5.6-terra`; it does not replace any default or sub-agent roster entry. See [GPT-6.1 Terra limits, reasoning and Fast](/reference/configuration/providers/#gpt-61-terra). + ## OpenAI account modes | Provider id | Use | Credential/account rule | @@ -845,12 +847,14 @@ The preset uses [Chat Completions](https://tokenlab.sh/docs/en/quickstart) and d `GET /v1/models?category=chat`, keeping only entries that declare `tool-use` capability. Image, video, audio, embedding and decision models are excluded from this chat preset. + + Each model then uses the request format TokenLab declares for it (`tokenlab.accepted_request_formats` on `GET /v1/models/{model}`): | Models | Codex (Responses clients) | Chat clients | Claude Code (Anthropic clients) | | --- | --- | --- | --- | -| `gpt-6-astra`, `gpt-6.1-sol`, `gpt-6-sol`, `gpt-6-luna`, `grok-4.7`, `deepseek-v4.1-flash`, `deepseek-v4-pro`, `kimi-k3`, `glm-5.3` | [Responses](https://tokenlab.sh/docs/en/api-reference/responses/create-response) | Chat Completions | Chat Completions | +| `gpt-6-astra`, `gpt-6.1-sol`, `gpt-6.1-terra`, `gpt-6-sol`, `gpt-6-luna`, `grok-4.7`, `deepseek-v4.1-flash`, `deepseek-v4-pro`, `kimi-k3`, `glm-5.3` | [Responses](https://tokenlab.sh/docs/en/api-reference/responses/create-response) | Chat Completions | Chat Completions | | `claude-*` | [Messages](https://tokenlab.sh/docs/en/api-reference/messages/create-message) | Messages | Messages | | Every other model, including `gemini-3.8-flash` | Chat Completions | Chat Completions | Chat Completions | @@ -871,9 +875,12 @@ picker and marks it as a sponsor, and nothing else about routing or defaults cha **Modelflare** is an OpenAI-compatible relay at `https://modelflare.dev/v1`. Select **Modelflare** in `ocx init` or the dashboard's **Add provider** picker, or run `ocx provider add modelflare`, and give it your key directly or as the reference `${MODELFLARE_API_KEY}` so the key stays in your -environment. The preset uses Chat Completions and seeds four models that +environment. The preset uses Chat Completions. The following existing models were verified with chat, streaming and tool calls: `glm-5.3-flash` (the default), -`claude-sonnet-5-5`, `gpt-6.1-sol` and `deepseek-v4-flash`. You can add other Chat-compatible +`claude-sonnet-5-5`, `gpt-6.1-sol` and `deepseek-v4-flash`. +`gpt-6.1-terra` is a preemptive seed mirroring Sol; it has not been inference-verified here. + +You can add other Chat-compatible Modelflare models as custom models. Image and video models use separate Modelflare endpoints and do not work through this Chat preset. An ordinary Modelflare key is bound to one routing group and can call only that group's models, so use a Smart key for the full seeded set, or pass @@ -1584,6 +1591,9 @@ visible even while live catalogs lag: | Codex login (Pool or Direct) | `gpt-5.6-*` | 922,000 | | OpenAI (API key) | `openai-apikey/gpt-5.6-*` plus `*-pro` | 922,000 (922,000 max input) | | OpenRouter | `openrouter/openai/gpt-5.6-sol`, `openrouter/openai/gpt-5.6-terra`, `openrouter/openai/gpt-5.6-luna` | 922,000 | +| Codex | `gpt-6.1-terra` | 500,000 / 872,000 | +| OpenAI API | `openai-apikey/gpt-6.1-terra` | 1,050,000 (128,000 max output) | +| OpenRouter | `openrouter/openai/gpt-6.1-terra` | 1,050,000 | | Cursor | `cursor/gpt-5.6-sol`, `cursor/gpt-5.6-terra`, `cursor/gpt-5.6-luna` | 1,000,000 | The native GPT-5.6 entries preserve the pinned upstream reasoning ladders (for example, Luna has @@ -1630,7 +1640,7 @@ seconds per call, including pacing and body reads. These are OpenCodex safeguard GitHub limits; oversized catalogs, slow negotiation or a truncated intent excerpt can affect compatibility. For named selections, Copilot fronts a mixed-wire catalog: the following models (`gpt-5.3-codex`, `gpt-5.4`, -`gpt-5.4-mini`, `gpt-5.5`, `gpt-5.6-luna`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`) reject +`gpt-5.4-mini`, `gpt-5.5`, `gpt-5.6-luna`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-6.1-sol`, `gpt-6.1-terra`, `gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`) reject `/chat/completions` for agent traffic, so opencodex routes those models over the Responses API by built-in default while every other Copilot model stays on chat completions. The precedence is: hard wire pin → your explicit diff --git a/docs-site/src/content/docs/ja/getting-started/quickstart.md b/docs-site/src/content/docs/ja/getting-started/quickstart.md index 216e3891dac..62759e3710a 100644 --- a/docs-site/src/content/docs/ja/getting-started/quickstart.md +++ b/docs-site/src/content/docs/ja/getting-started/quickstart.md @@ -5,6 +5,8 @@ description: 最初のプロバイダーを構成し、3 つのコマンドで O このガイドでは、新規インストールから非 OpenAI モデルに対して Codex を実行するまでを説明します。 +`gpt-5.6-terra` に加えて `gpt-6.1-terra` も選択できます。既定モデルやサブエージェントのモデル一覧は変わりません。[GPT-6.1 Terra の上限・推論・Fast](/ja/reference/configuration/providers/#gpt-61-terra)を参照してください。 + ## スタンドアロンバイナリ（npm 不要） npm を使わず、Bun ランタイムを含むリリースアーカイブの `ocx` バイナリも利用できます。 diff --git a/docs-site/src/content/docs/ja/guides/codex-app-models.md b/docs-site/src/content/docs/ja/guides/codex-app-models.md index 63d62a27364..28d6c1c946b 100644 --- a/docs-site/src/content/docs/ja/guides/codex-app-models.md +++ b/docs-site/src/content/docs/ja/guides/codex-app-models.md @@ -30,6 +30,8 @@ cp ~/.opencodex/config.json.pre-openai-tiers-v2.bak ~/.opencodex/config.json 以前の v1 の 3 プロバイダー設定は、単一のオプション対応行に自動的に移行されます。 +`gpt-5.6-terra` に加えて `gpt-6.1-terra` も選択できます。既定モデルやサブエージェントのモデル一覧は変わりません。[GPT-6.1 Terra の上限・推論・Fast](/ja/reference/configuration/providers/#gpt-61-terra)を参照してください。 + ## 統合パス `ocx init`、`ocx start`、および `ocx sync` は、共有 Codex 設定とカタログをプロキシに接続します。設定の挿入、カタログの同期、シム、WebSocket フォールバック、および復元の仕組みについては、[Codexの統合](/guides/codex-integration/) を参照してください。 @@ -52,10 +54,11 @@ visibility = "list" |ルート |ピッカー ID とカタログのメタデータ | | --- | --- | -| Codex ログイン (account-qualified 行が無効) | `gpt-5.6-sol`、`gpt-5.6-terra`、`gpt-5.6-luna` などの bare native id を表示し、`codexAccountMode` に従って Pool または Direct を使用します。GPT-5.6 行のカタログ ウィンドウは 922,000 トークンです。 | +| Codex ログイン (account-qualified 行が無効) | `gpt-5.6-sol`、`gpt-5.6-terra`、`gpt-5.6-luna` などの bare native id を表示し、`codexAccountMode` に従って Pool または Direct を使用します。GPT-5.6 行のカタログ ウィンドウは 922,000 トークンです。 `gpt-6.1-terra`：既定 500,000 / 長文 872,000。 | | Codex ログイン (account-qualified 行が有効で、有効な selector あり) | 有効な selector とサポート対象 native model の各組み合わせに `/` 行を表示します。各行は対応付けられたアカウントだけを使用し、bare native 行はピッカーで非表示になります。Native metadata と context window は保持されます。 | -| OpenAI (API キー) |正確に 8 つの名前空間行: `gpt-5.5`、`gpt-5.6`、Sol/Terra/Luna、および 3 つの `*-pro` 仮想 ID (コンテキスト 922,000、8 つすべての最大入力 922,000) | +| OpenAI (API キー) | 名前空間付きモデルには `gpt-5.5`、`gpt-5.6`、Sol/Terra/Luna、`*-pro` 仮想 ID、Daybreak エイリアスが含まれます（コンテキスト 1,050,000、最大入力 922,000）。`openai-apikey/gpt-6.1-terra` はコンテキスト 1,050,000、最大出力 128,000 です。 | |オープンルーター | `openrouter/openai/gpt-5.6-sol`、`openrouter/openai/gpt-5.6-terra`、`openrouter/openai/gpt-5.6-luna` (922,000) | +| OpenRouter | `openrouter/openai/gpt-6.1-terra` (1,050,000) | | Cursor | 静的フォールバックには `cursor/gpt-5.6-sol`、`cursor/gpt-5.6-terra`、`cursor/gpt-5.6-luna` (1,000,000) と、Grok 4.5 / 4.6 / 4.7 の通常・Fast 行 (500,000) が含まれます。4.6 と 4.7 は `xhigh` も公開し、ライブアカウントの検出によって表示される行が決まります。 | | xAI | xAI のライブ検出が優先されます。フォールバックには `xai/grok-4.6` と `xai/grok-4.7` が含まれ、デフォルトは `xai/grok-4.5` です。3 モデルともコンテキストは 500,000 トークンです。Grok 4.6 と 4.7 は `low` / `medium` / `high` / `xhigh`（上流のデフォルトは `high`）を提供し、Grok 4.5 は `high` までです。 | diff --git a/docs-site/src/content/docs/ja/guides/model-ordering.md b/docs-site/src/content/docs/ja/guides/model-ordering.md index 74febb1e782..af4c32c0057 100644 --- a/docs-site/src/content/docs/ja/guides/model-ordering.md +++ b/docs-site/src/content/docs/ja/guides/model-ordering.md @@ -7,6 +7,8 @@ Codex モデルピッカーは opencodex 設定に書かれたプロバイダー 最終順序はカタログ priority で決まり、同じ priority を持つルーティングモデルには決定論的 アルファベット順ソートが適用されます。 +`gpt-5.6-terra` に加えて `gpt-6.1-terra` も選択できます。既定モデルやサブエージェントのモデル一覧は変わりません。[GPT-6.1 Terra の上限・推論・Fast](/ja/reference/configuration/providers/#gpt-61-terra)を参照してください。 + ## Codex が適用するルール Codex の models-manager はピッカーに表示されるカタログ項目を `priority` 昇順でソートします。 diff --git a/docs-site/src/content/docs/ja/guides/providers.md b/docs-site/src/content/docs/ja/guides/providers.md index 39fec41d0ca..ab15df10ce7 100644 --- a/docs-site/src/content/docs/ja/guides/providers.md +++ b/docs-site/src/content/docs/ja/guides/providers.md @@ -6,6 +6,8 @@ description: opencodex が LLM プロバイダーを認証し通信するすべ **プロバイダー**は一つの上流 LLM エンドポイントとそこへの到達方法を合わせたものです: アダプター、ベース URL、認証 モード、そしてオプションのモデル一覧で構成されます。プロバイダーは `~/.opencodex/config.json` の `providers` の下にあります。 +`gpt-5.6-terra` に加えて `gpt-6.1-terra` も選択できます。既定モデルやサブエージェントのモデル一覧は変わりません。[GPT-6.1 Terra の上限・推論・Fast](/ja/reference/configuration/providers/#gpt-61-terra)を参照してください。 + ## OpenAI アカウントモード | プロバイダー ID | 用途 | 認証情報/アカウットルール | @@ -465,6 +467,9 @@ Sol/Terra/Luna をフォールバックリストに入れています。 | Codex ログイン(Pool または Direct) | `gpt-5.6-*` | 922,000 | | OpenAI (API キー) | `openai-apikey/gpt-5.6-*` と `*-pro` | 922,000 (max input 922,000) | | OpenRouter | `openrouter/openai/gpt-5.6-sol`、`openrouter/openai/gpt-5.6-terra`、`openrouter/openai/gpt-5.6-luna` | 922,000 | +| Codex | `gpt-6.1-terra` | 500,000 / 872,000 | +| OpenAI API | `openai-apikey/gpt-6.1-terra` | 1,050,000 (128,000 max output) | +| OpenRouter | `openrouter/openai/gpt-6.1-terra` | 1,050,000 | | Cursor | `cursor/gpt-5.6-sol`、`cursor/gpt-5.6-terra`、`cursor/gpt-5.6-luna` | 1,000,000 | ネイティブ GPT-5.6 項目は固定の上流推論段階に従います。例えば Luna には @@ -484,7 +489,7 @@ Amazon Bedrock ネイティブ API のような、これらの実装のいずれ Gateway** は URL にアカウント + ゲートウェイ ID を埋める必要があります。 Copilot は混在 wire カタログを提供します。モデル（`gpt-5.3-codex`、`gpt-5.4`、 -`gpt-5.4-mini`、`gpt-5.5`、`gpt-5.6-luna`、`gpt-5.6-sol`、`gpt-5.6-terra`、`gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`）はエージェント +`gpt-5.4-mini`、`gpt-5.5`、`gpt-5.6-luna`、`gpt-5.6-sol`、`gpt-5.6-terra`、 `gpt-6.1-sol`、 `gpt-6.1-terra`、 `gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`）はエージェント 通信の `/chat/completions` を拒否するため、opencodex はこれらのモデルを組み込みデフォルトで Responses API 経由にルーティングし、他の Copilot モデルはすべて chat completions のままです。 優先順位は次のとおりです: ハード wire ピン → 明示的な diff --git a/docs-site/src/content/docs/ja/reference/adapters.md b/docs-site/src/content/docs/ja/reference/adapters.md index b817283250d..b2a2585812b 100644 --- a/docs-site/src/content/docs/ja/reference/adapters.md +++ b/docs-site/src/content/docs/ja/reference/adapters.md @@ -19,6 +19,8 @@ interface ProviderAdapter { `buildRequest` は `OcxParsedRequest` を上流の HTTP リクエストに落とし、`parseStream` / `parseResponse` はプロバイダーのレスポンスを内部 `AdapterEvent` に持ち上げます。`fetchResponse` があると、アダプターがリトライとタイムアウトを直接担います。`runTurn` は 1 回の HTTP fetch とその後のレスポンスストリームでは表現できない伝送方式をサポートします。その後 [`bridge.ts`](/ja/reference/architecture/#ブリッジ) がイベントを Responses SSE に変えます。 +`gpt-5.6-terra` に加えて `gpt-6.1-terra` も選択できます。既定モデルやサブエージェントのモデル一覧は変わりません。[GPT-6.1 Terra の上限・推論・Fast](/ja/reference/configuration/providers/#gpt-61-terra)を参照してください。 + ## `openai-chat` **対象:** OpenAI **Chat Completions**（`POST {baseUrl}/chat/completions`）および互換プロバイダー diff --git a/docs-site/src/content/docs/ja/reference/configuration/providers.md b/docs-site/src/content/docs/ja/reference/configuration/providers.md index b9b4816488e..fc82f872333 100644 --- a/docs-site/src/content/docs/ja/reference/configuration/providers.md +++ b/docs-site/src/content/docs/ja/reference/configuration/providers.md @@ -11,6 +11,16 @@ description: プロバイダー エントリ、認証、エンドポイント、 この推定は既定で無効です。プロバイダーごとに `inferContextWindow: true` で有効にします。未設定の場合、ウィンドウがないモデルは有効な Context cap、次に 128k を使います。 +## GPT-6.1 Terra + +[GPT-6.1 Terra](https://openai.com/index/introducing-gpt-6-1-terra/) は GPT-5.6 Terra の後継として 2026年10月26日に公開されました。`gpt-6.1-terra` は `gpt-5.6-terra` と並行して利用でき、既定モデルやサブエージェントのモデル一覧は変更しません。GitHub Copilot では Responses を使用します。OpenRouter の ID は `openai/gpt-6.1-terra` で、コンテキストは 1,050,000、100万トークンあたり入力 $1.00、出力 $5.00 です。 + +ネイティブ Codex：既定コンテキスト 500,000、長文コンテキスト上限 872,000、既定 effort は `low`。段階は `low`、`medium`、`high`、`xhigh`、`max`、`ultra` です。ネイティブの `ultra` は通信時に `max` として送信します。ネイティブ行の高速モードは Fast のみです。 + +[OpenAI API](https://developers.openai.com/api/docs/models/gpt-6.1-terra)：コンテキスト 1,050,000、最大出力 128,000。入力はテキストと画像、出力はテキスト。知識カットオフは 2026-06-01 です。effort は `none`、`low`、`medium`（既定）、`high`、`xhigh`、`max`。エンドポイントは `v1/responses` と `v1/chat/completions` ですが、ツール呼び出しには Responses が必要です。 + +100万トークンあたり入力 $1.00、キャッシュ入力 $0.05、キャッシュ書き込み $1.25（30分）、出力 $5.00。入力が 272,000 トークンを超える場合、リクエスト全体の入力・キャッシュは 2×、出力は 1.5× となり、それぞれ $2.00 / $0.10 / $2.50 / $7.50 です。Fast モードは 2× です。 + ## 初回登録時のモデル選択 新しい非 OAuth 接続では、信頼できるモデル一覧の取得が完了するまでモデルの公開を保留します。Models タブの重複しないモデル行が20個以上なら、モデルのスイッチをすべて OFF にします。プロバイダー自体は ACTIVE のままです。実際の認証方式が OAuth または ChatGPT ログインなら既定値を維持します。 @@ -126,7 +136,7 @@ account を削除しても mapping は保持され、同じ id を再追加す | `modelReasoningEfforts?` | `Record` |モデルごとのラベル。空のリストは努力制御を非表示にします。 | | `modelSupportsReasoningSummaries?` | `Record` |モデルを `false` に設定して、概要の広告を停止し、概要配信フィールドを削除します。 | | `modelReasoningSummaryDelivery?` | `Record` |モデルごとの応答配信列挙型。既存の配信フィールドを書き換えます。 | -| `modelAdapters?` | `Record` | 混合配線ゲートウェイのモデルごとの `openai-chat` または `openai-responses` 配線オーバーライド。明示的なエントリはレジストリのデフォルトを破ります。DeepSeek のプリセットは `deepseek-v4-flash` のネイティブ Responses を選択でき、GitHub Copilot は モデル (`gpt-5.3-codex`, `gpt-5.4`, `gpt-5.4-mini`, `gpt-5.5`, `gpt-5.6-luna`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`) を Responses 専用デフォルトとして宣言します。これらのモデルはエージェント トラフィックで `/chat/completions` を拒否するためです。`gpt-5.4-nano` のようなビルトイン デフォルトのないモデルはここでオプトインできます。単線アップストリーム ピンと正規の ChatGPT 転送はオーバーライドを拒否します。 | +| `modelAdapters?` | `Record` | 混合配線ゲートウェイのモデルごとの `openai-chat` または `openai-responses` 配線オーバーライド。明示的なエントリはレジストリのデフォルトを破ります。DeepSeek のプリセットは `deepseek-v4-flash` のネイティブ Responses を選択でき、GitHub Copilot は モデル (`gpt-5.3-codex`, `gpt-5.4`, `gpt-5.4-mini`, `gpt-5.5`, `gpt-5.6-luna`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-6.1-sol`, `gpt-6.1-terra`, `gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`) を Responses 専用デフォルトとして宣言します。これらのモデルはエージェント トラフィックで `/chat/completions` を拒否するためです。`gpt-5.4-nano` のようなビルトイン デフォルトのないモデルはここでオプトインできます。単線アップストリーム ピンと正規の ChatGPT 転送はオーバーライドを拒否します。 | | xAI Responses オプトイン（ダッシュボード） | スイッチ | `xai` のみで、`grok-4.5` と `grok-4.6` の `modelAdapters` エントリを原子的に設定または削除します。片方だけの場合は、次のスイッチ操作で両方が正規化されるまで混合状態を表示します。他のオーバーライドと tier 動作は変わりません。 Grok 4.7 は OAuth でレジストリの既定値により Responses を使用し、明示的な `modelAdapters["grok-4.7"] = "openai-chat"` で Chat に切り替えられます。 | | `xaiResponsesXSearch?` | `boolean` | デフォルトでは無効です。xAI Responses の宛先では、最終的なリクエスト正規化後もライブの `web_search` ツールが残っている場合にのみ、プロバイダーがホストする `x_search` 宣言を追加します。既存の宣言は重複させず、呼び出し元の `tool_choice` / `allowed_tools` セレクターの範囲を拡張することもありません。また、これは `search.xSearch` オプションを持つウェブ検索サイドカーとは別です。 | | `modelPreferHostedTools?` | `Record` | hosted tool namespace を予約する非 forward Responses gateway 向けの完全一致モデル opt-in。現在は `["image_generation"]` のみを受け付けます。一致したモデルは `openai-responses` wire を使い、その hosted tool をサポートする必要があります。競合するクライアント `image_gen` 宣言を除去し、呼び出し元の tool choice を維持するため selector も書き換えます。OpenAI API の仮想 `-pro` モデルでは、まず選択した公開 ID に一致させ、解決後のベース wire-model ID をフォールバックとして使用します。`modelAdapters` は公開 ID、次にベース ID の順に解決し、後者の結果が最終 wire を決めます。未設定のモデルは通常の alias 動作を維持します。 | diff --git a/docs-site/src/content/docs/ja/reference/configuration/routing.md b/docs-site/src/content/docs/ja/reference/configuration/routing.md index 99ff0bfb3b3..5111850779c 100644 --- a/docs-site/src/content/docs/ja/reference/configuration/routing.md +++ b/docs-site/src/content/docs/ja/reference/configuration/routing.md @@ -5,6 +5,8 @@ description: デフォルトのプロバイダーの選択、モデルの解決 ルーティングは、クライアントから送信されたモデル ID を 1 つの具体的なプロバイダーと上流モデルに変換します。 +`gpt-5.6-terra` に加えて `gpt-6.1-terra` も選択できます。既定モデルやサブエージェントのモデル一覧は変わりません。[GPT-6.1 Terra の上限・推論・Fast](/ja/reference/configuration/providers/#gpt-61-terra)を参照してください。 + ## トップレベルのルーティングフィールド |フィールド |タイプ |デフォルト |意味 | diff --git a/docs-site/src/content/docs/ko/getting-started/quickstart.md b/docs-site/src/content/docs/ko/getting-started/quickstart.md index 77cc5a35d1e..420b59217ea 100644 --- a/docs-site/src/content/docs/ko/getting-started/quickstart.md +++ b/docs-site/src/content/docs/ko/getting-started/quickstart.md @@ -5,6 +5,8 @@ description: 첫 프로바이더를 설정하고 명령어 세 개로 OpenAI Cod 이 가이드는 새로 설치한 상태에서 OpenAI가 아닌 모델로 Codex를 실행하기까지의 과정을 안내합니다. +`gpt-5.6-terra`와 함께 `gpt-6.1-terra`도 선택할 수 있습니다. 기본 모델이나 하위 에이전트 모델 목록은 바뀌지 않습니다. [GPT-6.1 Terra 한도·추론·Fast](/ko/reference/configuration/providers/#gpt-61-terra)를 참고하세요. + ## 독립 실행형 바이너리(npm 없음) npm 없이 Bun 런타임이 포함된 릴리스 아카이브의 `ocx` 바이너리를 사용할 수도 있습니다. diff --git a/docs-site/src/content/docs/ko/guides/codex-app-models.md b/docs-site/src/content/docs/ko/guides/codex-app-models.md index 60b38ca4c9c..1f4de5b15d9 100644 --- a/docs-site/src/content/docs/ko/guides/codex-app-models.md +++ b/docs-site/src/content/docs/ko/guides/codex-app-models.md @@ -74,6 +74,8 @@ cp ~/.opencodex/config.json.pre-openai-tiers-v2.bak ~/.opencodex/config.json 이전 v1의 3-provider 설정은 자동으로 옵션을 인식하는 단일 행으로 마이그레이션됩니다. +`gpt-5.6-terra`와 함께 `gpt-6.1-terra`도 선택할 수 있습니다. 기본 모델이나 하위 에이전트 모델 목록은 바뀌지 않습니다. [GPT-6.1 Terra 한도·추론·Fast](/ko/reference/configuration/providers/#gpt-61-terra)를 참고하세요. + ## 통합 경로 `ocx init`, `ocx start`, `ocx sync`는 공유 Codex 설정과 카탈로그를 프록시에 연결합니다. 설정 주입, @@ -104,11 +106,12 @@ GPT-5.6에만 사용합니다. 오래된 템플릿으로 근사하지 않고 모 | 경로 | 선택기 id와 카탈로그 메타데이터 | | --- | --- | -| Codex 로그인(계정 한정 선택기 행 비활성) | `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-5.6-luna` 같은 bare native id를 표시하고 `codexAccountMode`에 따라 Pool 또는 Direct를 사용합니다. GPT-5.6 행의 카탈로그 창은 922,000토큰입니다. | +| Codex 로그인(계정 한정 선택기 행 비활성) | `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-5.6-luna` 같은 bare native id를 표시하고 `codexAccountMode`에 따라 Pool 또는 Direct를 사용합니다. GPT-5.6 행의 카탈로그 창은 922,000토큰입니다. `gpt-6.1-terra`: 기본 500,000 / 장문 872,000. | | Codex 로그인(계정 한정 선택기 행 활성, 유효한 selector 있음) | 유효한 selector와 지원되는 native model의 각 조합마다 `/` 행을 표시합니다. 각 행은 매핑된 계정만 사용하며 bare native 행은 선택기에서 숨깁니다. Native metadata와 context window는 보존됩니다. | | Codex 로그인(명시적 Daybreak forward 행) | canonical `openai` provider에 정확한 `customModels` 항목이 있을 때만 `openai/gpt-daybreak-blue-latest`를 표시합니다. Daybreak wire id를 유지하고 고정된 Sol capability snapshot(컨텍스트 922,000; 자동 압축점 922,000)을 사용합니다. | -| OpenAI(API key) | 정확히 열 개의 네임스페이스 행: `gpt-5.5`, `gpt-5.6`, Sol/Terra/Luna, 세 개의 `*-pro` 가상 id, 두 Daybreak 별칭 (모두 컨텍스트 922,000; 최대 입력 922,000) | +| OpenAI(API key) | 네임스페이스 모델에는 `gpt-5.5`, `gpt-5.6`, Sol/Terra/Luna, `*-pro` 가상 id, Daybreak 별칭이 포함됩니다(컨텍스트 1,050,000; 최대 입력 922,000). `openai-apikey/gpt-6.1-terra`는 컨텍스트 1,050,000, 최대 출력 128,000입니다. | | OpenRouter | `openrouter/openai/gpt-5.6-sol`, `openrouter/openai/gpt-5.6-terra`, `openrouter/openai/gpt-5.6-luna` (922,000) | +| OpenRouter | `openrouter/openai/gpt-6.1-terra` (1,050,000) | | Cursor | 정적 폴백에는 `cursor/gpt-5.6-sol`, `cursor/gpt-5.6-terra`, `cursor/gpt-5.6-luna` (1,000,000)와 Grok 4.5/4.6/4.7의 일반·Fast 항목(500,000)이 들어갑니다. 4.6과 4.7은 `xhigh`도 노출하며, 실시간 계정 탐색이 어떤 항목을 계속 보일지 정합니다. | | xAI | 실시간 탐색이 기준입니다. 폴백 카탈로그에는 `xai/grok-4.6`과 `xai/grok-4.7`이 포함되며 기본값은 `xai/grok-4.5`입니다. 세 모델 모두 컨텍스트 창은 500,000입니다. Grok 4.6과 4.7은 `low` / `medium` / `high` / `xhigh`(업스트림 기본값: `high`)를 제공하고, Grok 4.5는 `high`까지만 제공합니다. | diff --git a/docs-site/src/content/docs/ko/guides/model-ordering.md b/docs-site/src/content/docs/ko/guides/model-ordering.md index e921bfdfbcd..47ad18bcf4c 100644 --- a/docs-site/src/content/docs/ko/guides/model-ordering.md +++ b/docs-site/src/content/docs/ko/guides/model-ordering.md @@ -7,6 +7,8 @@ Codex 모델 선택기는 opencodex 설정에 적힌 프로바이더 선언 순 않습니다. 최종 순서는 카탈로그 priority로 정해지며, 같은 priority를 가진 라우팅 모델에는 결정적인 알파벳순 정렬이 적용됩니다. +`gpt-5.6-terra`와 함께 `gpt-6.1-terra`도 선택할 수 있습니다. 기본 모델이나 하위 에이전트 모델 목록은 바뀌지 않습니다. [GPT-6.1 Terra 한도·추론·Fast](/ko/reference/configuration/providers/#gpt-61-terra)를 참고하세요. + ## Codex가 적용하는 규칙 Codex의 models-manager는 선택기에 표시되는 카탈로그 항목을 `priority` 오름차순으로 정렬합니다. diff --git a/docs-site/src/content/docs/ko/guides/providers.md b/docs-site/src/content/docs/ko/guides/providers.md index 4cb0c110238..14644b5d919 100644 --- a/docs-site/src/content/docs/ko/guides/providers.md +++ b/docs-site/src/content/docs/ko/guides/providers.md @@ -6,6 +6,8 @@ description: opencodex가 LLM 프로바이더를 인증하고 통신하는 모 **프로바이더**는 하나의 업스트림 LLM 엔드포인트와 거기에 도달하는 방법을 합친 것입니다: 어댑터, 베이스 URL, 인증 모드, 그리고 선택적인 모델 목록으로 구성됩니다. 프로바이더는 `~/.opencodex/config.json`의 `providers` 아래에 위치합니다. +`gpt-5.6-terra`와 함께 `gpt-6.1-terra`도 선택할 수 있습니다. 기본 모델이나 하위 에이전트 모델 목록은 바뀌지 않습니다. [GPT-6.1 Terra 한도·추론·Fast](/ko/reference/configuration/providers/#gpt-61-terra)를 참고하세요. + ## OpenAI 계정 모드 | 프로바이더 id | 용도 | 자격증명/계정 규칙 | @@ -471,6 +473,9 @@ Sol/Terra/Luna를 폴백 목록에 넣어 둡니다. | Codex 로그인(Pool 또는 Direct) | `gpt-5.6-*` | 922,000 | | OpenAI (API key) | `openai-apikey/gpt-5.6-*`와 `*-pro` | 922,000 (max input 922,000) | | OpenRouter | `openrouter/openai/gpt-5.6-sol`, `openrouter/openai/gpt-5.6-terra`, `openrouter/openai/gpt-5.6-luna` | 922,000 | +| Codex | `gpt-6.1-terra` | 500,000 / 872,000 | +| OpenAI API | `openai-apikey/gpt-6.1-terra` | 1,050,000 (128,000 max output) | +| OpenRouter | `openrouter/openai/gpt-6.1-terra` | 1,050,000 | | Cursor | `cursor/gpt-5.6-sol`, `cursor/gpt-5.6-terra`, `cursor/gpt-5.6-luna` | 1,000,000 | 네이티브 GPT-5.6 항목은 고정된 업스트림 reasoning 단계를 그대로 따릅니다. 예를 들어 Luna에는 @@ -491,7 +496,7 @@ Amazon Bedrock 네이티브 API처럼 이 구현 중 어느 것과도 맞지 않 Gateway**는 URL에 계정 + 게이트웨이 id를 채워야 합니다. Copilot은 혼합 wire 카탈로그를 제공합니다. 모델(`gpt-5.3-codex`, `gpt-5.4`, -`gpt-5.4-mini`, `gpt-5.5`, `gpt-5.6-luna`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`)은 에이전트 +`gpt-5.4-mini`, `gpt-5.5`, `gpt-5.6-luna`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-6.1-sol`, `gpt-6.1-terra`, `gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`)은 에이전트 트래픽에 대해 `/chat/completions`를 거부하므로 opencodex는 이 모델들을 내장 기본값으로 Responses API를 통해 라우팅하고, 다른 Copilot 모델은 모두 chat completions를 유지합니다. 우선순위는 하드 wire 핀 → 명시적 [`modelAdapters`](/ko/reference/configuration/providers/) diff --git a/docs-site/src/content/docs/ko/reference/adapters.md b/docs-site/src/content/docs/ko/reference/adapters.md index 546a0dea6eb..b9acbf7f5ad 100644 --- a/docs-site/src/content/docs/ko/reference/adapters.md +++ b/docs-site/src/content/docs/ko/reference/adapters.md @@ -23,6 +23,8 @@ interface ProviderAdapter { 스트림으로 표현할 수 없는 전송 방식을 지원합니다. 이후 [`bridge.ts`](/ko/reference/architecture/#브리지)가 이벤트를 Responses SSE로 바꿉니다. +`gpt-5.6-terra`와 함께 `gpt-6.1-terra`도 선택할 수 있습니다. 기본 모델이나 하위 에이전트 모델 목록은 바뀌지 않습니다. [GPT-6.1 Terra 한도·추론·Fast](/ko/reference/configuration/providers/#gpt-61-terra)를 참고하세요. + ## `openai-chat` **대상:** OpenAI **Chat Completions**(`POST {baseUrl}/chat/completions`)와 모든 호환 프로바이더 diff --git a/docs-site/src/content/docs/ko/reference/configuration/providers.md b/docs-site/src/content/docs/ko/reference/configuration/providers.md index 0fc58dc0558..6a0a43ef73b 100644 --- a/docs-site/src/content/docs/ko/reference/configuration/providers.md +++ b/docs-site/src/content/docs/ko/reference/configuration/providers.md @@ -11,6 +11,16 @@ description: 공급자 항목, 인증, 엔드포인트, 모델 카탈로그, 할 이 추정은 기본적으로 꺼져 있습니다. 공급자별로 `inferContextWindow: true`를 설정해야 켜집니다. 설정하지 않으면 창이 없는 모델은 활성 Context cap, 그다음 128k를 사용합니다. +## GPT-6.1 Terra + +[GPT-6.1 Terra](https://openai.com/index/introducing-gpt-6-1-terra/)는 GPT-5.6 Terra의 후속 모델로 2026년 10월 26일 출시되었습니다. `gpt-6.1-terra`는 `gpt-5.6-terra`와 함께 제공하며 기본 모델이나 하위 에이전트 모델 목록은 바꾸지 않습니다. GitHub Copilot에서는 Responses를 사용합니다. OpenRouter ID는 `openai/gpt-6.1-terra`이며 컨텍스트는 1,050,000, 100만 토큰당 입력 $1.00 / 출력 $5.00입니다. + +네이티브 Codex: 기본 컨텍스트 500,000, 장문 상한 872,000, 기본 effort `low`, 단계는 `low`, `medium`, `high`, `xhigh`, `max`, `ultra`입니다. 네이티브 `ultra`는 전송 시 `max`로 변환합니다. 네이티브 행의 고속 모드는 Fast만 제공합니다. + +[OpenAI API](https://developers.openai.com/api/docs/models/gpt-6.1-terra): 컨텍스트 1,050,000, 최대 출력 128,000, 텍스트·이미지 입력과 텍스트 출력, 지식 기준일 2026-06-01입니다. effort는 `none`, `low`, `medium`(기본), `high`, `xhigh`, `max`입니다. 엔드포인트는 `v1/responses`와 `v1/chat/completions`이며 도구 호출에는 Responses가 필요합니다. + +100만 토큰당 입력 $1.00, 캐시 입력 $0.05, 캐시 쓰기 $1.25(30분), 출력 $5.00입니다. 입력이 272,000 토큰을 초과하면 요청 전체에 입력·캐시 2×, 출력 1.5×를 적용하여 각각 $2.00 / $0.10 / $2.50 / $7.50입니다. Fast 모드는 2×입니다. + ## 처음 등록할 때의 모델 선택 신규 비-OAuth 연결은 신뢰할 수 있는 모델 목록을 확보할 때까지 모델 노출을 보류합니다. Models 탭의 중복 없는 모델 행이 20개 이상이면 모델 스위치를 모두 OFF로 설정합니다. 프로바이더는 활성 상태를 유지합니다. 실제 인증 방식이 OAuth나 ChatGPT 로그인인 연결은 기존 기본값을 유지합니다. @@ -126,7 +136,7 @@ managed map을 활성화하면 privacy-safe selector를 만들고, 이후 계정 | `modelReasoningEfforts?` | `Record` | 모델별 레이블입니다. 빈 목록이면 effort 제어를 숨깁니다. | | `modelSupportsReasoningSummaries?` | `Record` | 모델을 `false`로 두면 summary 광고를 멈추고 summary 전달 필드를 제거합니다. | | `modelReasoningSummaryDelivery?` | `Record` | 모델별 Responses 전달 enum입니다. 기존 delivery 필드를 다시 씁니다. | -| `modelAdapters?` | `Record` | 혼합 와이어 게이트웨이를 위한 모델별 `openai-chat` 또는 `openai-responses` 와이어 재정의입니다. 명시적 항목이 레지스트리 기본값보다 우선합니다. DeepSeek 프리셋은 `deepseek-v4-flash`에 네이티브 Responses를 선택할 수 있고, GitHub Copilot은 모델(`gpt-5.3-codex`, `gpt-5.4`, `gpt-5.4-mini`, `gpt-5.5`, `gpt-5.6-luna`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`)을 Responses 전용 기본값으로 선언합니다. 이 모델들은 에이전트 트래픽에서 `/chat/completions`를 거부하기 때문입니다. `gpt-5.4-nano`처럼 기본값이 없는 모델은 여기서 직접 옵트인할 수 있습니다. 단일 와이어 상위 항목과 정식 ChatGPT forward는 재정의를 거부합니다. | +| `modelAdapters?` | `Record` | 혼합 와이어 게이트웨이를 위한 모델별 `openai-chat` 또는 `openai-responses` 와이어 재정의입니다. 명시적 항목이 레지스트리 기본값보다 우선합니다. DeepSeek 프리셋은 `deepseek-v4-flash`에 네이티브 Responses를 선택할 수 있고, GitHub Copilot은 모델(`gpt-5.3-codex`, `gpt-5.4`, `gpt-5.4-mini`, `gpt-5.5`, `gpt-5.6-luna`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-6.1-sol`, `gpt-6.1-terra`, `gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`)을 Responses 전용 기본값으로 선언합니다. 이 모델들은 에이전트 트래픽에서 `/chat/completions`를 거부하기 때문입니다. `gpt-5.4-nano`처럼 기본값이 없는 모델은 여기서 직접 옵트인할 수 있습니다. 단일 와이어 상위 항목과 정식 ChatGPT forward는 재정의를 거부합니다. | | xAI Responses 옵트인(대시보드) | 스위치 | `xai`에서만 `grok-4.5`와 `grok-4.6`의 `modelAdapters` 항목을 원자적으로 설정하거나 지웁니다. 한 항목만 있으면 다음 스위치 쓰기가 둘을 정규화할 때까지 혼합 상태로 표시됩니다. 다른 재정의와 티어 동작은 바뀌지 않습니다. Grok 4.7은 OAuth에서 레지스트리 와이어 기본값으로 Responses를 사용하며, 명시적 `modelAdapters["grok-4.7"] = "openai-chat"` 항목으로 Chat으로 전환할 수 있습니다. | | `xaiResponsesXSearch?` | `boolean` | 기본적으로 비활성화됩니다. xAI Responses 대상에서는 최종 요청 정규화 후에도 실제 `web_search` 도구가 남아 있을 때만 공급자가 호스팅하는 `x_search` 선언을 추가합니다. 기존 선언은 중복하지 않고, 호출자의 `tool_choice`/`allowed_tools` 선택기 범위를 확장하지 않으며, 웹 검색 사이드카의 `search.xSearch` 옵션과는 별개입니다. | | `modelPreferHostedTools?` | `Record` | hosted tool namespace를 예약하는 non-forward Responses gateway용 정확한 모델 ID opt-in입니다. 현재 `["image_generation"]`만 허용하며, 일치하는 모델은 `openai-responses` wire를 사용하고 해당 hosted tool을 지원해야 합니다. 충돌하는 클라이언트 `image_gen` 선언을 제거하고 호출자의 tool choice를 유지하도록 selector도 다시 씁니다. OpenAI API 가상 `-pro` 모델은 선택한 공개 ID를 먼저 일치시키고, 해석된 기본 wire-model ID를 대체값으로 사용합니다. `modelAdapters`는 공개 ID를 먼저, 그 다음 기본 ID를 해석하며, 두 번째 결과가 최종 wire를 결정합니다. 설정하지 않은 모델은 일반 alias 동작을 유지합니다. | diff --git a/docs-site/src/content/docs/ko/reference/configuration/routing.md b/docs-site/src/content/docs/ko/reference/configuration/routing.md index d19dce2f092..ffdd4a573c8 100644 --- a/docs-site/src/content/docs/ko/reference/configuration/routing.md +++ b/docs-site/src/content/docs/ko/reference/configuration/routing.md @@ -5,6 +5,8 @@ description: 기본 provider 선택, model 해석 순서, combo 별칭, 대상 라우팅은 클라이언트가 보낸 model id를 하나의 실제 provider와 upstream model로 바꿉니다. +`gpt-5.6-terra`와 함께 `gpt-6.1-terra`도 선택할 수 있습니다. 기본 모델이나 하위 에이전트 모델 목록은 바뀌지 않습니다. [GPT-6.1 Terra 한도·추론·Fast](/ko/reference/configuration/providers/#gpt-61-terra)를 참고하세요. + ## 최상위 라우팅 필드 | Field | Type | Default | Meaning | diff --git a/docs-site/src/content/docs/reference/adapters.md b/docs-site/src/content/docs/reference/adapters.md index ef88ecb76b5..5a28844d42e 100644 --- a/docs-site/src/content/docs/reference/adapters.md +++ b/docs-site/src/content/docs/reference/adapters.md @@ -23,6 +23,8 @@ adapter own retries/timeouts, while `runTurn` supports transports that cannot be HTTP fetch followed by one response stream. [`bridge.ts`](/reference/architecture/#the-bridge) then turns the events into Responses SSE. +You can also select `gpt-6.1-terra` alongside `gpt-5.6-terra`; it does not replace any default or sub-agent roster entry. See [GPT-6.1 Terra limits, reasoning and Fast](/reference/configuration/providers/#gpt-61-terra). + ## External task input on translated Responses routes Codex task coordination can deliver input as `function_call_output` with nonblank diff --git a/docs-site/src/content/docs/reference/configuration/agents.md b/docs-site/src/content/docs/reference/configuration/agents.md index d03750291a2..1b6791280cd 100644 --- a/docs-site/src/content/docs/reference/configuration/agents.md +++ b/docs-site/src/content/docs/reference/configuration/agents.md @@ -385,7 +385,7 @@ Each selected destination resolves its own pin, then applicable caps and wire no Compaction requests are exempt. `none` means effort omission and provider-default behavior, not guaranteed reasoning disablement. For canonical OpenAI forwarding, the final model's supported effort list takes precedence: -`gpt-6.1-sol` starts at `low`, so an incoming `none` or `minimal` is sent as `low`, including +`gpt-6.1-sol` and `gpt-6.1-terra` start at `low`, so an incoming `none` or `minimal` is sent as `low`, including after a compaction model switch or combo failover. `GET /api/effort-caps` includes the map. `PUT /api/effort-caps` accepts `modelPinnedEfforts` diff --git a/docs-site/src/content/docs/reference/configuration/providers.md b/docs-site/src/content/docs/reference/configuration/providers.md index 9ec4cb46ad5..808d56d2c23 100644 --- a/docs-site/src/content/docs/reference/configuration/providers.md +++ b/docs-site/src/content/docs/reference/configuration/providers.md @@ -33,6 +33,16 @@ have a 60-second upload deadline, a 128 MiB input cap and at most two simultaneo provider pacing/concurrency still applies. Oversized text or unconvertible images still need compaction; this transport repair does not extend the model's context window. +## GPT-6.1 Terra + +[GPT-6.1 Terra](https://openai.com/index/introducing-gpt-6-1-terra/) was released on October 26, 2026 as the successor to GPT-5.6 Terra. `gpt-6.1-terra` is available alongside `gpt-5.6-terra`; no default model or sub-agent roster changes. GitHub Copilot uses Responses; OpenRouter lists `openai/gpt-6.1-terra` with 1,050,000 context and $1.00 input / $5.00 output per 1M tokens. + +Native Codex: default context 500,000, long-context ceiling 872,000, default effort `low`, ladder `low`, `medium`, `high`, `xhigh`, `max`, `ultra`. Native `ultra` is sent as `max` on the wire. The native row offers Fast only. + +[OpenAI API](https://developers.openai.com/api/docs/models/gpt-6.1-terra): context 1,050,000, maximum output 128,000; text/image input and text output; knowledge cutoff 2026-06-01. Efforts: `none`, `low`, `medium` (default), `high`, `xhigh`, `max`. Endpoints: `v1/responses` and `v1/chat/completions`; tool calling requires Responses. + +Per 1M tokens: $1.00 input, $0.05 cached input, $1.25 cache write (30 minutes), $5.00 output. Above 272,000 input tokens, the whole request uses 2× input/cache and 1.5× output: $2.00 / $0.10 / $2.50 / $7.50 respectively. Fast mode costs 2×. + ## Context windows on custom providers When a custom provider omits a model's context window, OpenCodex can infer it from the bundled @@ -354,7 +364,7 @@ Providers can expose a built-in shorthand, such as `agy` for `google-antigravity | `modelSuppressSyntheticMax?` | `Record` | Catalog-only per-model switch. `true` prevents OpenCodex from adding a missing synthetic `max` rung while retaining a provider-declared `max` and continuing to add `ultra` to reasoning-capable ladders. A preserved row that already contains `max` keeps it until healthy discovery rebuilds that row, because the catalog does not persist whether an older `max` was synthetic. If a configured default names a suppressed missing `max`, the catalog falls back to the highest real rung below it. Codex uses the same ladder membership for the picker and explicit `spawn_agent` effort validation, so an explicit `max` spawn can fail client-side before proxy clamping; `ultra` remains the supported harness path. | | `modelSupportsReasoningSummaries?` | `Record` | Set a model to `false` to stop advertising summaries and strip summary-delivery fields. | | `modelReasoningSummaryDelivery?` | `Record` | Per-model Responses delivery enum; rewrites an existing delivery field. | -| `modelAdapters?` | `Record` | Per-model `openai-chat` or `openai-responses` wire override for mixed-wire gateways. Explicit entries beat registry defaults. The OpenCode Go preset selects Responses for `gpt-5.6-luna` while leaving sibling models on their documented wires; DeepSeek can select native Responses for `deepseek-v4-flash`; Alibaba Token Plan (Beijing) pins `qwen3.8-flash`, `qwen3.7-plus`, and `glm-5.3` to its native Responses API for Responses inbound only (live-verified on that gateway, including plaintext reasoning replay; Chat and Anthropic inbound stay on Chat, and the rest of the family can be opted in here); and GitHub Copilot declares Responses-only defaults for the following models (`gpt-5.3-codex`, `gpt-5.4`, `gpt-5.4-mini`, `gpt-5.5`, `gpt-5.6-luna`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`) because those models reject `/chat/completions` for agent traffic. Models without a built-in default (for example `gpt-5.4-nano`) can be opted in here. Single-wire upstream pins and canonical ChatGPT forward reject overrides. | +| `modelAdapters?` | `Record` | Per-model `openai-chat` or `openai-responses` wire override for mixed-wire gateways. Explicit entries beat registry defaults. The OpenCode Go preset selects Responses for `gpt-5.6-luna` while leaving sibling models on their documented wires; DeepSeek can select native Responses for `deepseek-v4-flash`; Alibaba Token Plan (Beijing) pins `qwen3.8-flash`, `qwen3.7-plus`, and `glm-5.3` to its native Responses API for Responses inbound only (live-verified on that gateway, including plaintext reasoning replay; Chat and Anthropic inbound stay on Chat, and the rest of the family can be opted in here); and GitHub Copilot declares Responses-only defaults for the following models (`gpt-5.3-codex`, `gpt-5.4`, `gpt-5.4-mini`, `gpt-5.5`, `gpt-5.6-luna`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-6.1-sol`, `gpt-6.1-terra`, `gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`) because those models reject `/chat/completions` for agent traffic. Models without a built-in default (for example `gpt-5.4-nano`) can be opted in here. Single-wire upstream pins and canonical ChatGPT forward reject overrides. | | xAI Chat Completions (dashboard / CLI) | switch | Grok 4.5/4.6 OAuth Responses requests default to Responses. Existing Chat overrides are migrated once on upgrade; later Chat choices are preserved. Turn on to select Chat for both models, off to select Responses. CLI: `ocx provider edit xai --xai-chat on` or `--xai-chat off` (running proxy required). Mixed means only one model currently uses Chat. Other overrides and tier policy stay unchanged. API-key and translated Chat/Anthropic defaults are unchanged. Grok 4.7 defaults to Responses on OAuth through its registry wire default and can use Chat through an explicit `modelAdapters["grok-4.7"] = "openai-chat"` override. | | `xaiResponsesXSearch?` | `boolean` | Disabled by default. On an xAI Responses destination, append the provider-hosted `x_search` declaration only when a live `web_search` tool survives final request normalization. Existing declarations are not duplicated, caller `tool_choice`/`allowed_tools` selectors are never widened, and this is separate from the web-search sidecar's `search.xSearch` options. | | `modelPreferHostedTools?` | `Record` | Exact-model opt-in for non-forward Responses gateways that reserve a hosted-tool namespace. Currently accepts only `["image_generation"]`; a matching model must use the `openai-responses` wire and support that hosted tool. It removes colliding client `image_gen` declarations and rewrites their selectors to preserve caller tool choice. For OpenAI API virtual `-pro` models, the selected public ID is matched first and the resolved base wire-model ID is a fallback. `modelAdapters` resolves the public ID first, then the base ID; the second resolution determines the final wire. Other models retain normal alias behavior. | @@ -916,6 +926,7 @@ OpenAI-backed model slugs: - `openai/gpt-5.6-sol` - `openai/gpt-5.6-terra` +- `openai/gpt-6.1-terra` - `openai/gpt-5.6-luna` `anthropic/claude-sonnet-5` and undeclared OpenRouter models remain unclassified. A provider-level diff --git a/docs-site/src/content/docs/reference/configuration/routing.md b/docs-site/src/content/docs/reference/configuration/routing.md index e518b009789..4efaa61ef82 100644 --- a/docs-site/src/content/docs/reference/configuration/routing.md +++ b/docs-site/src/content/docs/reference/configuration/routing.md @@ -5,6 +5,8 @@ description: Default-provider selection, model resolution order, combo aliases, Routing turns the model id sent by a client into one concrete provider and upstream model. +You can also select `gpt-6.1-terra` alongside `gpt-5.6-terra`; it does not replace any default or sub-agent roster entry. See [GPT-6.1 Terra limits, reasoning and Fast](/reference/configuration/providers/#gpt-61-terra). + ## Top-level routing fields | Field | Type | Default | Meaning | diff --git a/docs-site/src/content/docs/ru/getting-started/quickstart.md b/docs-site/src/content/docs/ru/getting-started/quickstart.md index 99d6cdb2a1b..cfe87c16c28 100644 --- a/docs-site/src/content/docs/ru/getting-started/quickstart.md +++ b/docs-site/src/content/docs/ru/getting-started/quickstart.md @@ -5,6 +5,8 @@ description: Настройте первого провайдера и напр Это руководство проводит от чистой установки до запуска Codex с моделью не от OpenAI. +Наряду с `gpt-5.6-terra` можно выбрать `gpt-6.1-terra`. Модель по умолчанию и список моделей подагентов не меняются. См. [лимиты, уровни рассуждения и Fast для GPT-6.1 Terra](/ru/reference/configuration/providers/#gpt-61-terra). + ## Автономный бинарный файл (без npm) Можно также использовать архив с бинарным файлом `ocx` и рантаймом Bun без npm. diff --git a/docs-site/src/content/docs/ru/guides/codex-app-models.md b/docs-site/src/content/docs/ru/guides/codex-app-models.md index 366b3b44046..bf8eb05339c 100644 --- a/docs-site/src/content/docs/ru/guides/codex-app-models.md +++ b/docs-site/src/content/docs/ru/guides/codex-app-models.md @@ -54,6 +54,8 @@ cp ~/.opencodex/config.json.pre-openai-tiers-v2.bak ~/.opencodex/config.json Более ранние трёхпровайдерные конфигурации v1 автоматически мигрируют в одну строку с переключаемым режимом. +Наряду с `gpt-5.6-terra` можно выбрать `gpt-6.1-terra`. Модель по умолчанию и список моделей подагентов не меняются. См. [лимиты, уровни рассуждения и Fast для GPT-6.1 Terra](/ru/reference/configuration/providers/#gpt-61-terra). + ## Путь интеграции `ocx init`, `ocx start` и `ocx sync` подключают общий конфиг и каталог Codex к прокси; подробности @@ -84,10 +86,11 @@ per-model identity и метаданные вместо приближения | Маршрут | Id в селекторе и метаданные каталога | | --- | --- | -| Вход Codex (строки с указанием аккаунта выключены) | Bare native-id, например `gpt-5.6-sol`, `gpt-5.6-terra` и `gpt-5.6-luna`; Pool или Direct выбирается через `codexAccountMode`. У строк GPT-5.6 окно каталога 922 000 токенов. | +| Вход Codex (строки с указанием аккаунта выключены) | Bare native-id, например `gpt-5.6-sol`, `gpt-5.6-terra` и `gpt-5.6-luna`; Pool или Direct выбирается через `codexAccountMode`. У строк GPT-5.6 окно каталога 922 000 токенов. `gpt-6.1-terra`: контекст 500,000 по умолчанию / 872,000 расширенный. | | Вход Codex (строки с указанием аккаунта включены и есть подходящие селекторы) | По одной строке `/` для каждой пары подходящего селектора и поддерживаемой нативной модели; каждая строка использует только сопоставленный аккаунт, а bare native-строки скрыты из picker'а. Нативные метаданные и окна контекста сохраняются. | -| OpenAI (API key) | Ровно восемь namespaced-строк: `gpt-5.5`, `gpt-5.6`, Sol/Terra/Luna и три виртуальных id `*-pro` (контекст 922,000; максимум входа 922,000 у всех восьми) | +| OpenAI (API key) | Модели с пространством имён включают `gpt-5.5`, `gpt-5.6`, Sol/Terra/Luna, виртуальные id `*-pro` и псевдонимы Daybreak (контекст 1,050,000; максимум входа 922,000). `openai-apikey/gpt-6.1-terra` добавляет контекст 1,050,000 и максимум выхода 128,000. | | OpenRouter | `openrouter/openai/gpt-5.6-sol`, `openrouter/openai/gpt-5.6-terra`, `openrouter/openai/gpt-5.6-luna` (922,000) | +| OpenRouter | `openrouter/openai/gpt-6.1-terra` (1,050,000) | | Cursor | Статический fallback включает `cursor/gpt-5.6-sol`, `cursor/gpt-5.6-terra` и `cursor/gpt-5.6-luna` (1,000,000), а также обычные/Fast-строки Grok 4.5, 4.6 и 4.7 (500,000). Для 4.6 и 4.7 доступен ещё `xhigh`; какие строки останутся видимыми, решает live-discovery аккаунта. | | xAI | Live-discovery имеет приоритет. Fallback-каталог включает `xai/grok-4.6` и `xai/grok-4.7`, а моделью по умолчанию остаётся `xai/grok-4.5`; у всех трёх окно 500,000 токенов. Grok 4.6 и 4.7 поддерживают `low` / `medium` / `high` / `xhigh` (upstream-default: `high`), а Grok 4.5 — только до `high`. | diff --git a/docs-site/src/content/docs/ru/guides/model-ordering.md b/docs-site/src/content/docs/ru/guides/model-ordering.md index 5ff04e48920..846e2b6d836 100644 --- a/docs-site/src/content/docs/ru/guides/model-ordering.md +++ b/docs-site/src/content/docs/ru/guides/model-ordering.md @@ -7,6 +7,8 @@ description: Как opencodex определяет порядок моделей конфигурации opencodex. Итоговый порядок определяется приоритетами каталога, а маршрутизируемые модели с одинаковым приоритетом упорядочиваются детерминированно по алфавиту. +Наряду с `gpt-5.6-terra` можно выбрать `gpt-6.1-terra`. Модель по умолчанию и список моделей подагентов не меняются. См. [лимиты, уровни рассуждения и Fast для GPT-6.1 Terra](/ru/reference/configuration/providers/#gpt-61-terra). + ## Правило, которое применяет Codex Менеджер моделей Codex сортирует видимые в селекторе записи каталога по `priority` по diff --git a/docs-site/src/content/docs/ru/guides/providers.md b/docs-site/src/content/docs/ru/guides/providers.md index 66c7357be33..d47eba8456f 100644 --- a/docs-site/src/content/docs/ru/guides/providers.md +++ b/docs-site/src/content/docs/ru/guides/providers.md @@ -7,6 +7,8 @@ description: Все способы, которыми opencodex аутентиф базовый URL, режим аутентификации и необязательный список моделей. Провайдеры находятся в `~/.opencodex/config.json` в секции `providers`. +Наряду с `gpt-5.6-terra` можно выбрать `gpt-6.1-terra`. Модель по умолчанию и список моделей подагентов не меняются. См. [лимиты, уровни рассуждения и Fast для GPT-6.1 Terra](/ru/reference/configuration/providers/#gpt-61-terra). + ## Режимы аккаунтов OpenAI | Id провайдера | Назначение | Правило учётных данных/аккаунтов | @@ -490,6 +492,9 @@ GPT-5.6 Sol/Terra/Luna заранее внесены в резервные сп | Вход Codex (Pool или Direct) | `gpt-5.6-*` | 922,000 | | OpenAI (API key) | `openai-apikey/gpt-5.6-*` плюс `*-pro` | 922,000 (макс. вход 922,000) | | OpenRouter | `openrouter/openai/gpt-5.6-sol`, `openrouter/openai/gpt-5.6-terra`, `openrouter/openai/gpt-5.6-luna` | 922,000 | +| Codex | `gpt-6.1-terra` | 500,000 / 872,000 | +| OpenAI API | `openai-apikey/gpt-6.1-terra` | 1,050,000 (128,000 max output) | +| OpenRouter | `openrouter/openai/gpt-6.1-terra` | 1,050,000 | | Cursor | `cursor/gpt-5.6-sol`, `cursor/gpt-5.6-terra`, `cursor/gpt-5.6-luna` | 1,000,000 | Нативные записи GPT-5.6 сохраняют закреплённые вышестоящие шкалы уровней рассуждений (например, у @@ -510,7 +515,7 @@ Assist), `azure` / `azure-openai`, `kiro` и `cursor`. Проприетарны точке. **Cloudflare AI Gateway** требует подставить в URL id аккаунта и шлюза. Copilot предоставляет каталог со смешанными проводами: модели (`gpt-5.3-codex`, -`gpt-5.4`, `gpt-5.4-mini`, `gpt-5.5`, `gpt-5.6-luna`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`) +`gpt-5.4`, `gpt-5.4-mini`, `gpt-5.5`, `gpt-5.6-luna`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-6.1-sol`, `gpt-6.1-terra`, `gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`) отклоняют `/chat/completions` для агентного трафика, поэтому opencodex по умолчанию маршрутизирует эти модели через Responses API, а все остальные модели Copilot остаются на chat completions. Приоритет: жёсткий wire-пин → явная запись diff --git a/docs-site/src/content/docs/ru/reference/adapters.md b/docs-site/src/content/docs/ru/reference/adapters.md index 3bad254262f..d1800b7861b 100644 --- a/docs-site/src/content/docs/ru/reference/adapters.md +++ b/docs-site/src/content/docs/ru/reference/adapters.md @@ -25,6 +25,8 @@ interface ProviderAdapter { с последующим одним потоком ответа. Затем [`bridge.ts`](/ru/reference/architecture/#мост) превращает события в Responses SSE. +Наряду с `gpt-5.6-terra` можно выбрать `gpt-6.1-terra`. Модель по умолчанию и список моделей подагентов не меняются. См. [лимиты, уровни рассуждения и Fast для GPT-6.1 Terra](/ru/reference/configuration/providers/#gpt-61-terra). + ## `openai-chat` **Назначение:** OpenAI **Chat Completions** (`POST {baseUrl}/chat/completions`) и все совместимые diff --git a/docs-site/src/content/docs/ru/reference/configuration/providers.md b/docs-site/src/content/docs/ru/reference/configuration/providers.md index 98f181a7bb6..bba82ea2c7b 100644 --- a/docs-site/src/content/docs/ru/reference/configuration/providers.md +++ b/docs-site/src/content/docs/ru/reference/configuration/providers.md @@ -12,6 +12,16 @@ description: Записи провайдеров, аутентификация, Эта оценка по умолчанию выключена: включите её для провайдера параметром `inferContextWindow: true`. Без него модель без окна использует включённый Context cap, затем 128k. +## GPT-6.1 Terra + +[GPT-6.1 Terra](https://openai.com/index/introducing-gpt-6-1-terra/) вышла 26 октября 2026 года как преемница GPT-5.6 Terra. `gpt-6.1-terra` доступна наряду с `gpt-5.6-terra`; модель по умолчанию и список подагентов не меняются. GitHub Copilot использует Responses. OpenRouter предлагает `openai/gpt-6.1-terra` с контекстом 1,050,000 и ценой $1.00 за вход / $5.00 за выход на миллион токенов. + +Нативный Codex: контекст по умолчанию 500,000, расширенный предел 872,000, effort по умолчанию `low`; уровни `low`, `medium`, `high`, `xhigh`, `max`, `ultra`. Нативный `ultra` передаётся по сети как `max`. Нативная строка предлагает только Fast. + +[OpenAI API](https://developers.openai.com/api/docs/models/gpt-6.1-terra): контекст 1,050,000, максимальный выход 128,000; текст и изображения на входе, текст на выходе; срез знаний 2026-06-01. Effort: `none`, `low`, `medium` (по умолчанию), `high`, `xhigh`, `max`. Эндпоинты: `v1/responses` и `v1/chat/completions`; вызов инструментов требует Responses. + +За миллион токенов: $1.00 вход, $0.05 чтение кеша, $1.25 запись кеша (30 минут), $5.00 выход. При входе свыше 272,000 токенов весь запрос тарифицируется с множителем 2× для входа и кеша и 1.5× для выхода: соответственно $2.00 / $0.10 / $2.50 / $7.50. Режим Fast стоит 2×. + ## Выбор моделей при первой регистрации Новое подключение без OAuth не публикует модели до получения достоверного списка. Если в Models не менее 20 уникальных строк моделей, все переключатели моделей изначально OFF, но сам провайдер остаётся ACTIVE. Подключения, фактически использующие OAuth или вход ChatGPT, сохраняют настройки по умолчанию. @@ -139,7 +149,7 @@ cross-route credential fallback не существует. Строки API GPT- | `modelReasoningEfforts?` | `Record` | Label'ы по отдельным моделям. Пустой список скрывает управление effort. | | `modelSupportsReasoningSummaries?` | `Record` | Установите `false` для модели, чтобы перестать рекламировать summary и вырезать поля доставки summary. | | `modelReasoningSummaryDelivery?` | `Record` | Responses delivery enum по моделям; переписывает уже существующее поле delivery. | -| `modelAdapters?` | `Record` | Wire-override по модели для `openai-chat` или `openai-responses` в gateway с несколькими wire-форматами. Явные записи имеют приоритет над default'ами registry; preset DeepSeek может выбирать native Responses для `deepseek-v4-flash`, а GitHub Copilot объявляет Responses-only default'ы для моделей (`gpt-5.3-codex`, `gpt-5.4`, `gpt-5.4-mini`, `gpt-5.5`, `gpt-5.6-luna`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`), потому что эти модели отклоняют `/chat/completions` для агентного трафика. Модели без встроенного default'а (например, `gpt-5.4-nano`) можно включить здесь. Single-wire upstream pin'ы и canonical ChatGPT forward override не принимают. | +| `modelAdapters?` | `Record` | Wire-override по модели для `openai-chat` или `openai-responses` в gateway с несколькими wire-форматами. Явные записи имеют приоритет над default'ами registry; preset DeepSeek может выбирать native Responses для `deepseek-v4-flash`, а GitHub Copilot объявляет Responses-only default'ы для моделей (`gpt-5.3-codex`, `gpt-5.4`, `gpt-5.4-mini`, `gpt-5.5`, `gpt-5.6-luna`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-6.1-sol`, `gpt-6.1-terra`, `gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`), потому что эти модели отклоняют `/chat/completions` для агентного трафика. Модели без встроенного default'а (например, `gpt-5.4-nano`) можно включить здесь. Single-wire upstream pin'ы и canonical ChatGPT forward override не принимают. | | Opt-in xAI Responses (панель) | переключатель | Только для `xai`: атомарно задаёт или удаляет записи `modelAdapters` для `grok-4.5` и `grok-4.6`. Одна запись отображается как смешанное состояние до следующего переключения. Остальные override и поведение tier не меняются. Grok 4.7 по умолчанию использует Responses на OAuth через настройку реестра и может перейти на Chat через явную запись `modelAdapters["grok-4.7"] = "openai-chat"`. | | `xaiResponsesXSearch?` | `boolean` | По умолчанию отключено. Для назначения xAI Responses декларация `x_search`, размещённая у провайдера, добавляется только тогда, когда действующий инструмент `web_search` сохраняется после окончательной нормализации запроса. Существующие декларации не дублируются, селекторы вызывающей стороны `tool_choice`/`allowed_tools` никогда не расширяются, и эта настройка не связана с параметрами `search.xSearch` сайдкара веб-поиска. | | `modelPreferHostedTools?` | `Record` | Opt-in для точного model ID в non-forward Responses gateway, который резервирует namespace hosted tool. Сейчас допускается только `["image_generation"]`; совпавшая модель должна использовать wire `openai-responses` и поддерживать этот hosted tool. Прокси удаляет конфликтующие клиентские объявления `image_gen` и переписывает их selectors, сохраняя caller tool choice. Для виртуальных моделей OpenAI API `-pro` сначала сопоставляется выбранный публичный ID, а затем в качестве fallback используется ID базовой wire-модели. `modelAdapters` сначала разрешается по публичному ID, затем по базовому ID; второй результат определяет итоговый wire. Остальные модели сохраняют обычное alias-поведение. | diff --git a/docs-site/src/content/docs/ru/reference/configuration/routing.md b/docs-site/src/content/docs/ru/reference/configuration/routing.md index b117669318f..c4f83cdcb0d 100644 --- a/docs-site/src/content/docs/ru/reference/configuration/routing.md +++ b/docs-site/src/content/docs/ru/reference/configuration/routing.md @@ -6,6 +6,8 @@ description: Выбор провайдера по умолчанию, поряд Маршрутизация преобразует id модели, отправленный клиентом, в конкретного провайдера и модель upstream. +Наряду с `gpt-5.6-terra` можно выбрать `gpt-6.1-terra`. Модель по умолчанию и список моделей подагентов не меняются. См. [лимиты, уровни рассуждения и Fast для GPT-6.1 Terra](/ru/reference/configuration/providers/#gpt-61-terra). + ## Поля маршрутизации верхнего уровня | Поле | Тип | По умолчанию | Значение | diff --git a/docs-site/src/content/docs/tr/getting-started/quickstart.md b/docs-site/src/content/docs/tr/getting-started/quickstart.md index 27e9f1d95a7..e7b9d98d16b 100644 --- a/docs-site/src/content/docs/tr/getting-started/quickstart.md +++ b/docs-site/src/content/docs/tr/getting-started/quickstart.md @@ -6,6 +6,8 @@ description: İlk sağlayıcınızı yapılandırın ve OpenAI Codex'i üç komu Bu kılavuz, yeni bir kurulumdan başlayarak Codex'i OpenAI harici bir model üzerinde çalıştırmanızı sağlar. +`gpt-5.6-terra` yanında `gpt-6.1-terra` da seçilebilir. Varsayılan model ve alt ajan model listesi değişmez. [GPT-6.1 Terra sınırları, akıl yürütme ve Fast](/tr/reference/configuration/providers/#gpt-61-terra) bölümüne bakın. + ## 1. Kurulum sihirbazını çalıştırın ```bash diff --git a/docs-site/src/content/docs/tr/guides/codex-app-models.md b/docs-site/src/content/docs/tr/guides/codex-app-models.md index e270fea3574..40625b39ed0 100644 --- a/docs-site/src/content/docs/tr/guides/codex-app-models.md +++ b/docs-site/src/content/docs/tr/guides/codex-app-models.md @@ -97,6 +97,8 @@ cp ~/.opencodex/config.json.pre-openai-tiers-v2.bak ~/.opencodex/config.json Daha önceki v1 üç sağlayıcılı yapılandırmalar otomatik olarak tek seçenek duyarlı satıra geçer. +`gpt-5.6-terra` yanında `gpt-6.1-terra` da seçilebilir. Varsayılan model ve alt ajan model listesi değişmez. [GPT-6.1 Terra sınırları, akıl yürütme ve Fast](/tr/reference/configuration/providers/#gpt-61-terra) bölümüne bakın. + ## Desktop uzak izin listesi sınırlaması `codex debug models` ve uygulama sunucusu `model/list` yönlendirilen bir modeli @@ -152,11 +154,12 @@ meta verileri sağladığı GPT-5.6 için kullanılır. | Rota | Seçici kimlikleri ve katalog meta verileri | | --- | --- | -| Codex girişi (hesap nitelikli satırlar devre dışı) | `gpt-5.6-sol`, `gpt-5.6-terra` ve `gpt-5.6-luna` gibi yalın yerel kimlikler; Pool veya Direct `codexAccountMode` aracılığıyla seçilir. GPT-5.6 satırları 922.000 tokenlik bir katalog penceresi kullanır. | +| Codex girişi (hesap nitelikli satırlar devre dışı) | `gpt-5.6-sol`, `gpt-5.6-terra` ve `gpt-5.6-luna` gibi yalın yerel kimlikler; Pool veya Direct `codexAccountMode` aracılığıyla seçilir. GPT-5.6 satırları 922.000 tokenlik bir katalog penceresi kullanır. `gpt-6.1-terra`: varsayılan bağlam 500,000 / uzun bağlam 872,000. | | Codex girişi (uygun seçicilerle hesap nitelikli satırlar etkin) | Uygun seçici ve desteklenen yerel model başına bir `/` satırı; her satır yalnızca eşlenen hesabını kullanır ve yalın yerel satırlar seçiciden gizlenir. Yerel meta veriler ve bağlam pencereleri korunur. | | Codex girişi (açık Daybreak iletme satırı) | Yalnızca tam `customModels` satırı kurallı `openai` sağlayıcısında yapılandırıldığında `openai/gpt-daybreak-blue-latest`. Daybreak hat kimliğini korur ve sabitlenmiş Sol yetenek anlık görüntüsünü kullanır (922.000 bağlam; 829.800 otomatik sıkıştırma). | -| OpenAI (API anahtarı) | Tam olarak on ad alanlı satır: `gpt-5.5`, `gpt-5.6`, Sol/Terra/Luna, üç `*-pro` sanal kimliği ve iki Daybreak takma adı (onunun tümü için 922.000 bağlam; 922.000 maksimum girdi) | +| OpenAI (API anahtarı) | Ad alanlı modeller arasında `gpt-5.5`, `gpt-5.6`, Sol/Terra/Luna, `*-pro` sanal kimlikleri ve Daybreak takma adları bulunur (1,050,000 bağlam; 922,000 maksimum girdi). `openai-apikey/gpt-6.1-terra` için bağlam 1,050,000, maksimum çıktı 128,000’dır. | | OpenRouter | `openrouter/openai/gpt-5.6-sol`, `openrouter/openai/gpt-5.6-terra`, `openrouter/openai/gpt-5.6-luna` (922.000) | +| OpenRouter | `openrouter/openai/gpt-6.1-terra` (1,050,000) | | Cursor | Statik geri dönüş `cursor/gpt-5.6-sol`, `cursor/gpt-5.6-terra` ve `cursor/gpt-5.6-luna` (1.000.000) ile Grok 4.5, 4.6 ve 4.7 için normal/Fast satırları (500.000) içerir; 4.6 ve 4.7 ayrıca `xhigh` sunar. Canlı hesap keşfi hangi satırların görünür kalacağını belirler. | | xAI | Canlı keşif yetkilidir. Geri dönüş kataloğu `xai/grok-4.6` ve `xai/grok-4.7` içerir; varsayılan model `xai/grok-4.5` olarak kalır. Üçünün de bağlam penceresi 500.000 tokendir. Grok 4.6 ve 4.7 `low` / `medium` / `high` / `xhigh` (yukarı akış varsayılanı: `high`) sunarken, Grok 4.5 `high` ile durur. | diff --git a/docs-site/src/content/docs/tr/guides/model-ordering.md b/docs-site/src/content/docs/tr/guides/model-ordering.md index ea42630154c..6a0bd9b96f4 100644 --- a/docs-site/src/content/docs/tr/guides/model-ordering.md +++ b/docs-site/src/content/docs/tr/guides/model-ordering.md @@ -8,6 +8,8 @@ veya model dizilerinin sırasını korumaz. Nihai sırası, aynı önceliği pay yönlendirilmiş modeller için belirleyici bir alfabetik sırayla birlikte katalog önceliklerinden gelir. +`gpt-5.6-terra` yanında `gpt-6.1-terra` da seçilebilir. Varsayılan model ve alt ajan model listesi değişmez. [GPT-6.1 Terra sınırları, akıl yürütme ve Fast](/tr/reference/configuration/providers/#gpt-61-terra) bölümüne bakın. + ## Codex'in uyguladığı kural Codex'in models-manager'ı, seçicide görünen katalog girdilerini artan sırada diff --git a/docs-site/src/content/docs/tr/guides/providers.md b/docs-site/src/content/docs/tr/guides/providers.md index 76de995c6d3..e5692726ab7 100644 --- a/docs-site/src/content/docs/tr/guides/providers.md +++ b/docs-site/src/content/docs/tr/guides/providers.md @@ -8,6 +8,8 @@ bir adaptör, bir temel URL, bir kimlik doğrulama modu ve isteğe bağlı bir m listesi. Sağlayıcılar `~/.opencodex/config.json` içinde `providers` altında bulunur. +`gpt-5.6-terra` yanında `gpt-6.1-terra` da seçilebilir. Varsayılan model ve alt ajan model listesi değişmez. [GPT-6.1 Terra sınırları, akıl yürütme ve Fast](/tr/reference/configuration/providers/#gpt-61-terra) bölümüne bakın. + ## OpenAI hesap modları | Sağlayıcı kimliği | Kullanım | Kimlik bilgisi/hesap kuralı | @@ -665,6 +667,9 @@ tohumlanmıştır: | Codex girişi (Pool veya Direct) | `gpt-5.6-*` | 922.000 | | OpenAI (API anahtarı) | `openai-apikey/gpt-5.6-*` artı `*-pro` | 922.000 (922.000 maksimum girdi) | | OpenRouter | `openrouter/openai/gpt-5.6-sol`, `openrouter/openai/gpt-5.6-terra`, `openrouter/openai/gpt-5.6-luna` | 922.000 | +| Codex | `gpt-6.1-terra` | 500,000 / 872,000 | +| OpenAI API | `openai-apikey/gpt-6.1-terra` | 1,050,000 (128,000 max output) | +| OpenRouter | `openrouter/openai/gpt-6.1-terra` | 1,050,000 | | Cursor | `cursor/gpt-5.6-sol`, `cursor/gpt-5.6-terra`, `cursor/gpt-5.6-luna` | 1.000.000 | Yerel GPT-5.6 girdileri sabitlenmiş yukarı akış akıl yürütme merdivenlerini @@ -688,7 +693,7 @@ anahtar/abonelik belirteci ağ geçidi olarak kalır. **Cloudflare AI Gateway**, URL'ye doldurulan hesap + ağ geçidi kimliklerinize ihtiyaç duyar. Copilot karma hatlı bir katalog sunar: modeller (`gpt-5.3-codex`, `gpt-5.4`, -`gpt-5.4-mini`, `gpt-5.5`, `gpt-5.6-luna`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`) ajan +`gpt-5.4-mini`, `gpt-5.5`, `gpt-5.6-luna`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-6.1-sol`, `gpt-6.1-terra`, `gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`) ajan trafiği için `/chat/completions`'ı reddeder, bu nedenle opencodex yerleşik varsayılan olarak bu modelleri Responses API üzerinden yönlendirirken diğer tüm Copilot modelleri sohbet tamamlamalarında kalır. Öncelik sırası: sabit hat diff --git a/docs-site/src/content/docs/tr/reference/adapters.md b/docs-site/src/content/docs/tr/reference/adapters.md index 2a31a0cd7f0..7da928557c9 100644 --- a/docs-site/src/content/docs/tr/reference/adapters.md +++ b/docs-site/src/content/docs/tr/reference/adapters.md @@ -26,6 +26,8 @@ getirmesini takip eden tek bir yanıt akışı olarak temsil edilemeyen aktarım destekler. [`bridge.ts`](/tr/reference/architecture/#köprü-bridge) daha sonra olayları Responses SSE'ye dönüştürür. +`gpt-5.6-terra` yanında `gpt-6.1-terra` da seçilebilir. Varsayılan model ve alt ajan model listesi değişmez. [GPT-6.1 Terra sınırları, akıl yürütme ve Fast](/tr/reference/configuration/providers/#gpt-61-terra) bölümüne bakın. + ## `openai-chat` **Hedefler:** OpenAI **Chat Completions** (`POST {baseUrl}/chat/completions`; diff --git a/docs-site/src/content/docs/tr/reference/configuration/providers.md b/docs-site/src/content/docs/tr/reference/configuration/providers.md index 15a8160c080..0242a1b4754 100644 --- a/docs-site/src/content/docs/tr/reference/configuration/providers.md +++ b/docs-site/src/content/docs/tr/reference/configuration/providers.md @@ -12,6 +12,16 @@ Model penceresi bildirilmemiş veya yapılandırılmamışsa sırasıyla Azure m Bu tahmin varsayılan olarak kapalıdır; sağlayıcı başına `inferContextWindow: true` ile açılır. Ayarlanmazsa penceresi olmayan model etkin Context cap'i, ardından 128k'yı kullanır. +## GPT-6.1 Terra + +[GPT-6.1 Terra](https://openai.com/index/introducing-gpt-6-1-terra/), GPT-5.6 Terra’nın halefi olarak 26 Ekim 2026’da yayımlandı. `gpt-6.1-terra`, `gpt-5.6-terra` ile birlikte kullanılabilir; varsayılan model ve alt ajan listesi değişmez. GitHub Copilot, Responses kullanır. OpenRouter kimliği `openai/gpt-6.1-terra`, bağlamı 1,050,000 ve milyon token başına giriş / çıkış fiyatı $1.00 / $5.00’dır. + +Yerel Codex: varsayılan bağlam 500,000, uzun bağlam tavanı 872,000, varsayılan effort `low`; düzeyler `low`, `medium`, `high`, `xhigh`, `max`, `ultra`. Yerel `ultra`, aktarımda `max` olarak gönderilir. Yerel satır yalnızca Fast sunar. + +[OpenAI API](https://developers.openai.com/api/docs/models/gpt-6.1-terra): bağlam 1,050,000, en fazla çıktı 128,000; metin/görsel girişi ve metin çıktısı; bilgi kesim tarihi 2026-06-01. Effort düzeyleri: `none`, `low`, `medium` (varsayılan), `high`, `xhigh`, `max`. Uç noktalar: `v1/responses` ve `v1/chat/completions`; araç çağrıları Responses gerektirir. + +Milyon token başına: giriş $1.00, önbellek okuma $0.05, önbellek yazma $1.25 (30 dakika), çıktı $5.00. Giriş 272,000 tokenı aşarsa tüm istekte giriş/önbellek 2×, çıktı 1.5× ücretlendirilir: sırasıyla $2.00 / $0.10 / $2.50 / $7.50. Fast modu 2× ücretlidir. + ## İlk kayıtta model seçimi Yeni OAuth dışı bağlantılar, modelleri göstermeden önce güvenilir bir model listesini bekler. Models sekmesinde en az 20 benzersiz model satırı varsa tüm model anahtarları başlangıçta OFF olur; sağlayıcının kendisi ACTIVE kalır. Gerçekte OAuth veya ChatGPT girişi kullanan bağlantılar varsayılanlarını korur. @@ -138,7 +148,7 @@ alanlı seçilmiş kimlikleri yalın kimliklere yeniden yazar. | `modelReasoningEfforts?` | `Record` | Model başına etiketler. Boş bir liste çaba denetimini gizler. `reasoningEfforts`'ta olduğu gibi, yapılandırılmış her `google` adaptör merdiveni `thinkingLevel` yeteneğini iddia eder; doğrudan ve Vertex görsel olmayan istekleri düz Gemini yolunu kullanırken, Cloud Code Assist bunu istek zarfı altında gönderir. | | `modelSupportsReasoningSummaries?` | `Record` | Özetlerin bildirilmesini durdurmak ve özet teslim alanlarını kaldırmak için bir modeli `false` olarak ayarlayın. | | `modelReasoningSummaryDelivery?` | `Record` | Model başına Responses teslim enum'ı; mevcut bir teslim alanını yeniden yazar. | -| `modelAdapters?` | `Record` | Karışık hatlı ağ geçitleri için model başına `openai-chat` veya `openai-responses` hat geçersiz kılma. Açık girdiler kayıt defteri varsayılanlarını yener. OpenCode Go önayarı, kardeş modelleri belgelenmiş hatlarında bırakırken `gpt-5.6-luna` için Responses'ı seçer; DeepSeek, `deepseek-v4-flash` için yerel Responses seçebilir; ve GitHub Copilot, modeller (`gpt-5.3-codex`, `gpt-5.4`, `gpt-5.4-mini`, `gpt-5.5`, `gpt-5.6-luna`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`) için yalnızca Responses varsayılanlarını bildirir çünkü bu modeller ajan trafiği için `/chat/completions`'ı reddeder. Yerleşik varsayılanı olmayan modeller (örneğin `gpt-5.4-nano`) burada dahil edilebilir. Tek hatlı yukarı akış pinleri ve kurallı ChatGPT iletme geçersiz kılmaları reddeder. | +| `modelAdapters?` | `Record` | Karışık hatlı ağ geçitleri için model başına `openai-chat` veya `openai-responses` hat geçersiz kılma. Açık girdiler kayıt defteri varsayılanlarını yener. OpenCode Go önayarı, kardeş modelleri belgelenmiş hatlarında bırakırken `gpt-5.6-luna` için Responses'ı seçer; DeepSeek, `deepseek-v4-flash` için yerel Responses seçebilir; ve GitHub Copilot, modeller (`gpt-5.3-codex`, `gpt-5.4`, `gpt-5.4-mini`, `gpt-5.5`, `gpt-5.6-luna`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-6.1-sol`, `gpt-6.1-terra`, `gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`) için yalnızca Responses varsayılanlarını bildirir çünkü bu modeller ajan trafiği için `/chat/completions`'ı reddeder. Yerleşik varsayılanı olmayan modeller (örneğin `gpt-5.4-nano`) burada dahil edilebilir. Tek hatlı yukarı akış pinleri ve kurallı ChatGPT iletme geçersiz kılmaları reddeder. | | xAI Responses katılımı (panel) | anahtar | Yalnızca `xai` için `grok-4.5` ve `grok-4.6` `modelAdapters` girdilerini atomik olarak ayarlar veya temizler. Tek girdi, sonraki anahtar yazımı ikisini eşitleyene kadar karma durum olarak görünür. Diğer geçersiz kılmalar ve katman davranışı değişmez. Grok 4.7, OAuth üzerinde kayıt defteri hat varsayılanıyla Responses kullanır ve açık `modelAdapters["grok-4.7"] = "openai-chat"` girdisiyle Chat’e geçirilebilir. | | `xaiResponsesXSearch?` | `boolean` | Varsayılan olarak devre dışıdır. Bir xAI Responses hedefinde, yalnızca canlı bir `web_search` aracı son istek normalleştirmesinden sağ çıktığında sağlayıcı tarafından barındırılan `x_search` bildirimini ekler. Mevcut bildirimler yinelenmez, çağıranın `tool_choice`/`allowed_tools` seçicileri hiçbir zaman genişletilmez ve bu, web araması yardımcı hizmetinin `search.xSearch` seçeneklerinden ayrıdır. | | `modelPreferHostedTools?` | `Record` | Barındırılan bir araç ad alanı ayıran iletme harici Responses ağ geçitleri için tam model dahil etme. Şu anda yalnızca `["image_generation"]` kabul eder; eşleşen bir model `openai-responses` hattını kullanmalı ve bu barındırılan aracı desteklemelidir. Çakışan istemci `image_gen` bildirimlerini kaldırır ve arayan araç seçimini korumak için seçicilerini yeniden yazar. OpenAI API sanal `-pro` modelleri için önce seçilen genel kimlik eşleştirilir ve çözümlenen temel hat model kimliği bir geri dönüştür. `modelAdapters` önce genel kimliği, ardından temel kimliği çözer; ikinci çözümleme son hattı belirler. Diğer modeller normal takma ad davranışını korur. | diff --git a/docs-site/src/content/docs/tr/reference/configuration/routing.md b/docs-site/src/content/docs/tr/reference/configuration/routing.md index 3a89ef094e4..a282b9ca800 100644 --- a/docs-site/src/content/docs/tr/reference/configuration/routing.md +++ b/docs-site/src/content/docs/tr/reference/configuration/routing.md @@ -6,6 +6,8 @@ description: Varsayılan sağlayıcı seçimi, model çözümleme sırası, komb Yönlendirme, bir istemci tarafından gönderilen model kimliğini somut bir sağlayıcıya ve yukarı akış modeline dönüştürür. +`gpt-5.6-terra` yanında `gpt-6.1-terra` da seçilebilir. Varsayılan model ve alt ajan model listesi değişmez. [GPT-6.1 Terra sınırları, akıl yürütme ve Fast](/tr/reference/configuration/providers/#gpt-61-terra) bölümüne bakın. + ## Üst düzey yönlendirme alanları | Alan | Tip | Varsayılan | Anlamı | diff --git a/docs-site/src/content/docs/zh-cn/getting-started/quickstart.md b/docs-site/src/content/docs/zh-cn/getting-started/quickstart.md index 76d866052f8..b494fa5bd91 100644 --- a/docs-site/src/content/docs/zh-cn/getting-started/quickstart.md +++ b/docs-site/src/content/docs/zh-cn/getting-started/quickstart.md @@ -5,6 +5,8 @@ description: 配置你的第一个 provider，并在三条命令内让 OpenAI Co 本指南将带你从全新安装，一路走到用一个非 OpenAI 模型运行 Codex。 +除了 `gpt-5.6-terra`，还可以选择 `gpt-6.1-terra`；默认模型和子代理模型列表均不变。参见 [GPT-6.1 Terra 的限制、推理与 Fast](/zh-cn/reference/configuration/providers/#gpt-61-terra)。 + ## 独立二进制文件（无需 npm） 你也可以使用包含 Bun 运行时的发布压缩包中的 `ocx`，无需 npm。 diff --git a/docs-site/src/content/docs/zh-cn/guides/codex-app-models.md b/docs-site/src/content/docs/zh-cn/guides/codex-app-models.md index 5214e768367..aeaa975c102 100644 --- a/docs-site/src/content/docs/zh-cn/guides/codex-app-models.md +++ b/docs-site/src/content/docs/zh-cn/guides/codex-app-models.md @@ -30,6 +30,8 @@ cp ~/.opencodex/config.json.pre-openai-tiers-v2.bak ~/.opencodex/config.json 更早的 v1 三 provider 配置会自动迁移到这个支持单一选项的行。 +除了 `gpt-5.6-terra`，还可以选择 `gpt-6.1-terra`；默认模型和子代理模型列表均不变。参见 [GPT-6.1 Terra 的限制、推理与 Fast](/zh-cn/reference/configuration/providers/#gpt-61-terra)。 + ## Desktop 远程 allowlist 限制 如果 `codex debug models` 和 app-server 的 `model/list` 都包含某个路由模型，但 Desktop @@ -65,10 +67,11 @@ visibility = "list" | 路由 | 选择器 id 与目录元数据 | | --- | --- | -| Codex 登录（账户限定的选择器行未启用） | 显示 `gpt-5.6-sol`、`gpt-5.6-terra`、`gpt-5.6-luna` 等裸原生 id，并按 `codexAccountMode` 使用 Pool 或 Direct。GPT-5.6 行使用 922,000-token 目录窗口。 | +| Codex 登录（账户限定的选择器行未启用） | 显示 `gpt-5.6-sol`、`gpt-5.6-terra`、`gpt-5.6-luna` 等裸原生 id，并按 `codexAccountMode` 使用 Pool 或 Direct。GPT-5.6 行使用 922,000-token 目录窗口。 `gpt-6.1-terra`：默认上下文 500,000 / 长上下文 872,000。 | | Codex 登录（账户限定的选择器行已启用且存在有效 selector） | 为每个有效 selector 与受支持原生模型的组合显示 `/` 行。每行只使用映射账户，裸原生行会从选择器中隐藏。原生 metadata 与 context window 会保留。 | -| OpenAI（API key） | 恰好八个命名空间行：`gpt-5.5`、`gpt-5.6`、Sol/Terra/Luna，以及三个 `*-pro` 虚拟 id（八个条目均为 1,050,000 context / 922,000 max input） | +| OpenAI（API key） | 命名空间模型包括 `gpt-5.5`、`gpt-5.6`、Sol/Terra/Luna、`*-pro` 虚拟 id 和 Daybreak 别名（上下文 1,050,000；最大输入 922,000）。`openai-apikey/gpt-6.1-terra` 的上下文为 1,050,000，最大输出为 128,000。 | | OpenRouter | `openrouter/openai/gpt-5.6-sol`、`openrouter/openai/gpt-5.6-terra`、`openrouter/openai/gpt-5.6-luna`（922,000） | +| OpenRouter | `openrouter/openai/gpt-6.1-terra` (1,050,000) | | Cursor | 静态回退包含 `cursor/gpt-5.6-sol`、`cursor/gpt-5.6-terra`、`cursor/gpt-5.6-luna`（1,000,000），以及 Grok 4.5/4.6/4.7 的普通和 Fast 条目（500,000）。4.6 和 4.7 还提供 `xhigh`；实时账户发现会决定最终哪些条目仍然可见。 | | xAI | 实时发现具有权威性。回退目录包含 `xai/grok-4.6` 和 `xai/grok-4.7`，默认模型仍为 `xai/grok-4.5`；三者的上下文窗口均为 500,000。Grok 4.6 和 4.7 提供 `low` / `medium` / `high` / `xhigh`（上游默认值为 `high`），Grok 4.5 最高为 `high`。 | diff --git a/docs-site/src/content/docs/zh-cn/guides/model-ordering.md b/docs-site/src/content/docs/zh-cn/guides/model-ordering.md index ffe4ffda879..b1af2ed77e3 100644 --- a/docs-site/src/content/docs/zh-cn/guides/model-ordering.md +++ b/docs-site/src/content/docs/zh-cn/guides/model-ordering.md @@ -6,6 +6,8 @@ description: opencodex 如何确定 Codex 模型选择器和 spawn_agent 模型 Codex 模型选择器不会保留 opencodex 配置中 provider 的声明顺序或模型数组顺序。最终顺序由目录 priority 决定；priority 相同的路由模型则使用确定性的字母顺序。 +除了 `gpt-5.6-terra`，还可以选择 `gpt-6.1-terra`；默认模型和子代理模型列表均不变。参见 [GPT-6.1 Terra 的限制、推理与 Fast](/zh-cn/reference/configuration/providers/#gpt-61-terra)。 + ## Codex 应用的规则 Codex 的 models-manager 按 `priority` 升序排列选择器中可见的目录条目。目录数组本身的顺序会被 diff --git a/docs-site/src/content/docs/zh-cn/guides/providers.md b/docs-site/src/content/docs/zh-cn/guides/providers.md index cdf84045d8a..9f96a22e6cd 100644 --- a/docs-site/src/content/docs/zh-cn/guides/providers.md +++ b/docs-site/src/content/docs/zh-cn/guides/providers.md @@ -5,6 +5,8 @@ description: opencodex 进行身份验证并与 LLM 提供商通信的所有方 **提供商（provider）** 是一个上游 LLM 端点，加上访问它的方式：一个 adapter、一个基础 URL、一种认证模式，以及一个可选的模型列表。提供商配置位于 `~/.opencodex/config.json` 的 `providers` 下。 +除了 `gpt-5.6-terra`，还可以选择 `gpt-6.1-terra`；默认模型和子代理模型列表均不变。参见 [GPT-6.1 Terra 的限制、推理与 Fast](/zh-cn/reference/configuration/providers/#gpt-61-terra)。 + ## OpenAI 账户模式 | Provider id | 用途 | 凭证/账户规则 | @@ -503,6 +505,9 @@ GPT-5.6 Sol/Terra/Luna 会预置在提供商的回退列表中，因此即使实 | Codex 登录（Pool 或 Direct） | `gpt-5.6-*` | 922,000 | | OpenAI (API key) | `openai-apikey/gpt-5.6-*` 和 `*-pro` | 922,000（max input 922,000） | | OpenRouter | `openrouter/openai/gpt-5.6-sol`、`openrouter/openai/gpt-5.6-terra`、`openrouter/openai/gpt-5.6-luna` | 922,000 | +| Codex | `gpt-6.1-terra` | 500,000 / 872,000 | +| OpenAI API | `openai-apikey/gpt-6.1-terra` | 1,050,000 (128,000 max output) | +| OpenRouter | `openrouter/openai/gpt-6.1-terra` | 1,050,000 | | Cursor | `cursor/gpt-5.6-sol`、`cursor/gpt-5.6-terra`、`cursor/gpt-5.6-luna` | 1,000,000 | 原生 GPT-5.6 条目保留固定的上游 reasoning 档位，例如 Luna 有 `max`，但没有 `ultra`。路由条目 @@ -535,7 +540,7 @@ GitHub 可能改变协议或账户权限。Auto 每次请求使用选中模型 不是已公布的 GitHub 限制；过大的目录、缓慢的协商或意图文本截断都可能影响兼容性。 具名选择时，Copilot 提供混合 wire 目录：其模型（`gpt-5.3-codex`、`gpt-5.4`、 -`gpt-5.4-mini`、`gpt-5.5`、`gpt-5.6-luna`、`gpt-5.6-sol`、`gpt-5.6-terra`、`gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`）会拒绝面向 +`gpt-5.4-mini`、`gpt-5.5`、`gpt-5.6-luna`、`gpt-5.6-sol`、`gpt-5.6-terra`、 `gpt-6.1-sol`、 `gpt-6.1-terra`、 `gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`）会拒绝面向 agent 流量的 `/chat/completions`，因此 opencodex 默认将这些模型路由到 Responses API，而其他 Copilot 模型仍走 chat completions。优先级为：硬 wire 固定 → 显式 [`modelAdapters`](/zh-cn/reference/configuration/providers/) 条目 → 注册表默认值 → 提供商级 diff --git a/docs-site/src/content/docs/zh-cn/reference/adapters.md b/docs-site/src/content/docs/zh-cn/reference/adapters.md index 512277d38fa..557f21aedac 100644 --- a/docs-site/src/content/docs/zh-cn/reference/adapters.md +++ b/docs-site/src/content/docs/zh-cn/reference/adapters.md @@ -22,6 +22,8 @@ interface ProviderAdapter { 无法表示成一次 HTTP fetch 加一条响应流的 transport。随后 [`bridge.ts`](/zh-cn/reference/architecture/#桥接器) 把 event 转成 Responses SSE。 +除了 `gpt-5.6-terra`，还可以选择 `gpt-6.1-terra`；默认模型和子代理模型列表均不变。参见 [GPT-6.1 Terra 的限制、推理与 Fast](/zh-cn/reference/configuration/providers/#gpt-61-terra)。 + ## `openai-chat` **目标：** OpenAI **Chat Completions**（`POST {baseUrl}/chat/completions`）以及所有兼容 provider， diff --git a/docs-site/src/content/docs/zh-cn/reference/configuration/providers.md b/docs-site/src/content/docs/zh-cn/reference/configuration/providers.md index 6a26f9cab26..bbe40d89bbc 100644 --- a/docs-site/src/content/docs/zh-cn/reference/configuration/providers.md +++ b/docs-site/src/content/docs/zh-cn/reference/configuration/providers.md @@ -11,6 +11,16 @@ description: 提供者条目、身份验证、端点、模型目录、配额、 该推断默认关闭，需要按渠道设置 `inferContextWindow: true` 开启。未开启时，缺少窗口的模型使用已启用的 Context cap，否则回退到 128k。 +## GPT-6.1 Terra + +[GPT-6.1 Terra](https://openai.com/index/introducing-gpt-6-1-terra/) 于 2026年10月26日发布，是 GPT-5.6 Terra 的后继型号。`gpt-6.1-terra` 与 `gpt-5.6-terra` 并列提供，不修改默认模型或子代理列表。GitHub Copilot 使用 Responses；OpenRouter ID 为 `openai/gpt-6.1-terra`，上下文为 1,050,000，每百万 token 输入 $1.00、输出 $5.00。 + +原生 Codex：默认上下文 500,000，长上下文上限 872,000，默认 effort 为 `low`，级别为 `low`、`medium`、`high`、`xhigh`、`max`、`ultra`。原生 `ultra` 在传输时映射为 `max`。原生条目仅提供 Fast 高速模式。 + +[OpenAI API](https://developers.openai.com/api/docs/models/gpt-6.1-terra)：上下文 1,050,000，最大输出 128,000；支持文本和图像输入、文本输出；知识截止日期为 2026-06-01。effort 为 `none`、`low`、`medium`（默认）、`high`、`xhigh`、`max`。端点为 `v1/responses` 和 `v1/chat/completions`；工具调用必须使用 Responses。 + +每百万 token：输入 $1.00、缓存输入 $0.05、缓存写入 $1.25（30分钟）、输出 $5.00。输入超过 272,000 token 时，整个请求按输入和缓存 2×、输出 1.5×计费，依次为 $2.00 / $0.10 / $2.50 / $7.50。Fast 模式价格为 2×。 + ## 首次注册时的模型选择 新的非 OAuth 连接会等待可靠的模型列表，再公开模型。如果 Models 标签页中去重后的模型行达到20个，所有模型开关初始为 OFF，但提供者本身保持 ACTIVE。实际认证方式为 OAuth 或 ChatGPT 登录的连接保留默认设置。 @@ -128,7 +138,7 @@ selector，而不是分配一个新名称。 | `modelReasoningEfforts?` | `Record` | 按模型设置的标签。空列表会隐藏 effort 控件。 | | `modelSupportsReasoningSummaries?` | `Record` | 将某个模型设为 `false`，即可停止暴露摘要并移除摘要交付字段。 | | `modelReasoningSummaryDelivery?` | `Record` | 按模型设置的 Responses 交付枚举；会重写现有的 delivery 字段。 | -| `modelAdapters?` | `Record` | 按模型设置的 `openai-chat` 或 `openai-responses` 线协议覆盖项，用于混合线协议网关。显式条目优先于注册表默认值；DeepSeek 预设可以为 `deepseek-v4-flash` 选择原生 Responses，GitHub Copilot 则为 模型（`gpt-5.3-codex`、`gpt-5.4`、`gpt-5.4-mini`、`gpt-5.5`、`gpt-5.6-luna`、`gpt-5.6-sol`、`gpt-5.6-terra`、`gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`）声明了 Responses 专用默认值，因为这些模型在代理流量下会拒绝 `/chat/completions`。没有内置默认值的模型（例如 `gpt-5.4-nano`）可以在此手动启用。单一线协议上游固定项和规范 ChatGPT forward 会拒绝覆盖。 | +| `modelAdapters?` | `Record` | 按模型设置的 `openai-chat` 或 `openai-responses` 线协议覆盖项，用于混合线协议网关。显式条目优先于注册表默认值；DeepSeek 预设可以为 `deepseek-v4-flash` 选择原生 Responses，GitHub Copilot 则为 模型（`gpt-5.3-codex`、`gpt-5.4`、`gpt-5.4-mini`、`gpt-5.5`、`gpt-5.6-luna`、`gpt-5.6-sol`、`gpt-5.6-terra`, `gpt-6.1-sol`, `gpt-6.1-terra`、`gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`）声明了 Responses 专用默认值，因为这些模型在代理流量下会拒绝 `/chat/completions`。没有内置默认值的模型（例如 `gpt-5.4-nano`）可以在此手动启用。单一线协议上游固定项和规范 ChatGPT forward 会拒绝覆盖。 | | xAI Responses 启用项（仪表板） | 开关 | 仅用于 `xai`，以原子方式设置或清除 `grok-4.5` 和 `grok-4.6` 的 `modelAdapters` 条目。若只存在一个条目，则显示混合状态，直到下次开关写入将两者统一。其他覆盖项和层级行为不变。 Grok 4.7 在 OAuth 上通过注册表线协议默认使用 Responses，也可通过显式的 `modelAdapters["grok-4.7"] = "openai-chat"` 条目切换到 Chat。 | | `xaiResponsesXSearch?` | `boolean` | 默认禁用。在 xAI Responses 目标上，仅当有效的 `web_search` 工具在最终请求规范化后仍保留时，才附加由提供方托管的 `x_search` 声明。不会重复已有声明，绝不会扩大调用方的 `tool_choice`/`allowed_tools` 选择范围，并且此项独立于网络搜索辅助服务的 `search.xSearch` 选项。 | | `modelPreferHostedTools?` | `Record` | 非 forward Responses gateway 的精确模型 ID opt-in，用于上游预留 hosted tool namespace 的情况。目前只支持 `["image_generation"]`；匹配模型必须使用 `openai-responses` wire 且支持该 hosted 工具。它会移除冲突的客户端 `image_gen` 声明，并改写其 selector 以保持调用方的 tool choice。对于 OpenAI API 的虚拟 `-pro` 模型，先匹配所选公开 ID，未命中时才使用解析出的基础 wire-model ID 作为回退。`modelAdapters` 会先按公开 ID、再按基础 ID 解析；后一次结果决定最终 wire。未配置模型保持普通 alias 行为。 | diff --git a/docs-site/src/content/docs/zh-cn/reference/configuration/routing.md b/docs-site/src/content/docs/zh-cn/reference/configuration/routing.md index 721b5d87873..85251829f3c 100644 --- a/docs-site/src/content/docs/zh-cn/reference/configuration/routing.md +++ b/docs-site/src/content/docs/zh-cn/reference/configuration/routing.md @@ -5,6 +5,8 @@ description: 默认提供方选择、模型解析顺序、组合别名、目标 路由会把客户端发送的 model id 转换为一个具体的提供方和上游模型。 +除了 `gpt-5.6-terra`，还可以选择 `gpt-6.1-terra`；默认模型和子代理模型列表均不变。参见 [GPT-6.1 Terra 的限制、推理与 Fast](/zh-cn/reference/configuration/providers/#gpt-61-terra)。 + ## 顶层路由字段 | 字段 | 类型 | 默认值 | 含义 | diff --git a/docs-site/src/content/docs/zh-tw/getting-started/quickstart.md b/docs-site/src/content/docs/zh-tw/getting-started/quickstart.md index ea72d3cfcae..2a427c87b6a 100644 --- a/docs-site/src/content/docs/zh-tw/getting-started/quickstart.md +++ b/docs-site/src/content/docs/zh-tw/getting-started/quickstart.md @@ -5,6 +5,8 @@ description: 設定你的第一個 provider,用三條命令讓 OpenAI Codex 透 本指南將帶你從全新安裝,一路走到用一個非 OpenAI 模型執行 Codex。 +除了 `gpt-5.6-terra`，也可以選擇 `gpt-6.1-terra`；預設模型與子代理模型清單均不變。參見 [GPT-6.1 Terra 的限制、推理與 Fast](/zh-tw/reference/configuration/providers/#gpt-61-terra)。 + ## 1. 執行設定嚮導 ```bash diff --git a/docs-site/src/content/docs/zh-tw/guides/codex-app-models.md b/docs-site/src/content/docs/zh-tw/guides/codex-app-models.md index 176a68a8bfd..5cb15ead14b 100644 --- a/docs-site/src/content/docs/zh-tw/guides/codex-app-models.md +++ b/docs-site/src/content/docs/zh-tw/guides/codex-app-models.md @@ -45,6 +45,8 @@ cp ~/.opencodex/config.json.pre-openai-tiers-v2.bak ~/.opencodex/config.json 較早的 v1 三 provider 設定會自動遷移為單一的 option-aware 列。 +除了 `gpt-5.6-terra`，也可以選擇 `gpt-6.1-terra`；預設模型與子代理模型清單均不變。參見 [GPT-6.1 Terra 的限制、推理與 Fast](/zh-tw/reference/configuration/providers/#gpt-61-terra)。 + ## Desktop 遠端 allowlist 限制 如果 `codex debug models` 和 app-server 的 `model/list` 都包含某個路由模型，但 Desktop 沒有 @@ -86,10 +88,11 @@ GPT-5.6，以便提供每個模型真實的身份和後設資料，而不是套 | 路由 | 選擇器 id 與目錄後設資料 | | --- | --- | -| Codex 登入（停用帳號限定列） | 裸原生 id，例如 `gpt-5.6-sol`、`gpt-5.6-terra`、`gpt-5.6-luna`；透過 `codexAccountMode` 選擇 Pool 或 Direct。GPT-5.6 列使用 922,000 token 的目錄視窗。 | +| Codex 登入（停用帳號限定列） | 裸原生 id，例如 `gpt-5.6-sol`、`gpt-5.6-terra`、`gpt-5.6-luna`；透過 `codexAccountMode` 選擇 Pool 或 Direct。GPT-5.6 列使用 922,000 token 的目錄視窗。 `gpt-6.1-terra`：預設上下文 500,000 / 長上下文 872,000。 | | Codex 登入（啟用帳號限定列且有合格選擇器） | 每個合格選擇器與受支援的原生模型各有一列 `/`；每列只使用其對應帳號，且裸原生列會從選擇器中隱藏。原生後設資料與 context 視窗保持不變。 | -| OpenAI（API key） | 恰好八個帶名稱空間的列：`gpt-5.5`、`gpt-5.6`、Sol/Terra/Luna 與三個 `*-pro` 虛擬 id（全部八個都是 1,050,000 context；922,000 max input） | +| OpenAI（API key） | 帶命名空間的模型包括 `gpt-5.5`、`gpt-5.6`、Sol/Terra/Luna、`*-pro` 虛擬 id 與 Daybreak 別名（上下文 1,050,000；最大輸入 922,000）。`openai-apikey/gpt-6.1-terra` 的上下文為 1,050,000，最大輸出為 128,000。 | | OpenRouter | `openrouter/openai/gpt-5.6-sol`、`openrouter/openai/gpt-5.6-terra`、`openrouter/openai/gpt-5.6-luna`（922,000） | +| OpenRouter | `openrouter/openai/gpt-6.1-terra` (1,050,000) | | Cursor | 靜態回退目錄包含 `cursor/gpt-5.6-sol`、`cursor/gpt-5.6-terra`、`cursor/gpt-5.6-luna`（1,000,000），以及 Grok 4.5/4.6/4.7 的一般與 Fast 項目（500,000）。4.6 和 4.7 還提供 `xhigh`；帳號的即時發現結果決定最終顯示哪些模型。 | | xAI | 以即時發現結果為準。回退目錄包含 `xai/grok-4.6` 與 `xai/grok-4.7`，預設模型仍為 `xai/grok-4.5`；三者的 context window 均為 500,000。Grok 4.6 與 4.7 提供 `low` / `medium` / `high` / `xhigh`（上游預設值為 `high`），Grok 4.5 最高為 `high`。 | diff --git a/docs-site/src/content/docs/zh-tw/guides/model-ordering.md b/docs-site/src/content/docs/zh-tw/guides/model-ordering.md index d944aef1993..c9c42f0f3ba 100644 --- a/docs-site/src/content/docs/zh-tw/guides/model-ordering.md +++ b/docs-site/src/content/docs/zh-tw/guides/model-ordering.md @@ -6,6 +6,8 @@ description: opencodex 如何確定 Codex 模型選擇器和 spawn_agent 模型 Codex 模型選擇器不會保留 opencodex 設定中 provider 的宣告順序或模型陣列順序。最終順序由目錄 priority 決定；priority 相同的路由模型則使用確定性的字母順序。 +除了 `gpt-5.6-terra`，也可以選擇 `gpt-6.1-terra`；預設模型與子代理模型清單均不變。參見 [GPT-6.1 Terra 的限制、推理與 Fast](/zh-tw/reference/configuration/providers/#gpt-61-terra)。 + ## Codex 應用的規則 Codex 的 models-manager 按 `priority` 升序排列選擇器中可見的目錄條目。目錄陣列本身的順序會被 diff --git a/docs-site/src/content/docs/zh-tw/guides/providers.md b/docs-site/src/content/docs/zh-tw/guides/providers.md index 460b9b85b70..0a28ca7ab97 100644 --- a/docs-site/src/content/docs/zh-tw/guides/providers.md +++ b/docs-site/src/content/docs/zh-tw/guides/providers.md @@ -6,6 +6,8 @@ description: opencodex 進行身分驗證並與 LLM 供應商通訊的所有方 **供應商（provider）** 是一個上游 LLM 端點，加上存取它的方式：adapter、base URL、認證模式，以及 可選的模型列表。供應商設定放在 `~/.opencodex/config.json` 的 `providers` 下。 +除了 `gpt-5.6-terra`，也可以選擇 `gpt-6.1-terra`；預設模型與子代理模型清單均不變。參見 [GPT-6.1 Terra 的限制、推理與 Fast](/zh-tw/reference/configuration/providers/#gpt-61-terra)。 + ## OpenAI 帳號模式 | Provider id | 用途 | 憑證／帳號規則 | @@ -533,6 +535,9 @@ GPT-5.6 Sol/Terra/Luna 會預置在 provider fallback list 中，因此即使即 | Codex 登入（Pool 或 Direct） | `gpt-5.6-*` | 922,000 | | OpenAI (API key) | `openai-apikey/gpt-5.6-*` 加 `*-pro` | 922,000（922,000 max input） | | OpenRouter | `openrouter/openai/gpt-5.6-sol`、`openrouter/openai/gpt-5.6-terra`、`openrouter/openai/gpt-5.6-luna` | 922,000 | +| Codex | `gpt-6.1-terra` | 500,000 / 872,000 | +| OpenAI API | `openai-apikey/gpt-6.1-terra` | 1,050,000 (128,000 max output) | +| OpenRouter | `openrouter/openai/gpt-6.1-terra` | 1,050,000 | | Cursor | `cursor/gpt-5.6-sol`、`cursor/gpt-5.6-terra`、`cursor/gpt-5.6-luna` | 1,000,000 | 原生 GPT-5.6 條目保留固定的上游 reasoning ladder，例如 Luna 有 `max` 但沒有 `ultra`。路由條目使用各 @@ -550,7 +555,7 @@ Antigravity／Cloud Code Assist 模式）、`azure` / `azure-openai`、`kiro`、 key／subscription-token gateway。**Cloudflare AI Gateway** 需要在 URL 填入 account 與 gateway id。 Copilot 的 catalog 混合多種 wire：模型（`gpt-5.3-codex`、`gpt-5.4`、`gpt-5.4-mini`、 -`gpt-5.5`、`gpt-5.6-luna`、`gpt-5.6-sol`、`gpt-5.6-terra`、`gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`）會拒絕 agent traffic 的 +`gpt-5.5`、`gpt-5.6-luna`、`gpt-5.6-sol`、`gpt-5.6-terra`、 `gpt-6.1-sol`、 `gpt-6.1-terra`、 `gpt-6-astra`, `grok-4.5`, `grok-4.6`, `mai-code-1.1-flash`, `mai-code-1-flash-picker`）會拒絕 agent traffic 的 `/chat/completions`，因此 opencodex 會依內建預設把這些模型路由到 Responses API；其他 Copilot 模型 仍使用 chat completions。優先順序為：hard wire pin → 你明確設定的 [`modelAdapters`](/zh-tw/reference/configuration/providers/) → registry default → provider-wide adapter。 diff --git a/docs-site/src/content/docs/zh-tw/guides/sub-agent-surface.md b/docs-site/src/content/docs/zh-tw/guides/sub-agent-surface.md index a27641478fd..6f9d6cdf2f8 100644 --- a/docs-site/src/content/docs/zh-tw/guides/sub-agent-surface.md +++ b/docs-site/src/content/docs/zh-tw/guides/sub-agent-surface.md @@ -20,7 +20,7 @@ opencodex 允許你為目錄中的所有模型選擇多代理協作介面。儀 | 模式 | 介面 | 行為 | | --- | --- | --- | | **v1** | `multi_agent_v1` | 使用經典的名稱空間代理工具，以及 `send_input` / `close_agent` / `resume_agent`。`spawn_agent` 的模型覆蓋可以在其他模型上生成子代理。 | -| **base**（預設） | 上游固定值 | 恢復上游模型的固定值：gpt-5.6-sol 和 gpt-5.6-terra 使用 v2，gpt-5.6-luna 使用 v1；未固定的模型遵循 Codex 的 `multi_agent_v2` 功能開關。生成行為取決於該模型最終使用的介面。 | +| **base**（預設） | 上游固定值 | 恢復上游模型的固定值：gpt-5.6-sol、gpt-5.6-terra 和 gpt-6.1-terra 使用 v2，gpt-5.6-luna 使用 v1；未固定的模型遵循 Codex 的 `multi_agent_v2` 功能開關。生成行為取決於該模型最終使用的介面。 | | **v2** | `multi_agent_v2` | 使用扁平的 `spawn_agent` 工具、併發會話，以及 `send_message` / `followup_task` / `wait_agent` / `interrupt_agent`。全量歷史 fork 時子代理繼承父模型；`fork_turns: "none"`（或部分 fork）時接受 `model` / `reasoning_effort` 覆蓋。如果原生→路由子代理只收到後端加密的任務內容，未明確信任的外部路由會回傳 `unreadable_encrypted_agent_task`；明確信任的直接金鑰驗證 Responses 路由可以原樣接收，而混合組合仍優先選擇可解密的原生目標（[#92](https://github.com/lidge-jun/opencodex/issues/92)）。 | ## 運作原理 @@ -256,7 +256,7 @@ opencodex 會將磁碟上的模型目錄與目前使用者擁有的每個 Codex | 模型 | 線路上的 `max` | 選擇 `ultra` 後的線路值 | | --- | --- | --- | | gpt-5.5 | xhigh | xhigh（先轉為 max，再經 `nativeEffortClamp`） | -| gpt-5.6-sol、gpt-5.6-terra | max | max | +| gpt-5.6-sol、gpt-5.6-terra、gpt-6.1-terra | max | max | | gpt-5.6-luna | max | 其精確上游階梯不提供該選項 | | 路由模型 | 由適配器對映或限制 | 先轉為 max，再由適配器對映或限制 | diff --git a/docs-site/src/content/docs/zh-tw/reference/adapters.md b/docs-site/src/content/docs/zh-tw/reference/adapters.md index 37ac0080cd5..aadd0493a54 100644 --- a/docs-site/src/content/docs/zh-tw/reference/adapters.md +++ b/docs-site/src/content/docs/zh-tw/reference/adapters.md @@ -22,6 +22,8 @@ interface ProviderAdapter { 無法表示成一次 HTTP fetch 加一條回應流的 transport。隨後 [`bridge.ts`](/zh-tw/reference/architecture/#橋接器) 把 event 轉成 Responses SSE。 +除了 `gpt-5.6-terra`，也可以選擇 `gpt-6.1-terra`；預設模型與子代理模型清單均不變。參見 [GPT-6.1 Terra 的限制、推理與 Fast](/zh-tw/reference/configuration/providers/#gpt-61-terra)。 + ## `openai-chat` **目標：** OpenAI **Chat Completions**（`POST {baseUrl}/chat/completions`）以及所有相容 provider， diff --git a/docs-site/src/content/docs/zh-tw/reference/configuration/providers.md b/docs-site/src/content/docs/zh-tw/reference/configuration/providers.md index 183cdf3a409..042eeefef15 100644 --- a/docs-site/src/content/docs/zh-tw/reference/configuration/providers.md +++ b/docs-site/src/content/docs/zh-tw/reference/configuration/providers.md @@ -11,6 +11,16 @@ description: 供應商項目、認證、端點、模型目錄、配額、context 此推斷預設關閉，需按供應商設定 `inferContextWindow: true` 開啟。未開啟時，缺少視窗的模型使用已啟用的 Context cap，否則回退至 128k。 +## GPT-6.1 Terra + +[GPT-6.1 Terra](https://openai.com/index/introducing-gpt-6-1-terra/) 於 2026年10月26日發布，是 GPT-5.6 Terra 的後繼型號。`gpt-6.1-terra` 與 `gpt-5.6-terra` 並列提供，不修改預設模型或子代理清單。GitHub Copilot 使用 Responses；OpenRouter ID 為 `openai/gpt-6.1-terra`，上下文為 1,050,000，每百萬 token 輸入 $1.00、輸出 $5.00。 + +原生 Codex：預設上下文 500,000，長上下文上限 872,000，預設 effort 為 `low`，級別為 `low`、`medium`、`high`、`xhigh`、`max`、`ultra`。原生 `ultra` 在傳輸時對應至 `max`。原生項目僅提供 Fast 高速模式。 + +[OpenAI API](https://developers.openai.com/api/docs/models/gpt-6.1-terra)：上下文 1,050,000，最大輸出 128,000；支援文字與影像輸入、文字輸出；知識截止日期為 2026-06-01。effort 為 `none`、`low`、`medium`（預設）、`high`、`xhigh`、`max`。端點為 `v1/responses` 和 `v1/chat/completions`；工具呼叫必須使用 Responses。 + +每百萬 token：輸入 $1.00、快取輸入 $0.05、快取寫入 $1.25（30分鐘）、輸出 $5.00。輸入超過 272,000 token 時，整個請求按輸入與快取 2×、輸出 1.5×計費，依序為 $2.00 / $0.10 / $2.50 / $7.50。Fast 模式價格為 2×。 + ## 首次註冊時的模型選擇 新的非 OAuth 連線會先等待可靠的模型清單，再公開模型。如果 Models 分頁中去重後的模型列達到20個，所有模型開關初始為 OFF，但供應商本身保持 ACTIVE。實際驗證方式為 OAuth 或 ChatGPT 登入的連線保留預設值。 @@ -103,7 +113,7 @@ ocx models provider openrouter on | `modelReasoningEfforts?` | `Record` | Per-model 標籤。空清單隱藏 effort 控制。 | | `modelSupportsReasoningSummaries?` | `Record` | 將模型設為 `false` 以停止廣告摘要並剝離 summary-delivery 欄位。 | | `modelReasoningSummaryDelivery?` | `Record` | Per-model Responses delivery 列舉；重寫既有的 delivery 欄位。 | -| `modelAdapters?` | `Record` | 混合 wire 閘道的 Per-model `openai-chat` 或 `openai-responses` wire 覆寫。明確項目勝過 registry 預設；DeepSeek 的預設可為 `deepseek-v4-flash` 選擇原生 Responses。單一 wire 上游 pin 與規範 ChatGPT forward 拒絕覆寫。 | +| `modelAdapters?` | `Record` | 混合 wire 閘道的 Per-model `openai-chat` 或 `openai-responses` wire 覆寫。明確項目勝過 registry 預設；DeepSeek 的預設可為 `deepseek-v4-flash` 選擇原生 Responses。單一 wire 上游 pin 與規範 ChatGPT forward 拒絕覆寫。 GitHub Copilot 為 `gpt-6.1-sol` 與 `gpt-6.1-terra` 使用 Responses。 | | xAI Responses 選用（儀表板） | 開關 | 僅用於 `xai`，以原子方式設定或清除 `grok-4.5` 與 `grok-4.6` 的 `modelAdapters` 項目。若只有一個項目，會顯示混合狀態，直到下次開關寫入統一兩者。其他覆寫與層級行為不變。 Grok 4.7 在 OAuth 上透過登錄檔 wire 預設使用 Responses，也可透過明確的 `modelAdapters["grok-4.7"] = "openai-chat"` 項目切換至 Chat。 | | `annotateEmptyToolOutputs?` | `boolean` | 在工具結果送達模型前，將已存在但為空的結果替換成簡短標記，使空白結果不會被解讀為遺漏的結果。適用於空白字串及僅含文字部分的陣列；影像、檔案及加密部分絕不會被更動。DeepSeek 透過內建登錄檔預設為 `true`，其他情況則不設定。設為 `false` 可讓供應商停用此功能；後續編輯即使省略此欄位，也會保留明確設定的 `false`。`PATCH /api/providers?name=` 接受 `true`、`false` 或 `null`；`null` 會清除覆寫並恢復使用登錄檔的預設行為。 | | `xaiResponsesXSearch?` | `boolean` | 預設停用。在 xAI Responses 目的地上，僅當即時 `web_search` 工具通過最終請求正規化後仍保留時，才附加由供應商託管的 `x_search` 宣告。既有宣告不會重複，呼叫端的 `tool_choice`／`allowed_tools` 選擇器絕不會擴大，且此設定與網頁搜尋輔助服務的 `search.xSearch` 選項分開。 | diff --git a/docs-site/src/content/docs/zh-tw/reference/configuration/routing.md b/docs-site/src/content/docs/zh-tw/reference/configuration/routing.md index 4dd6d004fe6..201b28ecc8f 100644 --- a/docs-site/src/content/docs/zh-tw/reference/configuration/routing.md +++ b/docs-site/src/content/docs/zh-tw/reference/configuration/routing.md @@ -5,6 +5,8 @@ description: 預設供應商選擇、模型解析順序、combo 別名、目標 路由將客戶端送出的模型 id 轉為一個具體的供應商與上游模型。 +除了 `gpt-5.6-terra`，也可以選擇 `gpt-6.1-terra`；預設模型與子代理模型清單均不變。參見 [GPT-6.1 Terra 的限制、推理與 Fast](/zh-tw/reference/configuration/providers/#gpt-61-terra)。 + ## 頂層路由欄位 | 欄位 | 型別 | 預設值 | 意義 | diff --git a/scripts/test-layout/layout.json b/scripts/test-layout/layout.json index 20f93f9e0ec..ac24774a337 100644 --- a/scripts/test-layout/layout.json +++ b/scripts/test-layout/layout.json @@ -911,7 +911,7 @@ "devin-reasoning-continuation.test.ts": "providers", "devin-stream-deadline.test.ts": "providers", "digitalocean-scaleway-provider.test.ts": "providers", - "docs-429-failover-claims.test.ts": "ci-workflows", + "docs-429-failover-claims.test.ts": "ci-workflows", "docs-gpt61-terra.test.ts": "ci-workflows", "docs-bun-source-requirement.test.ts": "ci-workflows", "docs-developer-role-policy.test.ts": "ci-workflows", "docs-gui-screenshot-policy.test.ts": "ci-workflows", diff --git a/tests/ci-workflows/docs-gpt61-terra.test.ts b/tests/ci-workflows/docs-gpt61-terra.test.ts new file mode 100644 index 00000000000..2278bc58532 --- /dev/null +++ b/tests/ci-workflows/docs-gpt61-terra.test.ts @@ -0,0 +1,56 @@ +import { describe, expect, test } from "bun:test"; +import { readdirSync, readFileSync } from "node:fs"; +import { repoPath } from "../helpers/repo-root"; + +const root = "docs-site/src/content/docs"; +// Discover translations from the content tree so a new locale cannot silently drift. +const locales = ["", ...readdirSync(repoPath(root), { withFileTypes: true }) + .filter(entry => entry.isDirectory() && /^[a-z]{2}(?:-[a-z]{2})?$/.test(entry.name)) + .map(entry => entry.name)]; +const read = (locale: string, page: string) => + readFileSync(repoPath(root, locale, page + ".md"), "utf8"); + +describe("GPT-6.1 Terra documentation", () => { + for (const locale of locales) { + test(`${locale || "en"}: native and API limits, pricing and Fast stay distinct`, () => { + const doc = read(locale, "reference/configuration/providers"); + const section = doc.split("## GPT-6.1 Terra")[1]?.split(/\n## /)[0]; + expect(section).toBeDefined(); + for (const value of ["gpt-6.1-terra", "gpt-5.6-terra", "500,000", "872,000", + "1,050,000", "128,000", "low", "ultra", "max", "none", "medium", + "$1.00", "$0.05", "$1.25", "$5.00", "272,000", "$2.00", "$0.10", + "$2.50", "$7.50", "Fast", "2026-06-01", "v1/responses", "v1/chat/completions"]) { + expect(section, `${locale}: ${value}`).toContain(value); + } + expect(section).not.toMatch(/Ultrafast|ultrafast/); + }); + + test(`${locale || "en"}: affected guides link to Terra without replacing older models`, () => { + for (const page of ["guides/providers", "guides/codex-app-models", "guides/model-ordering", + "getting-started/quickstart", "reference/adapters", "reference/configuration/routing"]) { + const doc = read(locale, page); + expect(doc, `${locale}/${page}`).toContain("gpt-6.1-terra"); + expect(doc).toContain("gpt-5.6-terra"); + expect(doc).toContain("/reference/configuration/providers/#gpt-61-terra"); + expect(doc.split("\n").filter(line => line.startsWith("| Cursor |")) + .join("\n")).not.toContain("gpt-6.1-terra"); + } + expect(read(locale, "reference/configuration/agents") + .split("\n").find(line => line.startsWith("| `subagentModels?`"))) + .not.toContain("gpt-6.1-terra"); + expect(read(locale, "guides/cursor-private-inference")).not.toContain("gpt-6.1-terra"); + }); + + test(`${locale || "en"}: OpenRouter and Copilot availability includes Terra`, () => { + for (const page of ["guides/providers", "guides/codex-app-models"]) { + const rows = read(locale, page).split("\n"); + const terra = rows.find(line => line.startsWith("| OpenRouter |") && line.includes("gpt-6.1-terra")); + expect(terra).toContain("openrouter/openai/gpt-6.1-terra"); + expect(terra).toContain("1,050,000"); + } + expect(read(locale, "reference/configuration/providers") + .split("\n").find(line => line.startsWith("| `modelAdapters?`"))) + .toContain("gpt-6.1-terra"); + }); + } +}); diff --git a/tests/fixtures/test-layout-expected.json b/tests/fixtures/test-layout-expected.json index 2d9d35496e3..d3b26cfd9ea 100644 --- a/tests/fixtures/test-layout-expected.json +++ b/tests/fixtures/test-layout-expected.json @@ -712,6 +712,7 @@ "devin-reasoning-continuation.test.ts": "providers", "devin-stream-deadline.test.ts": "providers", "digitalocean-scaleway-provider.test.ts": "providers", "docs-429-failover-claims.test.ts": "ci-workflows", "docs-bun-source-requirement.test.ts": "ci-workflows", "docs-developer-role-policy.test.ts": "ci-workflows", + "docs-gpt61-terra.test.ts": "ci-workflows", "docs-gui-screenshot-policy.test.ts": "ci-workflows", "docs-link-targets.test.ts": "ci-workflows", "docs-gjc-reasoning-export.test.ts": "ci-workflows", "docs-provider-billing-claims.test.ts": "ci-workflows", "docs-provider-discovery-limits.test.ts": "ci-workflows", "docs-provider-preset-counts.test.ts": "ci-workflows", From 452bbe654f3dd7cc82313613a9045977b7687080 Mon Sep 17 00:00:00 2001 From: JUN <243035832+lidge-jun@users.noreply.github.com> Date: Tue, 27 Oct 2026 08:35:29 +0900 Subject: [PATCH 3/9] docs(models): drop repeated Terra cross-link paragraphs and source comments --- docs-site/src/content/docs/fr/getting-started/quickstart.md | 2 -- docs-site/src/content/docs/fr/guides/codex-app-models.md | 2 -- docs-site/src/content/docs/fr/guides/model-ordering.md | 2 -- docs-site/src/content/docs/fr/guides/providers.md | 2 -- docs-site/src/content/docs/fr/reference/adapters.md | 2 -- .../src/content/docs/fr/reference/configuration/routing.md | 2 -- docs-site/src/content/docs/getting-started/quickstart.md | 2 -- docs-site/src/content/docs/guides/codex-app-models.md | 2 -- docs-site/src/content/docs/guides/model-ordering.md | 2 -- docs-site/src/content/docs/guides/providers.md | 5 ----- docs-site/src/content/docs/ja/getting-started/quickstart.md | 2 -- docs-site/src/content/docs/ja/guides/codex-app-models.md | 2 -- docs-site/src/content/docs/ja/guides/model-ordering.md | 2 -- docs-site/src/content/docs/ja/guides/providers.md | 2 -- docs-site/src/content/docs/ja/reference/adapters.md | 2 -- .../src/content/docs/ja/reference/configuration/routing.md | 2 -- docs-site/src/content/docs/ko/getting-started/quickstart.md | 2 -- docs-site/src/content/docs/ko/guides/codex-app-models.md | 2 -- docs-site/src/content/docs/ko/guides/model-ordering.md | 2 -- docs-site/src/content/docs/ko/guides/providers.md | 2 -- docs-site/src/content/docs/ko/reference/adapters.md | 2 -- .../src/content/docs/ko/reference/configuration/routing.md | 2 -- docs-site/src/content/docs/reference/adapters.md | 2 -- .../src/content/docs/reference/configuration/routing.md | 2 -- docs-site/src/content/docs/ru/getting-started/quickstart.md | 2 -- docs-site/src/content/docs/ru/guides/codex-app-models.md | 2 -- docs-site/src/content/docs/ru/guides/model-ordering.md | 2 -- docs-site/src/content/docs/ru/guides/providers.md | 2 -- docs-site/src/content/docs/ru/reference/adapters.md | 2 -- .../src/content/docs/ru/reference/configuration/routing.md | 2 -- docs-site/src/content/docs/tr/getting-started/quickstart.md | 2 -- docs-site/src/content/docs/tr/guides/codex-app-models.md | 2 -- docs-site/src/content/docs/tr/guides/model-ordering.md | 2 -- docs-site/src/content/docs/tr/guides/providers.md | 2 -- docs-site/src/content/docs/tr/reference/adapters.md | 2 -- .../src/content/docs/tr/reference/configuration/routing.md | 2 -- .../src/content/docs/zh-cn/getting-started/quickstart.md | 2 -- docs-site/src/content/docs/zh-cn/guides/codex-app-models.md | 2 -- docs-site/src/content/docs/zh-cn/guides/model-ordering.md | 2 -- docs-site/src/content/docs/zh-cn/guides/providers.md | 2 -- docs-site/src/content/docs/zh-cn/reference/adapters.md | 2 -- .../content/docs/zh-cn/reference/configuration/routing.md | 2 -- .../src/content/docs/zh-tw/getting-started/quickstart.md | 2 -- docs-site/src/content/docs/zh-tw/guides/codex-app-models.md | 2 -- docs-site/src/content/docs/zh-tw/guides/model-ordering.md | 2 -- docs-site/src/content/docs/zh-tw/guides/providers.md | 2 -- docs-site/src/content/docs/zh-tw/reference/adapters.md | 2 -- .../content/docs/zh-tw/reference/configuration/routing.md | 2 -- tests/ci-workflows/docs-gpt61-terra.test.ts | 6 ++---- 49 files changed, 2 insertions(+), 103 deletions(-) diff --git a/docs-site/src/content/docs/fr/getting-started/quickstart.md b/docs-site/src/content/docs/fr/getting-started/quickstart.md index 4036591dbb9..fa96c775b52 100644 --- a/docs-site/src/content/docs/fr/getting-started/quickstart.md +++ b/docs-site/src/content/docs/fr/getting-started/quickstart.md @@ -5,8 +5,6 @@ description: Configurez votre premier fournisseur et acheminez OpenAI Codex via Ce guide part d’une installation neuve et vous conduit jusqu’à l’exécution de Codex sur un modèle autre qu’OpenAI. -Vous pouvez aussi choisir `gpt-6.1-terra` aux côtés de `gpt-5.6-terra`, sans modifier le modèle par défaut ni la liste des sous-agents. Voir les [limites, le raisonnement et le mode Fast de GPT-6.1 Terra](/fr/reference/configuration/providers/#gpt-61-terra). - ## 1. Exécutez l'assistant de configuration ```bash diff --git a/docs-site/src/content/docs/fr/guides/codex-app-models.md b/docs-site/src/content/docs/fr/guides/codex-app-models.md index 23c959d0288..8e420079af1 100644 --- a/docs-site/src/content/docs/fr/guides/codex-app-models.md +++ b/docs-site/src/content/docs/fr/guides/codex-app-models.md @@ -89,8 +89,6 @@ cp ~/.opencodex/config.json.pre-openai-tiers-v2.bak ~/.opencodex/config.json Les anciennes configurations v1 à trois fournisseurs migrent automatiquement vers l'unique ligne tenant compte de l'option choisie. -Vous pouvez aussi choisir `gpt-6.1-terra` aux côtés de `gpt-5.6-terra`, sans modifier le modèle par défaut ni la liste des sous-agents. Voir les [limites, le raisonnement et le mode Fast de GPT-6.1 Terra](/fr/reference/configuration/providers/#gpt-61-terra). - ## Limitation de la liste d'autorisation distante de Desktop Si `codex debug models` et `model/list` du serveur d'application contiennent un modèle routé que Desktop diff --git a/docs-site/src/content/docs/fr/guides/model-ordering.md b/docs-site/src/content/docs/fr/guides/model-ordering.md index 52fa03cf3d1..fab755afdf4 100644 --- a/docs-site/src/content/docs/fr/guides/model-ordering.md +++ b/docs-site/src/content/docs/fr/guides/model-ordering.md @@ -7,8 +7,6 @@ Le sélecteur de modèles Codex ne conserve ni l’ordre de déclaration des fou configuration opencodex. L’ordre final découle des priorités du catalogue ; les modèles routés qui partagent la même priorité sont classés selon un ordre alphabétique déterministe. -Vous pouvez aussi choisir `gpt-6.1-terra` aux côtés de `gpt-5.6-terra`, sans modifier le modèle par défaut ni la liste des sous-agents. Voir les [limites, le raisonnement et le mode Fast de GPT-6.1 Terra](/fr/reference/configuration/providers/#gpt-61-terra). - ## La règle Codex s'applique Le gestionnaire de modèles de Codex trie les entrées de catalogue visibles dans le sélecteur par `priority`, dans l’ordre croissant. Il diff --git a/docs-site/src/content/docs/fr/guides/providers.md b/docs-site/src/content/docs/fr/guides/providers.md index dc1cab71246..91cc03aaabe 100644 --- a/docs-site/src/content/docs/fr/guides/providers.md +++ b/docs-site/src/content/docs/fr/guides/providers.md @@ -7,8 +7,6 @@ Un **fournisseur** associe un point de terminaison LLM en amont à la façon de une URL de base, un mode d'authentification et, facultativement, une liste de modèles. Les fournisseurs sont définis sous `providers` dans `~/.opencodex/config.json`. -Vous pouvez aussi choisir `gpt-6.1-terra` aux côtés de `gpt-5.6-terra`, sans modifier le modèle par défaut ni la liste des sous-agents. Voir les [limites, le raisonnement et le mode Fast de GPT-6.1 Terra](/fr/reference/configuration/providers/#gpt-61-terra). - ## Modes de compte OpenAI | Identifiant du fournisseur | Utilisation | Règle relative aux identifiants et aux comptes | diff --git a/docs-site/src/content/docs/fr/reference/adapters.md b/docs-site/src/content/docs/fr/reference/adapters.md index 8f22a99a5b8..d45e12b48a1 100644 --- a/docs-site/src/content/docs/fr/reference/adapters.md +++ b/docs-site/src/content/docs/fr/reference/adapters.md @@ -20,8 +20,6 @@ interface ProviderAdapter { `incoming` est un `IncomingMeta` obligatoire qui transporte notamment les en-têtes, le signal d’abandon et le budget de traduction. Le contexte facultatif de `fetchResponse` est un `AdapterFetchContext`. Les méthodes d’analyse reçoivent elles aussi un `TranslatorBudget` obligatoire afin de borner les données traduites. -Vous pouvez aussi choisir `gpt-6.1-terra` aux côtés de `gpt-5.6-terra`, sans modifier le modèle par défaut ni la liste des sous-agents. Voir les [limites, le raisonnement et le mode Fast de GPT-6.1 Terra](/fr/reference/configuration/providers/#gpt-61-terra). - ## `openai-chat` **Cibles :** l’API **Chat Completions** d’OpenAI (`POST {baseUrl}/chat/completions` ; un suffixe `/chat/completions` ou `/` est d’abord retiré de `baseUrl`) et tous les fournisseurs compatibles — xAI, Kimi, DeepSeek, GLM, Groq, OpenRouter, Ollama (local), entre autres. diff --git a/docs-site/src/content/docs/fr/reference/configuration/routing.md b/docs-site/src/content/docs/fr/reference/configuration/routing.md index 6179222454f..3b0fc9e6cf9 100644 --- a/docs-site/src/content/docs/fr/reference/configuration/routing.md +++ b/docs-site/src/content/docs/fr/reference/configuration/routing.md @@ -5,8 +5,6 @@ description: Sélection du fournisseur par défaut, ordre de résolution des mod Le routage transforme l’identifiant de modèle envoyé par un client en un fournisseur concret et un modèle en amont. -Vous pouvez aussi choisir `gpt-6.1-terra` aux côtés de `gpt-5.6-terra`, sans modifier le modèle par défaut ni la liste des sous-agents. Voir les [limites, le raisonnement et le mode Fast de GPT-6.1 Terra](/fr/reference/configuration/providers/#gpt-61-terra). - ## Champs de routage de premier niveau | Champ | Type | Valeur par défaut | Signification | diff --git a/docs-site/src/content/docs/getting-started/quickstart.md b/docs-site/src/content/docs/getting-started/quickstart.md index 4dbe7a150d7..ed39e7005e5 100644 --- a/docs-site/src/content/docs/getting-started/quickstart.md +++ b/docs-site/src/content/docs/getting-started/quickstart.md @@ -5,8 +5,6 @@ description: Configure your first provider and route OpenAI Codex through openco This guide takes you from a fresh install to running Codex against a non-OpenAI model. -You can also select `gpt-6.1-terra` alongside `gpt-5.6-terra`; it does not replace any default or sub-agent roster entry. See [GPT-6.1 Terra limits, reasoning and Fast](/reference/configuration/providers/#gpt-61-terra). - ## Standalone binary (no npm) You can also use a release archive containing the `ocx` binary and Bun runtime without npm. diff --git a/docs-site/src/content/docs/guides/codex-app-models.md b/docs-site/src/content/docs/guides/codex-app-models.md index b7dac9a0a70..4da93918113 100644 --- a/docs-site/src/content/docs/guides/codex-app-models.md +++ b/docs-site/src/content/docs/guides/codex-app-models.md @@ -118,8 +118,6 @@ cp ~/.opencodex/config.json.pre-openai-tiers-v2.bak ~/.opencodex/config.json Earlier v1 three-provider configurations migrate automatically into the single option-aware row. -You can also select `gpt-6.1-terra` alongside `gpt-5.6-terra`; it does not replace any default or sub-agent roster entry. See [GPT-6.1 Terra limits, reasoning and Fast](/reference/configuration/providers/#gpt-61-terra). - ## Desktop remote-allowlist limitation If `codex debug models` and app-server `model/list` contain a routed model but Desktop does not show diff --git a/docs-site/src/content/docs/guides/model-ordering.md b/docs-site/src/content/docs/guides/model-ordering.md index 49a33e52732..b3ca4772592 100644 --- a/docs-site/src/content/docs/guides/model-ordering.md +++ b/docs-site/src/content/docs/guides/model-ordering.md @@ -7,8 +7,6 @@ The Codex model picker does not preserve the order of provider declarations or m opencodex configuration. Its final order comes from catalog priorities, with a deterministic alphabetical order for routed models that share the same priority. -You can also select `gpt-6.1-terra` alongside `gpt-5.6-terra`; it does not replace any default or sub-agent roster entry. See [GPT-6.1 Terra limits, reasoning and Fast](/reference/configuration/providers/#gpt-61-terra). - ## The rule Codex applies Codex's models-manager sorts picker-visible catalog entries by `priority` in ascending order. It diff --git a/docs-site/src/content/docs/guides/providers.md b/docs-site/src/content/docs/guides/providers.md index 806964cda7d..f2d5f813a86 100644 --- a/docs-site/src/content/docs/guides/providers.md +++ b/docs-site/src/content/docs/guides/providers.md @@ -13,8 +13,6 @@ These links preserve the preset's referral parameters. Sponsor information is sh the configured provider name, adapter and endpoint match the preset; it never changes routing, account selection or defaults. -You can also select `gpt-6.1-terra` alongside `gpt-5.6-terra`; it does not replace any default or sub-agent roster entry. See [GPT-6.1 Terra limits, reasoning and Fast](/reference/configuration/providers/#gpt-61-terra). - ## OpenAI account modes | Provider id | Use | Credential/account rule | @@ -847,8 +845,6 @@ The preset uses [Chat Completions](https://tokenlab.sh/docs/en/quickstart) and d `GET /v1/models?category=chat`, keeping only entries that declare `tool-use` capability. Image, video, audio, embedding and decision models are excluded from this chat preset. - - Each model then uses the request format TokenLab declares for it (`tokenlab.accepted_request_formats` on `GET /v1/models/{model}`): @@ -879,7 +875,6 @@ environment. The preset uses Chat Completions. The following existing models were verified with chat, streaming and tool calls: `glm-5.3-flash` (the default), `claude-sonnet-5-5`, `gpt-6.1-sol` and `deepseek-v4-flash`. `gpt-6.1-terra` is a preemptive seed mirroring Sol; it has not been inference-verified here. - You can add other Chat-compatible Modelflare models as custom models. Image and video models use separate Modelflare endpoints and do not work through this Chat preset. An ordinary Modelflare key is bound to one routing group and diff --git a/docs-site/src/content/docs/ja/getting-started/quickstart.md b/docs-site/src/content/docs/ja/getting-started/quickstart.md index 62759e3710a..216e3891dac 100644 --- a/docs-site/src/content/docs/ja/getting-started/quickstart.md +++ b/docs-site/src/content/docs/ja/getting-started/quickstart.md @@ -5,8 +5,6 @@ description: 最初のプロバイダーを構成し、3 つのコマンドで O このガイドでは、新規インストールから非 OpenAI モデルに対して Codex を実行するまでを説明します。 -`gpt-5.6-terra` に加えて `gpt-6.1-terra` も選択できます。既定モデルやサブエージェントのモデル一覧は変わりません。[GPT-6.1 Terra の上限・推論・Fast](/ja/reference/configuration/providers/#gpt-61-terra)を参照してください。 - ## スタンドアロンバイナリ（npm 不要） npm を使わず、Bun ランタイムを含むリリースアーカイブの `ocx` バイナリも利用できます。 diff --git a/docs-site/src/content/docs/ja/guides/codex-app-models.md b/docs-site/src/content/docs/ja/guides/codex-app-models.md index 28d6c1c946b..ef99c820f3a 100644 --- a/docs-site/src/content/docs/ja/guides/codex-app-models.md +++ b/docs-site/src/content/docs/ja/guides/codex-app-models.md @@ -30,8 +30,6 @@ cp ~/.opencodex/config.json.pre-openai-tiers-v2.bak ~/.opencodex/config.json 以前の v1 の 3 プロバイダー設定は、単一のオプション対応行に自動的に移行されます。 -`gpt-5.6-terra` に加えて `gpt-6.1-terra` も選択できます。既定モデルやサブエージェントのモデル一覧は変わりません。[GPT-6.1 Terra の上限・推論・Fast](/ja/reference/configuration/providers/#gpt-61-terra)を参照してください。 - ## 統合パス `ocx init`、`ocx start`、および `ocx sync` は、共有 Codex 設定とカタログをプロキシに接続します。設定の挿入、カタログの同期、シム、WebSocket フォールバック、および復元の仕組みについては、[Codexの統合](/guides/codex-integration/) を参照してください。 diff --git a/docs-site/src/content/docs/ja/guides/model-ordering.md b/docs-site/src/content/docs/ja/guides/model-ordering.md index af4c32c0057..74febb1e782 100644 --- a/docs-site/src/content/docs/ja/guides/model-ordering.md +++ b/docs-site/src/content/docs/ja/guides/model-ordering.md @@ -7,8 +7,6 @@ Codex モデルピッカーは opencodex 設定に書かれたプロバイダー 最終順序はカタログ priority で決まり、同じ priority を持つルーティングモデルには決定論的 アルファベット順ソートが適用されます。 -`gpt-5.6-terra` に加えて `gpt-6.1-terra` も選択できます。既定モデルやサブエージェントのモデル一覧は変わりません。[GPT-6.1 Terra の上限・推論・Fast](/ja/reference/configuration/providers/#gpt-61-terra)を参照してください。 - ## Codex が適用するルール Codex の models-manager はピッカーに表示されるカタログ項目を `priority` 昇順でソートします。 diff --git a/docs-site/src/content/docs/ja/guides/providers.md b/docs-site/src/content/docs/ja/guides/providers.md index ab15df10ce7..2c5920a8c38 100644 --- a/docs-site/src/content/docs/ja/guides/providers.md +++ b/docs-site/src/content/docs/ja/guides/providers.md @@ -6,8 +6,6 @@ description: opencodex が LLM プロバイダーを認証し通信するすべ **プロバイダー**は一つの上流 LLM エンドポイントとそこへの到達方法を合わせたものです: アダプター、ベース URL、認証 モード、そしてオプションのモデル一覧で構成されます。プロバイダーは `~/.opencodex/config.json` の `providers` の下にあります。 -`gpt-5.6-terra` に加えて `gpt-6.1-terra` も選択できます。既定モデルやサブエージェントのモデル一覧は変わりません。[GPT-6.1 Terra の上限・推論・Fast](/ja/reference/configuration/providers/#gpt-61-terra)を参照してください。 - ## OpenAI アカウントモード | プロバイダー ID | 用途 | 認証情報/アカウットルール | diff --git a/docs-site/src/content/docs/ja/reference/adapters.md b/docs-site/src/content/docs/ja/reference/adapters.md index b2a2585812b..b817283250d 100644 --- a/docs-site/src/content/docs/ja/reference/adapters.md +++ b/docs-site/src/content/docs/ja/reference/adapters.md @@ -19,8 +19,6 @@ interface ProviderAdapter { `buildRequest` は `OcxParsedRequest` を上流の HTTP リクエストに落とし、`parseStream` / `parseResponse` はプロバイダーのレスポンスを内部 `AdapterEvent` に持ち上げます。`fetchResponse` があると、アダプターがリトライとタイムアウトを直接担います。`runTurn` は 1 回の HTTP fetch とその後のレスポンスストリームでは表現できない伝送方式をサポートします。その後 [`bridge.ts`](/ja/reference/architecture/#ブリッジ) がイベントを Responses SSE に変えます。 -`gpt-5.6-terra` に加えて `gpt-6.1-terra` も選択できます。既定モデルやサブエージェントのモデル一覧は変わりません。[GPT-6.1 Terra の上限・推論・Fast](/ja/reference/configuration/providers/#gpt-61-terra)を参照してください。 - ## `openai-chat` **対象:** OpenAI **Chat Completions**（`POST {baseUrl}/chat/completions`）および互換プロバイダー diff --git a/docs-site/src/content/docs/ja/reference/configuration/routing.md b/docs-site/src/content/docs/ja/reference/configuration/routing.md index 5111850779c..99ff0bfb3b3 100644 --- a/docs-site/src/content/docs/ja/reference/configuration/routing.md +++ b/docs-site/src/content/docs/ja/reference/configuration/routing.md @@ -5,8 +5,6 @@ description: デフォルトのプロバイダーの選択、モデルの解決 ルーティングは、クライアントから送信されたモデル ID を 1 つの具体的なプロバイダーと上流モデルに変換します。 -`gpt-5.6-terra` に加えて `gpt-6.1-terra` も選択できます。既定モデルやサブエージェントのモデル一覧は変わりません。[GPT-6.1 Terra の上限・推論・Fast](/ja/reference/configuration/providers/#gpt-61-terra)を参照してください。 - ## トップレベルのルーティングフィールド |フィールド |タイプ |デフォルト |意味 | diff --git a/docs-site/src/content/docs/ko/getting-started/quickstart.md b/docs-site/src/content/docs/ko/getting-started/quickstart.md index 420b59217ea..77cc5a35d1e 100644 --- a/docs-site/src/content/docs/ko/getting-started/quickstart.md +++ b/docs-site/src/content/docs/ko/getting-started/quickstart.md @@ -5,8 +5,6 @@ description: 첫 프로바이더를 설정하고 명령어 세 개로 OpenAI Cod 이 가이드는 새로 설치한 상태에서 OpenAI가 아닌 모델로 Codex를 실행하기까지의 과정을 안내합니다. -`gpt-5.6-terra`와 함께 `gpt-6.1-terra`도 선택할 수 있습니다. 기본 모델이나 하위 에이전트 모델 목록은 바뀌지 않습니다. [GPT-6.1 Terra 한도·추론·Fast](/ko/reference/configuration/providers/#gpt-61-terra)를 참고하세요. - ## 독립 실행형 바이너리(npm 없음) npm 없이 Bun 런타임이 포함된 릴리스 아카이브의 `ocx` 바이너리를 사용할 수도 있습니다. diff --git a/docs-site/src/content/docs/ko/guides/codex-app-models.md b/docs-site/src/content/docs/ko/guides/codex-app-models.md index 1f4de5b15d9..40c716687da 100644 --- a/docs-site/src/content/docs/ko/guides/codex-app-models.md +++ b/docs-site/src/content/docs/ko/guides/codex-app-models.md @@ -74,8 +74,6 @@ cp ~/.opencodex/config.json.pre-openai-tiers-v2.bak ~/.opencodex/config.json 이전 v1의 3-provider 설정은 자동으로 옵션을 인식하는 단일 행으로 마이그레이션됩니다. -`gpt-5.6-terra`와 함께 `gpt-6.1-terra`도 선택할 수 있습니다. 기본 모델이나 하위 에이전트 모델 목록은 바뀌지 않습니다. [GPT-6.1 Terra 한도·추론·Fast](/ko/reference/configuration/providers/#gpt-61-terra)를 참고하세요. - ## 통합 경로 `ocx init`, `ocx start`, `ocx sync`는 공유 Codex 설정과 카탈로그를 프록시에 연결합니다. 설정 주입, diff --git a/docs-site/src/content/docs/ko/guides/model-ordering.md b/docs-site/src/content/docs/ko/guides/model-ordering.md index 47ad18bcf4c..e921bfdfbcd 100644 --- a/docs-site/src/content/docs/ko/guides/model-ordering.md +++ b/docs-site/src/content/docs/ko/guides/model-ordering.md @@ -7,8 +7,6 @@ Codex 모델 선택기는 opencodex 설정에 적힌 프로바이더 선언 순 않습니다. 최종 순서는 카탈로그 priority로 정해지며, 같은 priority를 가진 라우팅 모델에는 결정적인 알파벳순 정렬이 적용됩니다. -`gpt-5.6-terra`와 함께 `gpt-6.1-terra`도 선택할 수 있습니다. 기본 모델이나 하위 에이전트 모델 목록은 바뀌지 않습니다. [GPT-6.1 Terra 한도·추론·Fast](/ko/reference/configuration/providers/#gpt-61-terra)를 참고하세요. - ## Codex가 적용하는 규칙 Codex의 models-manager는 선택기에 표시되는 카탈로그 항목을 `priority` 오름차순으로 정렬합니다. diff --git a/docs-site/src/content/docs/ko/guides/providers.md b/docs-site/src/content/docs/ko/guides/providers.md index 14644b5d919..e7fe1c3c387 100644 --- a/docs-site/src/content/docs/ko/guides/providers.md +++ b/docs-site/src/content/docs/ko/guides/providers.md @@ -6,8 +6,6 @@ description: opencodex가 LLM 프로바이더를 인증하고 통신하는 모 **프로바이더**는 하나의 업스트림 LLM 엔드포인트와 거기에 도달하는 방법을 합친 것입니다: 어댑터, 베이스 URL, 인증 모드, 그리고 선택적인 모델 목록으로 구성됩니다. 프로바이더는 `~/.opencodex/config.json`의 `providers` 아래에 위치합니다. -`gpt-5.6-terra`와 함께 `gpt-6.1-terra`도 선택할 수 있습니다. 기본 모델이나 하위 에이전트 모델 목록은 바뀌지 않습니다. [GPT-6.1 Terra 한도·추론·Fast](/ko/reference/configuration/providers/#gpt-61-terra)를 참고하세요. - ## OpenAI 계정 모드 | 프로바이더 id | 용도 | 자격증명/계정 규칙 | diff --git a/docs-site/src/content/docs/ko/reference/adapters.md b/docs-site/src/content/docs/ko/reference/adapters.md index b9acbf7f5ad..546a0dea6eb 100644 --- a/docs-site/src/content/docs/ko/reference/adapters.md +++ b/docs-site/src/content/docs/ko/reference/adapters.md @@ -23,8 +23,6 @@ interface ProviderAdapter { 스트림으로 표현할 수 없는 전송 방식을 지원합니다. 이후 [`bridge.ts`](/ko/reference/architecture/#브리지)가 이벤트를 Responses SSE로 바꿉니다. -`gpt-5.6-terra`와 함께 `gpt-6.1-terra`도 선택할 수 있습니다. 기본 모델이나 하위 에이전트 모델 목록은 바뀌지 않습니다. [GPT-6.1 Terra 한도·추론·Fast](/ko/reference/configuration/providers/#gpt-61-terra)를 참고하세요. - ## `openai-chat` **대상:** OpenAI **Chat Completions**(`POST {baseUrl}/chat/completions`)와 모든 호환 프로바이더 diff --git a/docs-site/src/content/docs/ko/reference/configuration/routing.md b/docs-site/src/content/docs/ko/reference/configuration/routing.md index ffdd4a573c8..d19dce2f092 100644 --- a/docs-site/src/content/docs/ko/reference/configuration/routing.md +++ b/docs-site/src/content/docs/ko/reference/configuration/routing.md @@ -5,8 +5,6 @@ description: 기본 provider 선택, model 해석 순서, combo 별칭, 대상 라우팅은 클라이언트가 보낸 model id를 하나의 실제 provider와 upstream model로 바꿉니다. -`gpt-5.6-terra`와 함께 `gpt-6.1-terra`도 선택할 수 있습니다. 기본 모델이나 하위 에이전트 모델 목록은 바뀌지 않습니다. [GPT-6.1 Terra 한도·추론·Fast](/ko/reference/configuration/providers/#gpt-61-terra)를 참고하세요. - ## 최상위 라우팅 필드 | Field | Type | Default | Meaning | diff --git a/docs-site/src/content/docs/reference/adapters.md b/docs-site/src/content/docs/reference/adapters.md index 5a28844d42e..ef88ecb76b5 100644 --- a/docs-site/src/content/docs/reference/adapters.md +++ b/docs-site/src/content/docs/reference/adapters.md @@ -23,8 +23,6 @@ adapter own retries/timeouts, while `runTurn` supports transports that cannot be HTTP fetch followed by one response stream. [`bridge.ts`](/reference/architecture/#the-bridge) then turns the events into Responses SSE. -You can also select `gpt-6.1-terra` alongside `gpt-5.6-terra`; it does not replace any default or sub-agent roster entry. See [GPT-6.1 Terra limits, reasoning and Fast](/reference/configuration/providers/#gpt-61-terra). - ## External task input on translated Responses routes Codex task coordination can deliver input as `function_call_output` with nonblank diff --git a/docs-site/src/content/docs/reference/configuration/routing.md b/docs-site/src/content/docs/reference/configuration/routing.md index 4efaa61ef82..e518b009789 100644 --- a/docs-site/src/content/docs/reference/configuration/routing.md +++ b/docs-site/src/content/docs/reference/configuration/routing.md @@ -5,8 +5,6 @@ description: Default-provider selection, model resolution order, combo aliases, Routing turns the model id sent by a client into one concrete provider and upstream model. -You can also select `gpt-6.1-terra` alongside `gpt-5.6-terra`; it does not replace any default or sub-agent roster entry. See [GPT-6.1 Terra limits, reasoning and Fast](/reference/configuration/providers/#gpt-61-terra). - ## Top-level routing fields | Field | Type | Default | Meaning | diff --git a/docs-site/src/content/docs/ru/getting-started/quickstart.md b/docs-site/src/content/docs/ru/getting-started/quickstart.md index cfe87c16c28..99d6cdb2a1b 100644 --- a/docs-site/src/content/docs/ru/getting-started/quickstart.md +++ b/docs-site/src/content/docs/ru/getting-started/quickstart.md @@ -5,8 +5,6 @@ description: Настройте первого провайдера и напр Это руководство проводит от чистой установки до запуска Codex с моделью не от OpenAI. -Наряду с `gpt-5.6-terra` можно выбрать `gpt-6.1-terra`. Модель по умолчанию и список моделей подагентов не меняются. См. [лимиты, уровни рассуждения и Fast для GPT-6.1 Terra](/ru/reference/configuration/providers/#gpt-61-terra). - ## Автономный бинарный файл (без npm) Можно также использовать архив с бинарным файлом `ocx` и рантаймом Bun без npm. diff --git a/docs-site/src/content/docs/ru/guides/codex-app-models.md b/docs-site/src/content/docs/ru/guides/codex-app-models.md index bf8eb05339c..04a4381f8ee 100644 --- a/docs-site/src/content/docs/ru/guides/codex-app-models.md +++ b/docs-site/src/content/docs/ru/guides/codex-app-models.md @@ -54,8 +54,6 @@ cp ~/.opencodex/config.json.pre-openai-tiers-v2.bak ~/.opencodex/config.json Более ранние трёхпровайдерные конфигурации v1 автоматически мигрируют в одну строку с переключаемым режимом. -Наряду с `gpt-5.6-terra` можно выбрать `gpt-6.1-terra`. Модель по умолчанию и список моделей подагентов не меняются. См. [лимиты, уровни рассуждения и Fast для GPT-6.1 Terra](/ru/reference/configuration/providers/#gpt-61-terra). - ## Путь интеграции `ocx init`, `ocx start` и `ocx sync` подключают общий конфиг и каталог Codex к прокси; подробности diff --git a/docs-site/src/content/docs/ru/guides/model-ordering.md b/docs-site/src/content/docs/ru/guides/model-ordering.md index 846e2b6d836..5ff04e48920 100644 --- a/docs-site/src/content/docs/ru/guides/model-ordering.md +++ b/docs-site/src/content/docs/ru/guides/model-ordering.md @@ -7,8 +7,6 @@ description: Как opencodex определяет порядок моделей конфигурации opencodex. Итоговый порядок определяется приоритетами каталога, а маршрутизируемые модели с одинаковым приоритетом упорядочиваются детерминированно по алфавиту. -Наряду с `gpt-5.6-terra` можно выбрать `gpt-6.1-terra`. Модель по умолчанию и список моделей подагентов не меняются. См. [лимиты, уровни рассуждения и Fast для GPT-6.1 Terra](/ru/reference/configuration/providers/#gpt-61-terra). - ## Правило, которое применяет Codex Менеджер моделей Codex сортирует видимые в селекторе записи каталога по `priority` по diff --git a/docs-site/src/content/docs/ru/guides/providers.md b/docs-site/src/content/docs/ru/guides/providers.md index d47eba8456f..49ff52970f9 100644 --- a/docs-site/src/content/docs/ru/guides/providers.md +++ b/docs-site/src/content/docs/ru/guides/providers.md @@ -7,8 +7,6 @@ description: Все способы, которыми opencodex аутентиф базовый URL, режим аутентификации и необязательный список моделей. Провайдеры находятся в `~/.opencodex/config.json` в секции `providers`. -Наряду с `gpt-5.6-terra` можно выбрать `gpt-6.1-terra`. Модель по умолчанию и список моделей подагентов не меняются. См. [лимиты, уровни рассуждения и Fast для GPT-6.1 Terra](/ru/reference/configuration/providers/#gpt-61-terra). - ## Режимы аккаунтов OpenAI | Id провайдера | Назначение | Правило учётных данных/аккаунтов | diff --git a/docs-site/src/content/docs/ru/reference/adapters.md b/docs-site/src/content/docs/ru/reference/adapters.md index d1800b7861b..3bad254262f 100644 --- a/docs-site/src/content/docs/ru/reference/adapters.md +++ b/docs-site/src/content/docs/ru/reference/adapters.md @@ -25,8 +25,6 @@ interface ProviderAdapter { с последующим одним потоком ответа. Затем [`bridge.ts`](/ru/reference/architecture/#мост) превращает события в Responses SSE. -Наряду с `gpt-5.6-terra` можно выбрать `gpt-6.1-terra`. Модель по умолчанию и список моделей подагентов не меняются. См. [лимиты, уровни рассуждения и Fast для GPT-6.1 Terra](/ru/reference/configuration/providers/#gpt-61-terra). - ## `openai-chat` **Назначение:** OpenAI **Chat Completions** (`POST {baseUrl}/chat/completions`) и все совместимые diff --git a/docs-site/src/content/docs/ru/reference/configuration/routing.md b/docs-site/src/content/docs/ru/reference/configuration/routing.md index c4f83cdcb0d..b117669318f 100644 --- a/docs-site/src/content/docs/ru/reference/configuration/routing.md +++ b/docs-site/src/content/docs/ru/reference/configuration/routing.md @@ -6,8 +6,6 @@ description: Выбор провайдера по умолчанию, поряд Маршрутизация преобразует id модели, отправленный клиентом, в конкретного провайдера и модель upstream. -Наряду с `gpt-5.6-terra` можно выбрать `gpt-6.1-terra`. Модель по умолчанию и список моделей подагентов не меняются. См. [лимиты, уровни рассуждения и Fast для GPT-6.1 Terra](/ru/reference/configuration/providers/#gpt-61-terra). - ## Поля маршрутизации верхнего уровня | Поле | Тип | По умолчанию | Значение | diff --git a/docs-site/src/content/docs/tr/getting-started/quickstart.md b/docs-site/src/content/docs/tr/getting-started/quickstart.md index e7b9d98d16b..27e9f1d95a7 100644 --- a/docs-site/src/content/docs/tr/getting-started/quickstart.md +++ b/docs-site/src/content/docs/tr/getting-started/quickstart.md @@ -6,8 +6,6 @@ description: İlk sağlayıcınızı yapılandırın ve OpenAI Codex'i üç komu Bu kılavuz, yeni bir kurulumdan başlayarak Codex'i OpenAI harici bir model üzerinde çalıştırmanızı sağlar. -`gpt-5.6-terra` yanında `gpt-6.1-terra` da seçilebilir. Varsayılan model ve alt ajan model listesi değişmez. [GPT-6.1 Terra sınırları, akıl yürütme ve Fast](/tr/reference/configuration/providers/#gpt-61-terra) bölümüne bakın. - ## 1. Kurulum sihirbazını çalıştırın ```bash diff --git a/docs-site/src/content/docs/tr/guides/codex-app-models.md b/docs-site/src/content/docs/tr/guides/codex-app-models.md index 40625b39ed0..6cf1ba16587 100644 --- a/docs-site/src/content/docs/tr/guides/codex-app-models.md +++ b/docs-site/src/content/docs/tr/guides/codex-app-models.md @@ -97,8 +97,6 @@ cp ~/.opencodex/config.json.pre-openai-tiers-v2.bak ~/.opencodex/config.json Daha önceki v1 üç sağlayıcılı yapılandırmalar otomatik olarak tek seçenek duyarlı satıra geçer. -`gpt-5.6-terra` yanında `gpt-6.1-terra` da seçilebilir. Varsayılan model ve alt ajan model listesi değişmez. [GPT-6.1 Terra sınırları, akıl yürütme ve Fast](/tr/reference/configuration/providers/#gpt-61-terra) bölümüne bakın. - ## Desktop uzak izin listesi sınırlaması `codex debug models` ve uygulama sunucusu `model/list` yönlendirilen bir modeli diff --git a/docs-site/src/content/docs/tr/guides/model-ordering.md b/docs-site/src/content/docs/tr/guides/model-ordering.md index 6a0bd9b96f4..ea42630154c 100644 --- a/docs-site/src/content/docs/tr/guides/model-ordering.md +++ b/docs-site/src/content/docs/tr/guides/model-ordering.md @@ -8,8 +8,6 @@ veya model dizilerinin sırasını korumaz. Nihai sırası, aynı önceliği pay yönlendirilmiş modeller için belirleyici bir alfabetik sırayla birlikte katalog önceliklerinden gelir. -`gpt-5.6-terra` yanında `gpt-6.1-terra` da seçilebilir. Varsayılan model ve alt ajan model listesi değişmez. [GPT-6.1 Terra sınırları, akıl yürütme ve Fast](/tr/reference/configuration/providers/#gpt-61-terra) bölümüne bakın. - ## Codex'in uyguladığı kural Codex'in models-manager'ı, seçicide görünen katalog girdilerini artan sırada diff --git a/docs-site/src/content/docs/tr/guides/providers.md b/docs-site/src/content/docs/tr/guides/providers.md index e5692726ab7..58f0f8ee2f1 100644 --- a/docs-site/src/content/docs/tr/guides/providers.md +++ b/docs-site/src/content/docs/tr/guides/providers.md @@ -8,8 +8,6 @@ bir adaptör, bir temel URL, bir kimlik doğrulama modu ve isteğe bağlı bir m listesi. Sağlayıcılar `~/.opencodex/config.json` içinde `providers` altında bulunur. -`gpt-5.6-terra` yanında `gpt-6.1-terra` da seçilebilir. Varsayılan model ve alt ajan model listesi değişmez. [GPT-6.1 Terra sınırları, akıl yürütme ve Fast](/tr/reference/configuration/providers/#gpt-61-terra) bölümüne bakın. - ## OpenAI hesap modları | Sağlayıcı kimliği | Kullanım | Kimlik bilgisi/hesap kuralı | diff --git a/docs-site/src/content/docs/tr/reference/adapters.md b/docs-site/src/content/docs/tr/reference/adapters.md index 7da928557c9..2a31a0cd7f0 100644 --- a/docs-site/src/content/docs/tr/reference/adapters.md +++ b/docs-site/src/content/docs/tr/reference/adapters.md @@ -26,8 +26,6 @@ getirmesini takip eden tek bir yanıt akışı olarak temsil edilemeyen aktarım destekler. [`bridge.ts`](/tr/reference/architecture/#köprü-bridge) daha sonra olayları Responses SSE'ye dönüştürür. -`gpt-5.6-terra` yanında `gpt-6.1-terra` da seçilebilir. Varsayılan model ve alt ajan model listesi değişmez. [GPT-6.1 Terra sınırları, akıl yürütme ve Fast](/tr/reference/configuration/providers/#gpt-61-terra) bölümüne bakın. - ## `openai-chat` **Hedefler:** OpenAI **Chat Completions** (`POST {baseUrl}/chat/completions`; diff --git a/docs-site/src/content/docs/tr/reference/configuration/routing.md b/docs-site/src/content/docs/tr/reference/configuration/routing.md index a282b9ca800..3a89ef094e4 100644 --- a/docs-site/src/content/docs/tr/reference/configuration/routing.md +++ b/docs-site/src/content/docs/tr/reference/configuration/routing.md @@ -6,8 +6,6 @@ description: Varsayılan sağlayıcı seçimi, model çözümleme sırası, komb Yönlendirme, bir istemci tarafından gönderilen model kimliğini somut bir sağlayıcıya ve yukarı akış modeline dönüştürür. -`gpt-5.6-terra` yanında `gpt-6.1-terra` da seçilebilir. Varsayılan model ve alt ajan model listesi değişmez. [GPT-6.1 Terra sınırları, akıl yürütme ve Fast](/tr/reference/configuration/providers/#gpt-61-terra) bölümüne bakın. - ## Üst düzey yönlendirme alanları | Alan | Tip | Varsayılan | Anlamı | diff --git a/docs-site/src/content/docs/zh-cn/getting-started/quickstart.md b/docs-site/src/content/docs/zh-cn/getting-started/quickstart.md index b494fa5bd91..76d866052f8 100644 --- a/docs-site/src/content/docs/zh-cn/getting-started/quickstart.md +++ b/docs-site/src/content/docs/zh-cn/getting-started/quickstart.md @@ -5,8 +5,6 @@ description: 配置你的第一个 provider，并在三条命令内让 OpenAI Co 本指南将带你从全新安装，一路走到用一个非 OpenAI 模型运行 Codex。 -除了 `gpt-5.6-terra`，还可以选择 `gpt-6.1-terra`；默认模型和子代理模型列表均不变。参见 [GPT-6.1 Terra 的限制、推理与 Fast](/zh-cn/reference/configuration/providers/#gpt-61-terra)。 - ## 独立二进制文件（无需 npm） 你也可以使用包含 Bun 运行时的发布压缩包中的 `ocx`，无需 npm。 diff --git a/docs-site/src/content/docs/zh-cn/guides/codex-app-models.md b/docs-site/src/content/docs/zh-cn/guides/codex-app-models.md index aeaa975c102..3d2f9b0b3ff 100644 --- a/docs-site/src/content/docs/zh-cn/guides/codex-app-models.md +++ b/docs-site/src/content/docs/zh-cn/guides/codex-app-models.md @@ -30,8 +30,6 @@ cp ~/.opencodex/config.json.pre-openai-tiers-v2.bak ~/.opencodex/config.json 更早的 v1 三 provider 配置会自动迁移到这个支持单一选项的行。 -除了 `gpt-5.6-terra`，还可以选择 `gpt-6.1-terra`；默认模型和子代理模型列表均不变。参见 [GPT-6.1 Terra 的限制、推理与 Fast](/zh-cn/reference/configuration/providers/#gpt-61-terra)。 - ## Desktop 远程 allowlist 限制 如果 `codex debug models` 和 app-server 的 `model/list` 都包含某个路由模型，但 Desktop diff --git a/docs-site/src/content/docs/zh-cn/guides/model-ordering.md b/docs-site/src/content/docs/zh-cn/guides/model-ordering.md index b1af2ed77e3..ffe4ffda879 100644 --- a/docs-site/src/content/docs/zh-cn/guides/model-ordering.md +++ b/docs-site/src/content/docs/zh-cn/guides/model-ordering.md @@ -6,8 +6,6 @@ description: opencodex 如何确定 Codex 模型选择器和 spawn_agent 模型 Codex 模型选择器不会保留 opencodex 配置中 provider 的声明顺序或模型数组顺序。最终顺序由目录 priority 决定；priority 相同的路由模型则使用确定性的字母顺序。 -除了 `gpt-5.6-terra`，还可以选择 `gpt-6.1-terra`；默认模型和子代理模型列表均不变。参见 [GPT-6.1 Terra 的限制、推理与 Fast](/zh-cn/reference/configuration/providers/#gpt-61-terra)。 - ## Codex 应用的规则 Codex 的 models-manager 按 `priority` 升序排列选择器中可见的目录条目。目录数组本身的顺序会被 diff --git a/docs-site/src/content/docs/zh-cn/guides/providers.md b/docs-site/src/content/docs/zh-cn/guides/providers.md index 9f96a22e6cd..55dbf90e35e 100644 --- a/docs-site/src/content/docs/zh-cn/guides/providers.md +++ b/docs-site/src/content/docs/zh-cn/guides/providers.md @@ -5,8 +5,6 @@ description: opencodex 进行身份验证并与 LLM 提供商通信的所有方 **提供商（provider）** 是一个上游 LLM 端点，加上访问它的方式：一个 adapter、一个基础 URL、一种认证模式，以及一个可选的模型列表。提供商配置位于 `~/.opencodex/config.json` 的 `providers` 下。 -除了 `gpt-5.6-terra`，还可以选择 `gpt-6.1-terra`；默认模型和子代理模型列表均不变。参见 [GPT-6.1 Terra 的限制、推理与 Fast](/zh-cn/reference/configuration/providers/#gpt-61-terra)。 - ## OpenAI 账户模式 | Provider id | 用途 | 凭证/账户规则 | diff --git a/docs-site/src/content/docs/zh-cn/reference/adapters.md b/docs-site/src/content/docs/zh-cn/reference/adapters.md index 557f21aedac..512277d38fa 100644 --- a/docs-site/src/content/docs/zh-cn/reference/adapters.md +++ b/docs-site/src/content/docs/zh-cn/reference/adapters.md @@ -22,8 +22,6 @@ interface ProviderAdapter { 无法表示成一次 HTTP fetch 加一条响应流的 transport。随后 [`bridge.ts`](/zh-cn/reference/architecture/#桥接器) 把 event 转成 Responses SSE。 -除了 `gpt-5.6-terra`，还可以选择 `gpt-6.1-terra`；默认模型和子代理模型列表均不变。参见 [GPT-6.1 Terra 的限制、推理与 Fast](/zh-cn/reference/configuration/providers/#gpt-61-terra)。 - ## `openai-chat` **目标：** OpenAI **Chat Completions**（`POST {baseUrl}/chat/completions`）以及所有兼容 provider， diff --git a/docs-site/src/content/docs/zh-cn/reference/configuration/routing.md b/docs-site/src/content/docs/zh-cn/reference/configuration/routing.md index 85251829f3c..721b5d87873 100644 --- a/docs-site/src/content/docs/zh-cn/reference/configuration/routing.md +++ b/docs-site/src/content/docs/zh-cn/reference/configuration/routing.md @@ -5,8 +5,6 @@ description: 默认提供方选择、模型解析顺序、组合别名、目标 路由会把客户端发送的 model id 转换为一个具体的提供方和上游模型。 -除了 `gpt-5.6-terra`，还可以选择 `gpt-6.1-terra`；默认模型和子代理模型列表均不变。参见 [GPT-6.1 Terra 的限制、推理与 Fast](/zh-cn/reference/configuration/providers/#gpt-61-terra)。 - ## 顶层路由字段 | 字段 | 类型 | 默认值 | 含义 | diff --git a/docs-site/src/content/docs/zh-tw/getting-started/quickstart.md b/docs-site/src/content/docs/zh-tw/getting-started/quickstart.md index 2a427c87b6a..ea72d3cfcae 100644 --- a/docs-site/src/content/docs/zh-tw/getting-started/quickstart.md +++ b/docs-site/src/content/docs/zh-tw/getting-started/quickstart.md @@ -5,8 +5,6 @@ description: 設定你的第一個 provider,用三條命令讓 OpenAI Codex 透 本指南將帶你從全新安裝,一路走到用一個非 OpenAI 模型執行 Codex。 -除了 `gpt-5.6-terra`，也可以選擇 `gpt-6.1-terra`；預設模型與子代理模型清單均不變。參見 [GPT-6.1 Terra 的限制、推理與 Fast](/zh-tw/reference/configuration/providers/#gpt-61-terra)。 - ## 1. 執行設定嚮導 ```bash diff --git a/docs-site/src/content/docs/zh-tw/guides/codex-app-models.md b/docs-site/src/content/docs/zh-tw/guides/codex-app-models.md index 5cb15ead14b..2b9eb7c20aa 100644 --- a/docs-site/src/content/docs/zh-tw/guides/codex-app-models.md +++ b/docs-site/src/content/docs/zh-tw/guides/codex-app-models.md @@ -45,8 +45,6 @@ cp ~/.opencodex/config.json.pre-openai-tiers-v2.bak ~/.opencodex/config.json 較早的 v1 三 provider 設定會自動遷移為單一的 option-aware 列。 -除了 `gpt-5.6-terra`，也可以選擇 `gpt-6.1-terra`；預設模型與子代理模型清單均不變。參見 [GPT-6.1 Terra 的限制、推理與 Fast](/zh-tw/reference/configuration/providers/#gpt-61-terra)。 - ## Desktop 遠端 allowlist 限制 如果 `codex debug models` 和 app-server 的 `model/list` 都包含某個路由模型，但 Desktop 沒有 diff --git a/docs-site/src/content/docs/zh-tw/guides/model-ordering.md b/docs-site/src/content/docs/zh-tw/guides/model-ordering.md index c9c42f0f3ba..d944aef1993 100644 --- a/docs-site/src/content/docs/zh-tw/guides/model-ordering.md +++ b/docs-site/src/content/docs/zh-tw/guides/model-ordering.md @@ -6,8 +6,6 @@ description: opencodex 如何確定 Codex 模型選擇器和 spawn_agent 模型 Codex 模型選擇器不會保留 opencodex 設定中 provider 的宣告順序或模型陣列順序。最終順序由目錄 priority 決定；priority 相同的路由模型則使用確定性的字母順序。 -除了 `gpt-5.6-terra`，也可以選擇 `gpt-6.1-terra`；預設模型與子代理模型清單均不變。參見 [GPT-6.1 Terra 的限制、推理與 Fast](/zh-tw/reference/configuration/providers/#gpt-61-terra)。 - ## Codex 應用的規則 Codex 的 models-manager 按 `priority` 升序排列選擇器中可見的目錄條目。目錄陣列本身的順序會被 diff --git a/docs-site/src/content/docs/zh-tw/guides/providers.md b/docs-site/src/content/docs/zh-tw/guides/providers.md index 0a28ca7ab97..9683b3925be 100644 --- a/docs-site/src/content/docs/zh-tw/guides/providers.md +++ b/docs-site/src/content/docs/zh-tw/guides/providers.md @@ -6,8 +6,6 @@ description: opencodex 進行身分驗證並與 LLM 供應商通訊的所有方 **供應商（provider）** 是一個上游 LLM 端點，加上存取它的方式：adapter、base URL、認證模式，以及 可選的模型列表。供應商設定放在 `~/.opencodex/config.json` 的 `providers` 下。 -除了 `gpt-5.6-terra`，也可以選擇 `gpt-6.1-terra`；預設模型與子代理模型清單均不變。參見 [GPT-6.1 Terra 的限制、推理與 Fast](/zh-tw/reference/configuration/providers/#gpt-61-terra)。 - ## OpenAI 帳號模式 | Provider id | 用途 | 憑證／帳號規則 | diff --git a/docs-site/src/content/docs/zh-tw/reference/adapters.md b/docs-site/src/content/docs/zh-tw/reference/adapters.md index aadd0493a54..37ac0080cd5 100644 --- a/docs-site/src/content/docs/zh-tw/reference/adapters.md +++ b/docs-site/src/content/docs/zh-tw/reference/adapters.md @@ -22,8 +22,6 @@ interface ProviderAdapter { 無法表示成一次 HTTP fetch 加一條回應流的 transport。隨後 [`bridge.ts`](/zh-tw/reference/architecture/#橋接器) 把 event 轉成 Responses SSE。 -除了 `gpt-5.6-terra`，也可以選擇 `gpt-6.1-terra`；預設模型與子代理模型清單均不變。參見 [GPT-6.1 Terra 的限制、推理與 Fast](/zh-tw/reference/configuration/providers/#gpt-61-terra)。 - ## `openai-chat` **目標：** OpenAI **Chat Completions**（`POST {baseUrl}/chat/completions`）以及所有相容 provider， diff --git a/docs-site/src/content/docs/zh-tw/reference/configuration/routing.md b/docs-site/src/content/docs/zh-tw/reference/configuration/routing.md index 201b28ecc8f..4dd6d004fe6 100644 --- a/docs-site/src/content/docs/zh-tw/reference/configuration/routing.md +++ b/docs-site/src/content/docs/zh-tw/reference/configuration/routing.md @@ -5,8 +5,6 @@ description: 預設供應商選擇、模型解析順序、combo 別名、目標 路由將客戶端送出的模型 id 轉為一個具體的供應商與上游模型。 -除了 `gpt-5.6-terra`，也可以選擇 `gpt-6.1-terra`；預設模型與子代理模型清單均不變。參見 [GPT-6.1 Terra 的限制、推理與 Fast](/zh-tw/reference/configuration/providers/#gpt-61-terra)。 - ## 頂層路由欄位 | 欄位 | 型別 | 預設值 | 意義 | diff --git a/tests/ci-workflows/docs-gpt61-terra.test.ts b/tests/ci-workflows/docs-gpt61-terra.test.ts index 2278bc58532..dc1ab4eb439 100644 --- a/tests/ci-workflows/docs-gpt61-terra.test.ts +++ b/tests/ci-workflows/docs-gpt61-terra.test.ts @@ -25,13 +25,11 @@ describe("GPT-6.1 Terra documentation", () => { expect(section).not.toMatch(/Ultrafast|ultrafast/); }); - test(`${locale || "en"}: affected guides link to Terra without replacing older models`, () => { - for (const page of ["guides/providers", "guides/codex-app-models", "guides/model-ordering", - "getting-started/quickstart", "reference/adapters", "reference/configuration/routing"]) { + test(`${locale || "en"}: model tables list Terra without replacing older models`, () => { + for (const page of ["guides/providers", "guides/codex-app-models"]) { const doc = read(locale, page); expect(doc, `${locale}/${page}`).toContain("gpt-6.1-terra"); expect(doc).toContain("gpt-5.6-terra"); - expect(doc).toContain("/reference/configuration/providers/#gpt-61-terra"); expect(doc.split("\n").filter(line => line.startsWith("| Cursor |")) .join("\n")).not.toContain("gpt-6.1-terra"); } From e342efb0c61703b38a925f2dc8880709dab4063d Mon Sep 17 00:00:00 2001 From: JUN <243035832+lidge-jun@users.noreply.github.com> Date: Tue, 27 Oct 2026 08:33:25 +0900 Subject: [PATCH 4/9] feat(codex): add GPT-6.1 Terra alongside existing native models Pin the supplied upstream row verbatim and register its native 500k/872k context, low-through-ultra ladder, Fast-only tiers and multi-agent v2. Keep GPT-5.6 Terra, defaults, configured-native template and roster version. Apply Terra's client minimum only to per-model absence evidence so unrelated roster success TTLs stay unchanged. Verify native, account-qualified and OpenAI-forward rows, Claude context and labels, and ultra-to-max wire folding. Keep Cursor and other lanes untouched. Validation: 613 affected tests and 38 layout/ratchet tests pass on Bun 1.4.4; typecheck, structure:check and privacy:scan pass. --- scripts/test-layout/layout.json | 2 +- src/codex/catalog/metadata.ts | 6 + src/codex/catalog/native-models.ts | 21 ++- src/codex/catalog/pinned-models.ts | 3 +- src/codex/data/roster-pinned-models.json | 178 +++++++++++++++++- src/codex/model-entitlements.ts | 11 +- structure/catalog.md | 6 +- structure/providers/openai-accounts.md | 8 +- .../claude-context-windows.test.ts | 2 + .../claude-desktop-native-context.test.ts | 15 +- .../claude-model-default-labels.test.ts | 1 + .../catalog-native-max-context.test.ts | 1 + .../codex-catalog-ladders.test.ts | 2 +- .../gpt6-native-rows.test.ts | 6 +- .../gpt61-terra-rows.test.ts | 141 ++++++++++++++ .../native-model-toggle.test.ts | 2 +- tests/fixtures/test-layout-expected.json | 1 + ...responses-native-ultra-effort-wire.test.ts | 4 +- 18 files changed, 385 insertions(+), 25 deletions(-) create mode 100644 tests/codex-integration/gpt61-terra-rows.test.ts diff --git a/scripts/test-layout/layout.json b/scripts/test-layout/layout.json index ac24774a337..d098143e59f 100644 --- a/scripts/test-layout/layout.json +++ b/scripts/test-layout/layout.json @@ -1011,7 +1011,7 @@ "google-wire-compiler.test.ts": "adapters/google", "google-wire-shape.test.ts": "adapters/google", "gpt6-native-rows.test.ts": "codex-integration", - "gpt61-sol-rows.test.ts": "codex-integration", + "gpt61-sol-rows.test.ts": "codex-integration", "gpt61-terra-rows.test.ts": "codex-integration", "grok-attribution.test.ts": "providers/xai", "grok-config-inject.test.ts": "providers/xai", "grok-config-write-lock.test.ts": "providers/xai", "grok-effort-inject.test.ts": "providers/xai", diff --git a/src/codex/catalog/metadata.ts b/src/codex/catalog/metadata.ts index ada0e738937..3a5afc515fe 100644 --- a/src/codex/catalog/metadata.ts +++ b/src/codex/catalog/metadata.ts @@ -44,12 +44,14 @@ import { ACCOUNT_GATED_NATIVE_OPENAI_MODELS, NATIVE_GPT6_CONTEXT, NATIVE_GPT61_SOL_CONTEXT, + NATIVE_GPT61_TERRA_CONTEXT, NATIVE_DAYBREAK_BLUE_MODEL, NATIVE_GPT6_ASTRA_MINOR_MODEL, NATIVE_GPT6_ASTRA_MODEL, NATIVE_GPT6_LUNA_MODEL, NATIVE_GPT6_SOL_MODEL, NATIVE_GPT61_SOL_MODEL, + NATIVE_GPT61_TERRA_MODEL, NATIVE_RESERVE_MODEL, NATIVE_OPENAI_CAPABILITY_ALIAS_MODELS, NATIVE_OPENAI_MODELS, @@ -76,6 +78,7 @@ export { NATIVE_GPT6_LUNA_MODEL, NATIVE_GPT6_SOL_MODEL, NATIVE_GPT61_SOL_MODEL, + NATIVE_GPT61_TERRA_MODEL, NATIVE_OPENAI_CAPABILITY_ALIAS_MODELS, NATIVE_OPENAI_MODELS, SELF_DESCRIBED_NATIVE_OPENAI_MODELS, @@ -97,6 +100,8 @@ export const DOCUMENTED_NATIVE_OPENAI_ADDITIONS = [ NATIVE_GPT6_SOL_MODEL, NATIVE_GPT6_LUNA_MODEL, // GPT-6.1 Sol needs client_version >= 0.153.0 upstream; older installed catalogs lack it. NATIVE_GPT61_SOL_MODEL, + // Terra's pinned row has the same client floor and backfills older installed catalogs too. + NATIVE_GPT61_TERRA_MODEL, ]; export function configuredNativeAliasSlugs( @@ -207,6 +212,7 @@ export const NATIVE_OPENAI_CONTEXT_OVERRIDES: Record