How to Choose GPT-5.6 Sol, Terra, and Luna: Chat Experience, Price, and Task Boundaries
OpenAI updated Sol in ChatGPT and expanded Luna access for free users on August 6, so model choice must distinguish Chat from API, Work, and Codex behavior.
Key takeaways
OpenAI updated ChatGPT on August 6, 2026. GPT-5.6 Sol for Plus and Pro users is designed to give more focused and reliable answers, with a slider that changes how much thought ChatGPT uses. Free and Go users are gradually moving to GPT-5.6 Luna as the default model and gaining broader text-chat access plus a Think button for harder questions. This is a Chat experience change: OpenAI says the Sol model used by Work and Codex is not changing in this release. ENHE's existing Sol, Terra, and Luna selection page should therefore add the product-boundary check instead of creating a duplicate GPT-5.6 event page.
# How to Choose GPT-5.6 Sol, Terra, and Luna: Chat Experience, Price, and Task Boundaries
First published: July 10, 2026 ; updated: August 7, 2026
Table of contents
- Direct answer
- Fact sources
- Action steps
- Why it matters
- Impact for ordinary AI users
- Related tools and tutorials
- FAQ
- Source links
Direct answer
This update does not put every GPT-5.6 surface under one set of rules. Plus and Pro users should choose faster or deeper thought in Chat based on the task. Free and Go users should watch for the gradual Luna default and Think-button availability. API, ChatGPT Work, and Codex users should not treat this Chat update as evidence that their model capability, pricing, or workspace behavior has changed, because OpenAI explicitly says the Sol model used by Work and Codex is unchanged.
Fact sources
OpenAI published "Improving GPT-5.6 Sol in ChatGPT—and expanding access to GPT-5.6 Luna for free users" on August 6, 2026. It says GPT-5.6 Sol in ChatGPT is intended to give more focused answers and reduce factual mistakes when answers rely on dates, numbers, sources, rules, or assumptions.
The announcement says Plus and Pro users can use a slider on web, mobile, and desktop to choose how much thought goes into an answer. Free and Go users are gradually moving to GPT-5.6 Luna as the default model and gaining broader text-chat access plus a Think button; file uploads, images, and other tools still have limits.
The same announcement says this optimized GPT-5.6 Sol is available only in ChatGPT's Chat experience. The GPT-5.6 Sol used by Work and Codex is not changing. API pricing, Fast mode, Work, and Codex workflows should therefore continue to use their own documentation and actual account settings.
ENHE already has a Sol, Terra, and Luna selection guide plus GPT-5.6, ChatGPT Work, and safe-testing coverage. The August 6 change adds a practical Chat-entry-point boundary instead of creating a second page for the same selection task.
Five steps to recheck GPT-5.6 by product entry point
- Identify whether the task is in ChatGPT Chat, the API, ChatGPT Work, or Codex. Do not automatically apply an announcement for one entry point to another.
- For Plus or Pro in Chat, test the faster and deeper thought settings with the same low-risk prompt and record factual checks, formatting, wait time, and rework.
- For Free or Go, check whether Luna and Think have reached the account. Wait for official rollout rather than attempting a workaround.
- For API, Work, or Codex, keep using the relevant model, price, permission, and organization settings. The August 6 Chat update is not a migration notice for those surfaces.
- Before scaling a real workflow, record the account, data scope, tool permissions, budget, human review, and rollback path.
Why it matters
When one model name appears in Chat, the API, Work, and Codex, the common mistake is treating an update for one entry point as a platform-wide change. The August 6 announcement creates a clear boundary: Chat Sol behavior and free-user Luna access change, while Work and Codex do not. Separating entry point, plan, and task avoids incorrect cost estimates, permission assumptions, and workflow migrations.
Impact for ordinary AI users
Ordinary users can use the Chat Sol slider and Luna Think access to organize everyday questions, research, writing, and planning, but should still check sources and key conclusions. People using the API or a team workspace should retain their current pricing, permissions, logging, and approval checks until the relevant product documentation or account setting actually changes.
Related tools and tutorials
ENHE's GPT-5.6 news page, ChatGPT Work explainer, safe-testing tutorial, AI software, account-services, and skill-learning sections help users verify Chat choices separately from API, workspace, and permission governance.
GPT-5.6 and ChatGPT Work news；ChatGPT Work explainer；Safe GPT-5.6 testing tutorial；AI software tools；AI account services；AI skill tutorials
FAQ
Does the August 6 update change GPT-5.6 Sol in Work or Codex?
No. OpenAI explicitly says the optimized version in this release is only for the ChatGPT Chat experience; the Sol model used by Work and Codex is not changing.
Can every free user use Luna without limits immediately?
The announcement describes a gradual rollout, and file uploads, images, and other tools still have limits. Check the models and allowance actually shown in the account.
Is the Chat thought slider the same as API Fast mode?
No. The slider controls thought level in Chat, while Fast mode is an API processing mode. Check their own official documentation and pricing separately.
Source links
- OpenAI: Improving GPT-5.6 Sol in ChatGPT—and expanding access to GPT-5.6 Luna for free users (2026-08-06)
- OpenAI: Advancing the price-performance frontier with GPT-5.6 (2026-07-30)
- OpenAI API docs: GPT-5.6 Sol model pricing
- OpenAI API docs: GPT-5.6 Terra model pricing
- OpenAI API docs: GPT-5.6 Luna model pricing
- OpenAI: GPT-5.6 frontier intelligence that scales with your ambition (2026-07-09)
What this means for everyday users
ENHE users should add product entry point as the first column of a Sol, Terra, and Luna selection sheet. Price, speed, and permission comparisons matter only after the entry point, plan, and account setting are confirmed.
Related reading
GitHub Copilot Metrics Add OpenCode and Other Clients: Requests Are Not Prompts
GitHub added totals_by_client to the Copilot usage metrics API on October 23, 2026. Enterprise and organization reports can now show model traffic from OpenCode, Claude Code, Codex, Zed, Copilot CLI, GitHub apps, cloud agents, code review, VS Code, JetBrains, and other clients. This article helps administrators build reliable one-day and 28-day reports without confusing model calls with user prompts. It explains request, session, token, model, and selection-mode fields; separates client traffic from agent-app jobs; and adds checks for unknown identifiers, empty arrays, permissions, and coverage. The result is a governance trend report, not an exact invoice or individual productivity score.
When Should an AI Agent Use a Local Small Model or the Cloud? A Hybrid Routing Checklist
AWS published an Adaptive Agentic Intelligence Framework guide using Strands Agents on October 21, 2026. The reference routes routine status checks and local vision work to small models through Ollama, while complex analysis goes to Amazon Bedrock. This durable guide helps teams decide when an AI agent should stay local and when it should use a cloud model. It classifies tasks, marks data that may leave the device, establishes local and cloud quality baselines, defines timeouts and fallbacks, applies one safety policy across both paths, and measures actual routing before estimating cost. The example can run on an 8 GB Raspberry Pi, but that hardware detail is not evidence that every workload belongs on a small local model.
How to Validate Amazon Quick Before Health-Data Use: HIPAA Eligible Does Not Mean Automatically Compliant
AWS published an Amazon Quick deployment guide for HIPAA-regulated environments on October 22, 2026. Its central distinction is durable: HIPAA eligible means the service can be used to process protected health information under the right agreement and configuration; it does not make an entire environment automatically compliant. This guide is for healthcare organizations, business associates, and technical owners working with legal, compliance, and security reviewers. It turns the source into an acceptance checklist covering the business associate addendum, data classification, irreversible key and identity choices, ACL-aware knowledge bases, least-privilege and read-only connectors, masked audit logs, adversarial access tests, and staged expansion from non-PHI work. It is operational guidance, not individualized legal advice or a substitute for professional review.
How to Validate AI-Agent Runtime Safety: A Four-Layer OpenShell Evidence Checklist
NVIDIA launched the OpenShell Reference Architecture on October 21, 2026 for building, containing, observing, and enforcing safer agents across enterprise infrastructure and edge systems. This durable guide turns that architecture into a four-layer acceptance checklist rather than a product summary. For one low-risk agent task, teams verify build provenance, identity and tool boundaries, file and network isolation, observable action logs, policy denials, human approval, and rollback. Each layer requires evidence and a failure response. The goal is not to claim that one runtime makes an agent safe. It is to decide which actions can proceed automatically, which must stop for review, and how operators can reconstruct what happened after a failed or unexpected action.
Notion AI Changes Credits and Bring-Your-Own AI: Audit Usage Before November 2
Notion announced updated AI credits and agent capabilities on October 19, 2026. The system is live for new customers, while existing customers move on November 2. Business and Enterprise seats receive monthly Standard and Select credits, personal workspaces can connect eligible ChatGPT subscriptions, and enterprise bring-your-own-model access remains a private alpha. This article turns the announcement into a practical pre-migration audit. It separates features that are available now from those that need an administrator or remain in testing, then gives users three representative tasks for measuring credit use, completion quality, and fallback behavior. Vendor performance and cost claims are clearly treated as claims, not independent ENHE AI test results.
How to Use GitHub Package Firewall: An npm Safety Checklist for Coding Agents
GitHub introduced Package Firewall in public preview on October 20, 2026 for GitHub Enterprise Cloud customers, including data-resident environments. The firewall sits between coding agents, CI runners, or internal registries and upstream package repositories. It evaluates package metadata and downloads against enterprise policies such as cooldown periods, GitHub Advisory Database checks, and supply-chain signals including attestation downgrades. The preview is free, but general availability is expected to use metered pricing similar to Actions, and npm is the only supported ecosystem today. This durable guide provides a rollout checklist for endpoint routing, a read-only build, blocked-package exceptions, audit evidence, false-positive review, and future budget preparation.
Summary
The August 6 update makes Sol in ChatGPT more focused and expands the path to Luna for free users, but it does not erase product-entry-point boundaries. Confirm whether you are using Chat, the API, Work, or Codex before comparing plan, model, price, and permissions for Sol, Terra, and Luna.
Sources
OpenAI: Improving GPT-5.6 Sol in ChatGPT—and expanding access to GPT-5.6 Luna for free users (2026-08-06)
OpenAI: Advancing the price-performance frontier with GPT-5.6 (2026-07-30)
OpenAI API docs: GPT-5.6 Sol model pricing
OpenAI API docs: GPT-5.6 Terra model pricing
OpenAI API docs: GPT-5.6 Luna model pricing
OpenAI: GPT-5.6 frontier intelligence that scales with your ambition (2026-07-09)