Dots
Require Dot approval before Codex or token-heavy work
A builder set a top Dot rule blocking Codex and other token-consuming tasks unless approved; web browsing still ran freely, but a local battery check still spawned Sol 6.1 Codex without asking.
What changed
Builder Yūgen (@izayoiyugen) set a top Dot rule roughly: no Codex or other token-consuming tasks without approval. After that, the Dot asked for approval on almost everything except web browsing and status checks. When it accessed the local machine to check battery, it still started a Codex thread on Sol 6.1 at high effort without asking.
Who is affected
People who want their primary Dot to stay cheap and only spend Codex quota when they say yes.
What to do now
Add an explicit top rule that Codex and other token-heavy work need approval. After saving it, spot-check local-machine actions: some status checks may still spawn Codex. Tighten the rule or deny those threads if that happens.
What is not confirmed
This is one builder's report on X, not an OpenAI changelog. Whether Sol 6.1 XHigh was required for a battery check, and whether every Dot build honors the same top-rule wording, is not confirmed in official docs.
Sources
- ReportYūgen on X
Get updates like this every morning
- ② Card on Stripe
- ③ 7 days free
Then $2/month · cancel anytime in one click