How to run Codex in full-auto mode

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.

Steps to run Codex in full-auto mode:

Review how the installed CLI maps the --full-auto flag.

$ 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.

Change to the repository root that should act as the writable workspace.
```
$ cd ~/projects/example-app
```
Keep the root as narrow as practical, because workspace-write allows file edits anywhere under the current working directory.
Start Codex with the full-auto preset.
```
$ codex --full-auto
```
If the directory has not been trusted yet, confirm the trust prompt before the session opens.

Related: How to fix Codex trusted directory error
Enter the first task after 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.".
Open the permissions picker when the task needs a different access level mid-session.
```
/permissions
```
The current interactive picker exposes Auto, Read-only, and Full Access even though the startup flag is still named --full-auto.
Check the repository state before committing or continuing with a larger task.
```
$ git status --short
```
Codex can make multiple file edits in one run, so inspect the changed paths and diff before keeping the results.
Exit the session when the task is complete.
```
/exit
```
Related: How to resume the last Codex session

Author: Mohd Shakir Zakaria
Mohd Shakir Zakaria is a cloud architect with deep roots in software development and open-source advocacy. Certified in AWS, Red Hat, VMware, ITIL, and Linux, he specializes in designing and managing robust cloud and on-premises infrastructures.