Which GPT-5.6 Tier Should You Default To? Luna First, Terra as the Generalist, Sol on Escalation

The right GPT-5.6 default depends first on where you are working. In a standard ChatGPT conversation, keep GPT-5.5 Instant as the everyday default and move to GPT-5.6 Sol Medium only when the task needs real reasoning. Terra and Luna are not selectable there. In ChatGPT Work, Codex, or the API, start with Luna for bounded and reversible work, use Terra for mixed everyday jobs that need more judgment, and reserve Sol for long-horizon, multi-file, high-stakes, or agentic work.

That is a different answer from simply choosing Terra because OpenAI calls it the everyday default. Terra is the easiest one-model compromise. It is not always the cheapest intelligent route, and independent benchmark data suggests Luna or Sol can beat it on cost versus capability at selected reasoning levels. The quota-smart habit is escalation, not permanent allegiance to one tier.

The first choice is the surface, not the tier

The most common misconception is that Sol, Terra, and Luna are three interchangeable buttons in the normal ChatGPT model picker. OpenAI’s current GPT-5.6 in ChatGPT documentation says otherwise. GPT-5.5 Instant remains the default in standard conversations. Sol powers Medium, High, and Extra High reasoning, while Sol Pro powers the Pro option. Terra and Luna are available through Work, Codex, and the API, not as selectable models in an ordinary chat.

That changes the decision tree. A Plus subscriber in a normal chat is not choosing Luna versus Terra versus Sol. The practical ladder is Instant, then Sol Medium, then Sol High. Plus includes Medium and High, while Pro, Business, and Enterprise also include Extra High and Sol Pro, subject to account and workspace settings. OpenAI also says an automatic switch from Instant to Medium does not consume the allowance for manually selected reasoning, so leaving automatic routing enabled can be less wasteful than selecting Sol for every prompt.

Work and Codex are the places where the three-tier choice becomes real. OpenAI says Work and Codex share pricing, credits, and usage limits. Plus, Pro, Business, and Enterprise users can access all three GPT-5.6 tiers there. ChatGPT Team is now called Business, so current Team-plan guidance should be read under the Business label.

The default routing rule

Use Luna first when the task is cheap to retry and easy to judge. Good candidates include classification, extraction, formatting, first-pass summaries, routine code edits, test generation, and repeated transformations with a clear acceptance check. Luna is OpenAI’s fastest and lowest-cost GPT-5.6 tier, and its API rate is $1 per million input tokens and $6 per million output tokens.

Use Terra when the work is still everyday but no longer mechanical. It is the sensible generalist for drafting from several sources, debugging a contained feature, comparing options, restructuring a document, or handling instructions with a few interacting constraints. OpenAI positions Terra as the balance of capability, speed, and cost. Its API rate is $2.50 per million input tokens and $15 per million output tokens.

Escalate to Sol when a failed answer is expensive, the task unfolds over many steps, or the model must keep a large working state. That includes architectural changes across a repository, ambiguous research synthesis, long-horizon agent runs, difficult debugging, security-sensitive analysis, or work where missing one constraint invalidates the result. Sol costs $5 per million input tokens and $30 per million output tokens through the API.

The price ratios make the routing cost visible. At the same input and output volumes, Terra costs 2.5 times Luna, while Sol costs 5 times Luna. That is a derived comparison from OpenAI’s current token rates. Sol only earns that premium when its extra reasoning lowers the chance of a costly failure or replaces several lower-tier attempts.

What the rate limits actually mean

OpenAI publishes ranges, not guaranteed prompt counts, for Work and Codex. On Plus, the current estimate is 15 to 90 local Sol messages, 20 to 110 Terra messages, or 50 to 280 Luna messages per five-hour window. Business carries the same published ranges. Local messages and cloud tasks share that window, and additional weekly limits may apply.

The two Pro plans multiply the Plus allowance. Pro at $100 per month is the 5x tier, with published five-hour ranges of 75 to 450 Sol messages, 100 to 550 Terra messages, and 250 to 1,400 Luna messages. Pro at $200 is the 20x tier, with 300 to 1,800 Sol, 400 to 2,200 Terra, and 1,000 to 5,600 Luna messages. These are still estimates, not entitlements to a fixed number of turns.

Plus costs $20 per month. Business costs $20 per user per month when billed annually or $25 per user per month when billed monthly, with a two-user minimum. Enterprise and Edu use contact-sales pricing. Enterprise and Edu workspaces without flexible pricing generally receive the same per-seat usage limits as Plus for most Work and Codex features; flexible-pricing workspaces have no fixed rate limit because usage scales with credits.

Standard ChatGPT is different. OpenAI says GPT-5.6 uses the existing allowances for automatic reasoning, manually selected reasoning, and Pro, but its GPT-5.6 help page does not publish a fixed Sol message count for Plus, Pro, Business, or Enterprise. When a manually selected GPT-5.6 reasoning allowance is exhausted, ChatGPT may continue with GPT-5.4 Thinking mini. On Pro, a model with a separate allowance can become temporarily unavailable until its reset time.

A prompt is not a stable unit of quota. OpenAI says consumption varies with the model, task size, context, reasoning, tool use, retrieval, caching, and whether work runs locally or in the cloud. The same-looking task can consume a different share of the allowance. Large codebases, long sessions, unnecessary files, oversized instructions, and extra MCP servers all increase the amount of context the system must carry.

Why Terra is not an automatic answer

Terra is the safest recommendation when someone wants one model and refuses to route. It sits between Luna and Sol on both price and OpenAI’s stated positioning. That does not make it the best value at every reasoning level.

Artificial Analysis, which says it supported OpenAI’s pre-release evaluation, scored Sol, Terra, and Luna at 59, 55, and 51 on its Intelligence Index at maximum reasoning. It estimated per-task costs of $1.04, $0.55, and $0.21. More consequentially, its cost-versus-intelligence analysis placed Luna and Sol on the Pareto frontier ahead of Terra across reasoning efforts: for each Terra setting, it found a Luna or Sol setting with more intelligence at no extra cost, or similar intelligence at lower cost.

That benchmark does not prove Terra is a bad model. It measures selected tasks through a specific evaluation setup, not every workflow. It does reject the lazy rule that the middle tier must always be the rational default. Luna can be the better starting point when mistakes are visible and retries are cheap. Sol can be the better economic choice when a weaker model would require repeated attempts or leave a difficult job unfinished. Terra remains useful in the wide middle where you want a capable generalist without Sol’s cost.

What users report after the launch

The community evidence is early, self-selected, and not a representative survey. It is still useful for finding failure modes that a pricing card compresses into a range.

The clearest user-reported consensus is that quota burn follows task shape more than prompt count. In an r/ChatGPT Sol Ultra thread, a Plus user said two large tasks exhausted the allowance. Other r/ChatGPT users and an r/OpenAI poster reported similarly sharp Sol consumption during coding work. These are individual reports, not measured rates, but they align with OpenAI’s statement that long-running, high-context and tool-heavy work uses more allowance per message.

Terra produces the strongest split. One r/OpenAI user reported that Terra found flaws in a plan produced with other models, while the original poster in the same thread said a Terra task reached the shared limit quickly without finishing. A separate r/ChatGPT poster described Terra as a coding downgrade from GPT-5.5. The useful conclusion is not that Terra is good or bad. Its value depends on whether the task benefits from its middle ground or exposes it to long agent loops that still consume substantial quota.

Luna is viable for more than trivial chat, but it is not a quota guarantee. A public OpenAI developer forum discussion includes users who said Luna Light consumed more allowance than expected on tool-heavy coding tasks. On LinkedIn, practitioners separately argued that routing matters more than always choosing the frontier model and recommended smaller batches and lower tiers for routine work. Those are user-reported practices, not verified performance claims.

The recurring workaround is consistent across the discussions: keep a lower-cost model at a modest reasoning level for daily work, narrow the file and tool context, and escalate only after the output reveals a real failure. That matches OpenAI’s own advice to trim unnecessary context, limit source material and MCP servers, switch to a smaller model near the limit, buy additional credits on eligible plans, or use an API key for usage-based local tasks.

A quota-preserving escalation policy

Use this policy instead of making Sol, Terra, or Luna a permanent default:

1. Start with the cheapest model that can be checked. In Work, Codex, or the API, choose Luna for bounded tasks with an objective pass condition. In standard ChatGPT, stay on Instant.
2. Move to Terra when the task needs judgment, not endurance. Escalate when Luna misses relationships among sources, mishandles interacting constraints, or needs repeated correction. Keep the scope tight before increasing reasoning effort.
3. Move to Sol when the failure cost or horizon changes. Use it for ambiguous multi-step work, large coordinated edits, agentic execution, difficult research, or high-stakes review. Start at Medium. Raise reasoning only when the first result shows a specific gap.
4. Change the task before buying more model. Remove irrelevant files, split independent work, disable unused tools and MCP servers, shorten inherited instructions, and check the usage dashboard. A smaller context can save more quota than dropping one model tier.

Terra is still the clean default for a user who will not route. For anyone willing to make one extra decision, Luna-first with explicit Sol escalation is the better quota policy. It preserves the middle tier for cases where it has a job to do, rather than treating the word everyday as proof that every task belongs there.