GPT-6.1 Sol reasoning levels determine how much work the same AI model puts into an answer. Think of them as choosing between a quick fix, a careful second opinion, and a full project team—not buying six different AIs. Here is a plain-English guide to Light, Medium, High, Extra High, Max, and Ultra, with six side-by-side examples and real websites you can open.

Updated October 19, 2026 · For ChatGPT Work, Codex, and developers · Examples below are guidance, not promised outputs.

GPT-6.1 Sol reasoning levels from Light to UltraSix steps: Light for quick edits, Medium for everyday work, High for debugging, Extra High for deeper checks, Max for difficult single tasks, and Ultra for parallel agents. GPT-6.1 SOL • REASONING GUIDE Pick the depth the task deserves 1LIGHTQuick edits 2MEDIUMEveryday work 3HIGHTough bugs 4EXTRA HIGHDeep checks 5MAXHardest single job 6ULTRAParallel agents These are settings for the same model, not six separate AI models. Ultra is a Work/Codex orchestration option.
The same GPT-6.1 Sol model, with increasing reasoning depth and (at Ultra) optional parallel-agent orchestration. Graphic: LogicWeb.

The quick answer: which GPT-6.1 Sol level should you use?

Start with Medium. Use Light for simple, reversible edits; High for difficult debugging and multi-step tasks; Extra High for a carefully checked deliverable; Max when a single problem deserves the deepest analysis; and Ultra when a big task can actually be divided among multiple agents. More reasoning can cost more time and tokens, but it does not guarantee a better outcome.

GPT-6.1 Sol levels explained

Level Best for What changes Simple example
Light (Low) Quick, narrow edits Fastest sensible starting point for obvious tasks One-page copy edits, formatting, extracting key details
Medium The everyday default Good balance of speed and reasoning Normal WordPress updates, code changes, planning
High Multi-step problems More depth for ambiguous bugs and trade-offs Checkout failures, tricky automation, app logic
Extra High (xhigh) Careful, complex deliverables More time for checking assumptions and edge cases Production review, detailed research, deep SEO audits
Max Hardest single-agent tasks Most intensive individual reasoning setting Architecture decisions, hard migrations, difficult debugging
Ultra Parallelizable project work Can enlist subagents for separable workstreams App + tests + documentation + research in parallel

Important naming detail: The OpenAI API exposes low, medium (default), high, xhigh, and max. Ultra is a Work/Codex option involving possible subagent delegation, not the API value ultra. Also, Ultrafast is a separate speed/service tier, not a deeper reasoning level. Availability varies with plan, client, and workspace settings. GPT-6.1 Sol is available in Work and Codex rather than regular Chat as of this update.

Max versus Ultra workflow diagramMax shows one agent exploring a complex task deeply. Ultra shows a coordinator delegating research, implementation, and testing to parallel subagents before integration. MAX vs. ULTRA: depth is not delegation MAXOne agent, deeper single-task reasoning AnalyzeImplementVerify ULTRAA coordinator may split independent workstreams Coordinator ResearchBuildTest Integrate results Delegation is workload-dependent; choosing Ultra does not guarantee agents will be spawned.
Max works a problem deeply; Ultra can coordinate parallel subtasks. Ultra does not guarantee delegation in every run.

Six side-by-side examples: same task, different reasoning levels

The tables describe the kind of work you should request or expect the agent to attempt at each setting—not literal transcripts, standardized performance scores, or a guarantee that Ultra will start helpers. You still need to review and test results.

On phones: Swipe left within a comparison table to see all six levels. The whole page stays in place.

1. Update a WordPress landing page

Prompt: “Make our WordPress hosting page clearer and easier to use.”

Light Medium High Extra High Max Ultra
Tighten the headline and CTA. Rewrite the sections and mobile CTA flow. Check navigation, responsive layout, and accessibility issues. Audit conversion friction, performance, headings, and regressions. Plan and verify a larger refactor with test coverage. Split content, front-end, SEO, and QA across parallel workstreams.

2. Fix a broken checkout

Prompt: “Customers say discount codes sometimes double-apply.”

Light Medium High Extra High Max Ultra
Locate the coupon calculation function. Reproduce the bug and patch the common path. Trace cart states and add regression tests. Investigate race conditions, refunds, and edge cases. Systematically review pricing invariants and failure recovery. Have agents investigate checkout, payments, and tests separately.

3. Turn data into a business answer

Prompt: “Why did hosting trial conversions fall this month?”

Light Medium High Extra High Max Ultra
Calculate the conversion-rate change. Segment by campaign and device. Check funnel steps, cohort shifts, and missing data. Test competing hypotheses and quantify uncertainty. Stress-test conclusions before an executive decision. Parallelize acquisition, funnel analytics, and instrumentation reviews.

4. Create an SEO article

Prompt: “Write a beginner guide to website uptime monitoring.”

Light Medium High Extra High Max Ultra
Draft a clean outline and introduction. Write a complete guide with examples and FAQ. Check intent, internal links, accuracy, and useful examples. Map topical gaps, sources, snippets, and editorial revisions. Resolve complex claims with a thorough source-verification pass. Divide research, editing, illustration, and fact-checking if substantial.

5. Build an interactive web app

Prompt: “Create a customer-facing DNS troubleshooting dashboard.”

Light Medium High Extra High Max Ultra
Make a visual demo with mock data. Add working forms and basic validation. Build typed components and tests for common failures. Cover mobile states, loading, security, and error recovery. Review architecture and robustness for a maintainable app. Split UI, API, validation, and test suites across agents.

6. Review a risky infrastructure change

Prompt: “Plan migration from one hosting platform to another.”

Light Medium High Extra High Max Ultra
Make a high-level checklist. Outline tasks, owners, and rollback. Sequence dependencies and failure tests. Assess downtime, DNS TTLs, backups, and recovery drills. Challenge assumptions and produce a rehearsable cutover plan. Coordinate separate infra, app, security, and test-track plans.

Pattern: Light and Medium are for getting something useful on the page. High and Extra High are for making it dependable. Max is for extremely difficult individual work. Ultra becomes useful when independent parts can run in parallel. This is a task-design recommendation, not a measured level-by-level output benchmark.

Choosing GPT-6.1 Sol reasoning effort with a simple decision pathStart at Medium. For small, reversible work go Light. For multistep problems choose High. For difficult reviews use Extra High or Max. For independent parallel work use Ultra. A simple rule: start in the middle MEDIUMDefault LIGHTIf quick & reversible HIGHIf tricky & multistep XHIGH / MAXIf costly to get wrong ULTRAIf parallelizable Move up only when acceptance criteria, risk, or real workload justify more reasoning.
Practical decision path: begin at the default; raise effort only when the job justifies it.

Real GPT-6.1 Sol websites you can try right now

These are real, publicly accessible builds, not mock screenshots. In an October 4, 2026 independent test, Spectrum AI Labs gave Codex the same website prompt at six settings, then published the resulting pages. The author says the pages were rebuilt to run on its own domain; they are experiments, not official OpenAI websites.

Effort What the reviewer reported Open the live site
Light One-page showcase with a particle sculpture Open Light build ↗
Medium Artwork, four playgrounds, and a brief builder Open Medium build ↗
High Particle sculpture, poster designer, and CSV analysis Open High build ↗
Extra High Mint-and-ivory design with 12 capability areas Open Extra High build ↗
Max Interactive 3D sculpture and studio tools Open Max build ↗
Ultra Morphing sculpture, code examples, and source download Open Ultra build ↗

3D Colosseum: compare graphics and engineering

The same tester also published interactive Three.js Colosseum builds. Try Light, Extra High, Max, and Ultra. On a slower laptop, 3D pages may take a few seconds to load.

What the test actually found: Max ranked highest in one blind AI review of code quality for both tasks; Ultra did not start any helper agents in those runs. This is a limited experiment—two prompts, one run at each setting, and one AI reviewer—not proof that Max always wins. It is a useful reminder that an elaborate-looking site is not necessarily maintainable code.

Website and app showcases shared on X

Here are two relevant X posts collected by Promptslove’s September 2026 roundup. X restricts some automated access, so the descriptions below are attributed summaries from that report, not independently verified recreations of the posts.

From @viktoroddy: luxury car-rental website challenge

A side-by-side video reportedly compares GPT-6.1 Sol and another model building a cinematic car-rental website from the same prompt. View the original for the visuals, and judge the result yourself.

View the original post on X ↗

https://x.com/viktoroddy/status/2105226806492283286

From @aniketjart: browser-based 3D game comparison

According to the same roundup, this post links to a playable fantasy/sci-fi Three.js project and compares results from an identical brief.

See the project and post on X ↗

For developers: one model, multiple effort settings

Here is a basic Responses API example using the default-to-practical medium setting. For a more challenging single-agent task, change medium to high, xhigh, or max. Do not set API reasoning.effort to ultra.

const response = await client.responses.create({
  model: "gpt-6.1-sol",
  reasoning: { effort: "medium" },
  input: "Audit this function and suggest a tested fix."
});

At standard API pricing, OpenAI lists $2 per million input tokens, $0.10 per million cached input tokens, and $10 per million output tokens for GPT-6.1 Sol. These are token rates, not a promise that every request or effort level costs the same total. Extra reasoning, tool use, and longer runs can increase consumption. For standard ChatGPT chats, the model choice and thinking controls are different from Work and Codex.

A practical way to choose without wasting time

  1. Define success: Say what the result must do, what must not change, and how to verify it.
  2. Start at Medium: Try Light instead when the task is tiny, obvious, and easy to undo.
  3. Escalate for a reason: Use High for unclear failures; Extra High when verification or edge cases matter; Max for the hardest single-agent analysis.
  4. Use Ultra only if work splits: Parallel review, build, tests, and documentation are a good fit; one bug fix usually is not.
  5. Check the work: Run tests, review permissions, and keep human approval for production changes, security, legal, or financial decisions.

Frequently asked questions

Is GPT-6.1 Sol Ultra a different model?

No. It is a higher-level Work/Codex execution option for GPT-6.1 Sol that may delegate subtasks to agents. It is not another separately named base model.

Is Max or Ultra smarter?

Max focuses effort on a single task; Ultra can coordinate workstreams. Neither wins every test. In one published two-task comparison, Max scored highest in the author’s blind code review, while Ultra never spawned helpers.

What is the best GPT-6.1 Sol setting for coding?

Use Medium for routine changes, High for real debugging, Extra High for careful production review, and Max for the hardest isolated problems. Use Ultra for a codebase project that divides naturally among agents.

Does Light cost less than Max?

Often in total use, because shorter reasoning usually consumes fewer tokens and less time. The standard API price per token is not itself a separate rate card for each effort level.

Is Ultra the same as Ultrafast?

No. Ultra is a reasoning/orchestration setting in supported Work/Codex clients; Ultrafast is a separate speed tier with availability that depends on plan and product.

Can I select GPT-6.1 Sol in ordinary ChatGPT chat?

As of October 19, 2026, OpenAI lists it for ChatGPT Work and Codex, not ordinary Chat. Eligibility and controls vary by plan and account.

Bottom line

Use the lowest reasoning setting that can reliably finish and verify the job. Medium handles most everyday work; High and Extra High are a sensible upgrade for complexity; Max is for depth; Ultra is for genuine multi-track projects. The live sites above show why there is no single perfect choice: appearance, code maintainability, speed, and delegation are different measures of success.

For more context, see LogicWeb’s GPT-6.1 Sol vs. GPT-6 Astra comparison and its GPT-6 reasoning-level primer.

Sources and methodology

Research checked October 19, 2026. All six scenario grids are editorial illustrations of appropriate scope, not transcripts of actual runs. Real-world build claims are attributed to their creators and remain subject to later changes.