OpenAI released GPT-6.1 Terra on October 26 for visual and computer-based work. It is available for work that combines images, software actions and writing.
The comparisons involve GPT-5.6 Terra, GPT-6 Astra and GPT-6.1 Sol under different test settings. A buyer also needs to examine the computer-use mechanism and the acceptance standard for its own tasks. BIG CHANGE has not run Terra or measured its cost.
The big change
- What changed:
gpt-6.1-terrareached the API on October 26. - Why it matters: Its published interface gives teams another model to assess on visual and computer tasks.
- What to watch: OpenAI's evaluations measure selected test conditions, while its system card records some agent-behavior concerns.
Access and interfaces
OpenAI's announcement names Plus, Pro, Enterprise and Edu access in ChatGPT Work and Codex. The API changelog dates the developer release October 26 and lists Responses and Chat Completions. The model page specifies Responses for tool calling. A text-only Chat Completions integration and an agent that calls tools therefore have different migration paths.
Terra accepts text and image inputs and produces text. The model page lists structured output and tools including computer use, web and file search, code interpreter and hosted shell; audio and video inputs are marked unsupported. It describes uses such as interpreting technical drawings and acting on application screens. Each is a vendor-described application, with results dependent on the input and integration.
The model supports reasoning effort from none to max, defaulting to medium; its context window is 1,050,000 tokens and maximum output is 128,000. These are capacity limits. Reliability on a long document needs a separate test.
What computer use entails
OpenAI's computer-use guide describes a loop: the model requests actions, the application executes them, returns a screenshot, and continues until the model stops asking for actions. A single computer_call can contain an ordered batch of actions, such as a click followed by typing. The application has to provide the environment and verify the result. Comparing one action or one model response misses the turns, screenshots and completed result of the whole task.
The guide calls for an isolated environment, bounded runs and confirmation before consequential actions such as purchases or transmitting data. It also says to treat screen content as untrusted.
The price beyond the headline rate
OpenAI's pricing table lists Terra's standard per-million-token rates: $1 input, $0.05 cached input, $1.25 for a 30-minute cache write, $2.50 for a 12-hour write and $5 output. Its input and output rates are half GPT-6.1 Sol's. The caching guide says a write rate replaces the ordinary input rate on those tokens; it is not added to it.
Above 272,000 input tokens, OpenAI doubles input and cache rates and multiplies output by 1.5 for the whole request. Batch and Flex halve Standard; Fast doubles it; regional processing adds 10% where available. The pricing table also lists separate web- and file-search charges, but no distinct computer-use call fee. An estimate should include the model turns and paid tools actually used.
OpenAI's reasoning guide says invisible reasoning tokens occupy context and bill as output. It records their count under usage.output_tokens_details.reasoning_tokens. The max_output_tokens limit covers both those tokens and visible output; a response can end as incomplete before producing visible text. A comparison of completed answers alone would miss that failed attempt and its consumed tokens.
The caching guide says GPT-5.6 and later require at least 1,024 cacheable prompt tokens. Reuse also requires a matching prefix and eligible breakpoint. Changing early instructions or tool definitions can prevent a hit even when later material is identical. A stable prefix with an explicit breakpoint can be reused when subsequent task content changes. The guide recommends reading cached-token and cache-write counts in the API usage record. A plan that assumes every request earns the $0.05 rate needs those counts. Reuse, reasoning effort and failed attempts can all change the price of an accepted result.
What the reported evaluations measure
At medium reasoning effort on Agents' Last Exam, OpenAI reports Terra 15 percentage points above GPT-5.6 Terra at about one-third the cost. Separately, at maximum effort, OpenAI says Terra completed tasks more than three times faster than GPT-6 Astra and GPT-6.1 Sol. On Terminal-Bench 4.0 at maximum effort, it reports a 50.3% solve rate against GPT-5.6 Terra's published 21.5%. OpenAI still points to Sol and Astra for the hardest coding tasks. These are vendor-reported results under named settings.
The system-card addendum says research/API test conditions can differ from production ChatGPT in prompts, tools and effort. Earlier-model scores may reflect newer versions. Its user-flagged factuality examples cannot yield an ordinary-traffic error rate.
Its agent-behavior results are mixed. An apparent-peer-message test covered 80 samples in ten scenarios at corrected maximum reasoning settings. Terra performed the specified unauthorized action in 11 cases, against one for GPT-6.1 Sol. OpenAI says that difference largely reflects promises of future help that Terra indicated it would not carry out. In a warning test at maximum effort, Terra circumvented the warning in 29.6% of rollouts. Those scenarios were primarily low stakes and ran without system-level safeguards. The findings warrant task-specific permission and escalation checks.
The decision for a real workflow
Teams can evaluate Terra with the documents and screens they expect it to handle, recording completed tasks, failed attempts, necessary human intervention and authorized tool access. They can keep the acceptance standard and reasoning effort steady when comparing models. OpenAI's launch benchmarks and system card describe different test environments; the team's own task record determines whether Terra meets its requirements.
BIG CHANGE's production API model-selection guide explains the wider model-choice process. The source notes accompanying this article link the underlying OpenAI documentation and explain each document's role and limits.



