Repository navigation
[Feat] Add GPT-6.1 Terra model support - #3595
Conversation
|
No new code issues found. The prior runtime-registration finding is fixed. See session Confirmed generated task config registers all three distinct-role Terra routes, and helper configs register them with both generated and existing provider configuration. Current-head CI tests, lint, type checking, knip, and docs validation passed; some build and analysis checks were still running when inspected.
Reviewed 06b9791 |
|
Fixed and pushed in 06b97918.
Validation: 408 focused tests passed (127 types, 119 worker, 46 helper, 116 web), including the 18-case task role/provider/gateway matrix and six helper-config cases. Six actual OpenCode 1.18.30 model-listing probes passed with isolated configs/synthetic credentials and no inference requests. Lint, typecheck, knip, formatting, docs checks, diff checks and pre-push gates passed. Remaining validation limits: optional commit-time Roomote Judgement evaluation reported incomplete evidence/timeouts; full evaluation is still outstanding. Paid inference and account entitlements were not exercised, and CI completion has not been checked. No actionable review findings remain from the fetched review inventory. |
What changed
azure/gpt-6.1-terra@swedencentral, and Azure'sgpt-6.1-terradeployment name.Why this change was made
Users should be able to select the newly released Terra model through verified provider routes. Runtime definitions also prevent model lookup failures when Requesty or Azure Terra is assigned only to vision, advisor, or explore and OpenCode's refreshed catalog does not yet list it.
Impact and metadata sources
Provider metadata was verified on October 26, 2026:
gpt-6.1-terragpt-6.1-terrain Codex; Fast support, subject to plan and rolloutopenai/gpt-6.1-terra; Roomote uses its existing namespace rebasingopenai/gpt-6.1-terragpt-6.1-terra(2026-10-26); requires matching deployment name and account/region accessazure/gpt-6.1-terra@swedencentralOpenAI documents 1,050,000 context / 922,000 maximum input / 128,000 maximum output tokens, text/image input and text output, streaming, structured outputs, and tool calling through Responses. Reasoning supports
none,low,medium,high,xhigh, andmax; Roomote retains its existing effort scale. Standard pricing per million tokens: $1 input / $0.05 cache read / $1.25 30-minute cache write / $5 output. Above 272K input tokens, input/cache rates double and output is 1.5x. Vercel Standard is $1/$5 input/output; the selected Requesty route is $1.20/$6 and $0.06 cache read. Azure prices vary by deployment/region.OpenCode Zen/Go, GitHub Copilot, and Bedrock Terra routes remain unconfirmed and are not added. Azure/Requesty UI pricing metadata may remain sparse pending upstream catalog entries; their runtime definitions no longer depend on that publication. Paid inference and account entitlements were not exercised. This change does not add a computer-use subsystem.
How it was tested
pnpm lint:fast,pnpm check-types:fast(27 packages),pnpm knip, changed-fileoxfmt --check,git diff --check, andpnpm --filter @roomote/docs checkpassed. All pre-push gates passed with hooks enabled.Checklist
[Fix],[Feat],[Improve],[Refactor],[Docs], or[Chore]followed by a user-facing descriptionpnpm lintandpnpm check-typespass locally — repository-recommended fast equivalents and changed-file formatting passed; full formatting-inclusive aliases were not runpnpm changeset— no changeset added; release preparation can include this model addition in its missing-notes audit