Skip to content

Conversation

pakrym-oai
Copy link
Collaborator

More/better docs.

Copy link
Collaborator

@bolinfest bolinfest left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just want to be sure that


In non-interactive mode, Codex does not ask for command or edit approvals. By default it runs in `read-only` mode, so it cannot edit files or run commands that require network access.

Use `codex exec --full-auto` to allow file edits. Use `codex exec --sandbox danger-full-access` to allow edits and networked commands.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like we have been moving away from the --full-auto name, though I admit it is succinct. No good suggestions here.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should also mention --skip-git-repo-check somewhere?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's below

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For the lack of better alternative let's stick to full-auto although I agree it's confusing.

docs/exec.md Outdated
{"project_name":"Codex CLI","programming_languages":["Rust","TypeScript","Shell"]}
```

Combine `--output-schema` with `--output-last-message <FILE>` to save the JSON output to a file.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we make -o or -O an alias for --output-last-message? Or just pipe the contents to stdout when --json is not specified?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll start with the latter.

@pakrym-oai pakrym-oai force-pushed the pakrym/add-a-separate-exec-doc branch from 3162218 to 6c6c1f8 Compare October 2, 2025 20:15
@pakrym-oai pakrym-oai closed this Oct 2, 2025
@pakrym-oai pakrym-oai reopened this Oct 2, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Oct 2, 2025
@pakrym-oai pakrym-oai merged commit b93cc0f into main Oct 2, 2025
18 checks passed
@pakrym-oai pakrym-oai deleted the pakrym/add-a-separate-exec-doc branch October 2, 2025 20:33
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants