Running Codex in full-auto mode lets a session move from prompt to edits and local commands without stopping for every routine action, which is useful for contained repository tasks such as fixing a test, updating docs, or applying a small refactor.
The current Codex CLI exposes --full-auto as a startup preset for the top-level codex command. Current local help shows that the interactive flag expands to --ask-for-approval on-request plus --sandbox workspace-write, so Codex can edit files and run commands inside the current repository while still stopping when work reaches outside that boundary.
Keep the working directory narrow before enabling the preset, because workspace-write can change any file under the chosen root. First-time runs in a directory can stop at a trust prompt, and codex exec –full-auto follows a slightly different path because exec already runs as a non-interactive command.
Related: approval-policy-set
Related: How to set Codex sandbox mode
$ codex --help
##### snipped #####
--full-auto
Convenience alias for low-friction sandboxed automatic execution (-a on-request, --sandbox
workspace-write)
##### snipped #####
The top-level codex command currently treats --full-auto as a shorthand for interactive on-request approval plus the workspace-write sandbox.
$ cd ~/projects/example-app
Keep the root as narrow as practical, because workspace-write allows file edits anywhere under the current working directory.
$ codex --full-auto
If the directory has not been trusted yet, confirm the trust prompt before the session opens.
> Update the failing test and run the matching test file.
Passing the first task on the launch command is also valid when the work is already known, for example codex --full-auto "Update the failing test and run the matching test file.".
/permissions
The current interactive picker exposes Auto, Read-only, and Full Access even though the startup flag is still named --full-auto.
$ git status --short
Codex can make multiple file edits in one run, so inspect the changed paths and diff before keeping the results.
/exit
Related: How to resume the last Codex session