Repository navigation
[Bug][Mobile]: Codex is sometimes launched without YOLO mode #10330
Description
Summary
The mobile app sometimes launches Codex without the configured YOLO/approval-bypass mode, even though YOLO mode is selected.
Environment
- Client: Orca mobile app
- Agent: OpenAI Codex
- Orca version: unknown
- Mobile OS/device: unknown
- Codex CLI version: unknown
Steps to reproduce
- Select/configure Codex with YOLO mode in the mobile app.
- Launch Codex from a workspace.
- Inspect the resulting terminal command or observe the session behavior.
- Repeat the launch; the issue is intermittent.
Expected behavior
Every launch made with YOLO mode enabled should start Codex with the appropriate approval-bypass/YOLO arguments, consistently.
Actual behavior
On some launches, Orca starts plain codex instead of the YOLO-configured command. The session then behaves as a normal approval-requesting Codex session.
Impact
The launch mode is unreliable and can cause an autonomous session to stop unexpectedly for manual approval. It also makes it difficult to know whether a session has the intended safety/permission configuration.
Please let me know which mobile logs or launch diagnostics would help identify why the YOLO arguments are occasionally dropped.
Made with Orca 🐋
Activity
J-TN commentedon Sep 7, 2026
I also encountered a related symptom on desktop macOS: a newly created Codex Chat session did not apply YOLO from Settings, while a session initiated from a terminal appeared to work. I noticed it after starting to use GPT-6 Astra, but the reproduction below happens before any model turn.
Investigation with
codex-cli 0.153.4found thatcodex --dangerously-bypass-approvals-and-sandbox app-serveraccepts the flag but opens a thread withapprovalPolicy: "on-request"and areadOnlysandbox. Passing-c approval_policy="never" -c sandbox_mode="danger-full-access"instead producesapprovalPolicy: "never"anddangerFullAccess.The proposed fix translates Settings permission flags into app-server configuration for new Codex Chats. The final diff changes only the argument parser and its tests, covering YOLO disabled, restricted settings and Windows/POSIX parsing. Saved-session launch resolution is unchanged.
PR: #19206
Code review also shows that ordinary mobile Codex Chat creation uses the same host-side launcher, so that path should benefit once the host is updated. Prompted/quick-command launches and legacy/fallback terminal sessions use a separate terminal command builder that this patch does not change.
A desktop comparison reproduced a blocked outside-workspace write on the baseline and a successful write without escalation in a fresh Chat on the initial fix revision. The probe files were independently verified. Reopening the baseline conversation still retained restricted permissions, so existing-session permission restoration is outside this PR. The final narrowed revision retains the tested parser conversion; the positive YOLO comparison has not been repeated on that revision. A subsequent contributor-confirmed new Chat with restricted arguments on the narrowed revision blocked the write, and
restricted.txtwas independently confirmed absent. The restricted Chat did not show a model label; that separate UI observation is recorded in the PR without claiming a diagnosis or fix.This confirms a new desktop Chat launch problem; it does not establish a fix for the original intermittent mobile plain-
codexterminal launch. Mobile verification remains outstanding. PR #19206 is now ready for review; the documented unrelated full-check failures remain open for maintainer/CI assessment.nwparker commentedon Oct 24, 2026
Thanks for reporting! #31315 stores each agent's permission (e.g. YOLO) in one place so terminals and new chats both read it. Could you check on the latest build? Please reply if Codex still launches without YOLO.