Fast mode shows up even if admin disabled it
Open 💬 2 comments Opened Apr 24, 2026 by amit-mittal
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.422.20832 (2025)
What subscription do you have?
Enterprise
What platform is your computer?
Darwin arm64
What issue are you seeing?
Even after setting below policy through cloud-managed requirements.toml, I am able to toggle /fast from Codex app. I don't know if codex is working in "fast" mode or "standard" mode and where the bug is.
[features]
fast_mode = falseWhat steps can reproduce the bug?
- Add the above policy following https://developers.openai.com/codex/enterprise/admin-setup#step-3-configure-codex-local-requirements
- Restart
codex-cli. You won't see a way to toggle/fastanymore. - Restart Codex app.
/fastmode can still be toggled and the session doesn't show any errors during prompts. - VSCode extension has a similar experience as Codex app
What is the expected behavior?
As an admin, we want to disable fast mode for our engineers and be 100% sure that it is indeed disabled. I don't know if it is a UI bug or backend bug or both.
Additional information
At the very least, please tell if there is a way to verify if the fast mode of using token is disabled and it won't work. If there is some other way to correctly disable it, let us know that too.
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Having the same issue, I sent an email to them as well.
I do have a newer version of the app, but that seems irrevelant.
@amit-mittal, by any chance, if you update your enterprise policy with something like
allowed_sandbox_modes = ["read-only"]And restart Codex, does that work for you? I found that this is not working for us; only if we manually delete a cache file and restart the machine does it finally work