GPT-5.6 Codex App Guide: Sol, Terra, Luna, Max & Ultra
In ChatGPT, GPT-5.6 primarily improves complex conversation and knowledge work. In the Codex App, the more important change is that the model can operate inside repositories, terminals, browsers, and multi-agent workflows until a task is complete.
Codex users can choose among Sol, Terra, and Luna, configure reasoning effort, use max for more demanding work, and access ultra on eligible plans for parallel agent coordination.
This guide explains how to select a model, what max and ultra actually change, how to interpret the 1.05M API context specification, and when a frontier model is worth the additional cost.
Quick verdict
- GPT-5.6 launched in Codex on July 9, 2026.
- Free and Go users can access GPT-5.6 Terra in Codex under the launch rules.
- Plus, Pro, Business, and Enterprise users can choose Sol, Terra, or Luna.
maxincreases reasoning effort for demanding tasks.ultracoordinates agents across parallel workstreams and is available in Codex to Plus and higher plans.- OpenAI lists ChatGPT desktop app Codex mode
26.707.30751and Codex CLI0.144.0as minimum versions for GPT-5.6 access.
The shortest recommendation is: use Sol for difficult engineering, Terra for everyday development, Luna for fast high-volume tasks, and ultra only when the work can benefit from parallel decomposition.
Codex App is more than a coding chat
The Codex App is a command center for agents. It can read and edit local code, execute commands and tests, present diffs for review, isolate parallel work with worktrees, reuse skills, run automations, and preserve project context across threads.
GPT-5.6 should therefore be evaluated across an execution chain, not by asking whether it can generate one function.
Sol vs Terra vs Luna in Codex
| Model | Codex role | Recommended tasks | |---|---|---| | GPT-5.6 Sol | Flagship capability | Architecture, large refactors, hard debugging, research | | GPT-5.6 Terra | Balanced default | Daily coding, tests, PRs, documentation, routine agents | | GPT-5.6 Luna | Fast and affordable | Small fixes, search, formatting, clear batch tasks |
Use Sol when a task has uncertainty, cross-module decisions, complex tools, or a high cost of failure. Use Terra for most routine repository work. Use Luna when scope is clear and throughput matters more than maximum reasoning depth.
What is the difference between max and ultra?
max allocates more reasoning effort to the selected model and task. It is useful when one difficult workstream needs deeper analysis.
ultra is different. OpenAI describes it as a highest-capability setting that coordinates multiple agents across parallel workstreams. A backend agent, frontend agent, test agent, and security reviewer can investigate independently before a lead agent synthesizes the result.
Parallelism is not free. A one-file edit may become slower if it is split among several agents. Ultra is valuable when the task has independent workstreams, not simply because it sounds more powerful.
GPT-5.6 coding performance
OpenAI reports the following results for GPT-5.6 Sol:
- 80 on Artificial Analysis Coding Agent Index v1.1
- 72.7% on DeepSWE v1.1
- 88.8% on Terminal-Bench 2.1
- 91.9% for Sol Ultra on Terminal-Bench 2.1
- 64.6% on SWE-Bench Pro
The pattern is more useful than any single rank: agent, terminal, and tool execution all improved. Production evaluation should still measure test pass rate, unnecessary changes, self-correction, goal drift, wall-clock time, token use, and human review burden on private repositories.
What does the 1.05M context window mean?
OpenAI's API documentation lists a 1.05M-token context window and 128K maximum output for Sol, Terra, and Luna.
That is a model-family API specification, not a promise of unlimited context in every Codex subscription task. Codex usage also depends on plan allowance, product context management, tool output, and current service policy.
Large repositories still benefit from a repository map, targeted retrieval, compact test and decision summaries, and checkpointed long-running goals instead of reading every file indiscriminately.
GPT-5.6 API pricing
| Model | Input / 1M tokens | Output / 1M tokens | |---|---:|---:| | GPT-5.6 Sol | $5 | $30 | | GPT-5.6 Terra | $2.50 | $15 | | GPT-5.6 Luna | $1 | $6 |
Requests above 272K input tokens use long-context pricing: the full request is billed at twice the input rate and 1.5 times the output rate.
Codex subscription allowances and API token billing are separate. Subscription users should evaluate Codex plan limits and credits, while programmatic workflows should measure tokens, tools, retries, and successful task cost.
Codex App vs an API agent
Codex App is designed for direct human supervision with projects, threads, diffs, permissions, worktrees, and local repository access. The API is designed for software systems that require explicit model selection, configurable reasoning, batch execution, routing, and automated retry logic.
GPT-5.6 in the Responses API also introduces Programmatic Tool Calling for in-memory coordination of tools and intermediate results. Multi-agent support is initially available in beta for concurrent subagents and synthesis.
Teams comparing GPT-5.6 with Claude, Grok, GLM, and DeepSeek can review live model pricing and availability, buy API tokens, and the API integration tutorials. Do not make purchasing decisions from launch pricing alone; verify current model support, allowances, regional access, and platform rates.
Who should upgrade?
GPT-5.6 in Codex is most relevant for teams maintaining medium or large repositories, coordinating parallel frontend/backend/test work, building security or scientific software, delivering products end to end, or routing tasks among model tiers.
Sol and ultra are unnecessary defaults for one-file fixes, formatting, simple replacements, low-risk documentation, or short tasks that cannot run in parallel.
A practical model-routing policy
Teams do not need a complicated router to benefit from three model tiers. Start with a simple policy based on task risk and scope:
- route search, formatting, renaming, and tightly specified edits to Luna
- route ordinary bug fixes, tests, PR feedback, and documentation to Terra
- route architecture, incident analysis, migrations, security work, and unclear repository problems to Sol
- increase reasoning to max only after the task proves difficult or the cost of a shallow answer is high
- use ultra when independent workstreams can run concurrently and the synthesis step has clear acceptance criteria
The routing decision should remain reversible. If Luna or Terra becomes stuck, escalate the same evidence and test results to the next tier instead of restarting the task without context.
Production evaluation checklist
Before standardizing on GPT-5.6 for a repository, run a small private benchmark that represents real work. Include a contained bug, a cross-module change, a failing test investigation, a documentation task, and one long-running agent workflow.
Record accepted-task rate, tests passed, unrelated files changed, tool failures, human review minutes, total elapsed time, and credits or API tokens consumed. Repeat the same tasks with the current default model. This exposes whether a higher benchmark score actually translates into faster delivery.
For multi-agent runs, add two more measurements: duplicated work across agents and synthesis errors. Parallel execution only helps when ownership is disjoint and the lead agent can reconcile results without dropping constraints.
Safety and repository control
The Codex App uses configurable system-level sandboxing and permission rules. Teams should still begin with narrow repository access, review diffs before merging, protect secrets from prompts and logs, and require tests for behavior-changing patches.
For destructive commands, production credentials, deployment actions, or external messages, keep explicit human approval in the workflow. A more capable model increases the amount of work an agent can perform, which makes clear boundaries more important rather than less important.
Final verdict
GPT-5.6 changes Codex App by turning model selection into workflow selection. Sol, Terra, and Luna cover capability, balance, and speed. Max deepens one workstream, while ultra coordinates several agents in parallel.
That is more mature than always selecting the largest model because real engineering tasks vary dramatically in complexity and value.
If your workflow has moved from code completion to agent execution, GPT-5.6 with Codex App is worth testing. The best setup is not Sol Ultra for everything, but a model tier matched to the difficulty and structure of each task.
FAQ
Which GPT-5.6 model is strongest in Codex App?
Sol is the flagship tier, while ultra is the highest-capability multi-agent setting. Results still depend on whether the task can be divided effectively and on plan allowances.
Can Free and Go users access GPT-5.6 in Codex?
At launch, OpenAI states that Free and Go users can access GPT-5.6 Terra in Codex. Sol and Luna require eligible higher plans.
Which version is required for GPT-5.6 Codex?
OpenAI lists ChatGPT desktop app Codex mode 26.707.30751 or Codex CLI 0.144.0 as minimum versions.
Does GPT-5.6 Codex support a 1M context window?
The GPT-5.6 API models have a 1.05M context specification. Actual Codex App context and usage depend on product policy, plan, and task management.
Is Terra or Luna better for daily coding?
Terra is the stronger balanced default for quality and cost. Luna is better for fast, clear, high-volume tasks where maximum reasoning is unnecessary.