Full access not available when Sol Ultra is selected

Resolved 💬 3 comments Opened Jul 16, 2026 by SandboChang Closed Jul 18, 2026

What version of the IDE extension are you using?

26.707.91948

What subscription do you have?

Pro20x

Which IDE are you using?

VSCode

What platform is your computer?

_No response_

What issue are you seeing?

Full access and Ultra mode are now mutually exclusive.

What steps can reproduce the bug?

Select Ultra/Full access when Full access/Ultra has been selected. It throws an exception to toggle either Ultra back to other effort, or access back to not Full access. Ultra+Full access cannot be used together.

What is the expected behavior?

Both of them can coexist.

Additional information

This is getting ridiculous. I need Full access to use my GPU for development, and then often I switch to Ultra for a short analysis and debug session. Now it breaks my workflow because someone does not know how to run their setup safely.

A warning should have been all that needs to be done. Users should be fully responsible for their action. It is completely ridiculous now I lost access to a critical function because someone does not know how to properly sandbox their systems.

This should be reverted asap. Staying on older version before this has been fixed.

View original on GitHub ↗

3 Comments

pharmatorium · 1 month ago

I can reproduce this in the ChatGPT/Codex desktop app 26.707.91948 (build 5440) on macOS 26.5.2, using 5.6 Sol.

The UI allows Full access with reasoning set to Very high. As soon as reasoning is switched to Ultra, the permission menu disables Full access and shows:

Unavailable with Ultra reasoning

The task is then effectively downgraded to “Approve for me”.

This coupling breaks the core workflow I use Codex for: long-running, unattended implementation and multi-agent tasks that need to edit files, use the network, run deployments, and continue autonomously for 30–60 minutes or longer. With approval prompts enabled, such a task simply stalls until I return. Reducing reasoning from Ultra to Very high is not a reasonable workaround because autonomy and reasoning quality are independent requirements.

I deliberately select Full access after reading and accepting the prominent risk warning. The product should not silently remove that choice only because Ultra reasoning is selected.

Expected behavior

  • Restore opt-in Full access for Sol Ultra.
  • Keep the existing strong warning and explicit confirmation.
  • If additional protection is considered necessary, add a second confirmation or a task-scoped opt-in instead of a hard prohibition.
  • Preserve the selected access level when switching between Very high and Ultra.

For power users, autonomous work with high-quality output is the primary value of Codex. This regression is severe enough that I am considering rolling back the update and cancelling my subscription if it remains. I have three screenshots documenting the Very high/Full access state, the Ultra fallback, and the disabled “Unavailable with Ultra reasoning” option.

SandboChang · 1 month ago

This has now been reverted as of version 26.715.31925.

hzw190 · 1 month ago

不错。