Answer: You configure `codex exec` options in the Codex GitHub Action by setting action inputs that map to `codex exec` options, including `prompt` or `prompt-file`, `codex-args`, `model` and `effort`, `sandbox`, `output-file`, `codex-version`, and `codex-home`. Status: Confirmed Entry: tool/codex/integrations/configure-codex-exec Revision: 1 Digest: sha256:28e443274bddaa22 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:51:30Z Last changed: 2026-11-13T03:51:30Z Last verified: 2026-11-20T13:39:51Z Next check: 2026-11-21T13:39:51Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of prompt inputs | prompt` or `prompt-file | [1] | 2026-11-20 codex-args | codex-args | [1] | 2026-11-20 model and effort | model` and `effort | [1] | 2026-11-20 sandbox modes | workspace-write`, `read-only`, `danger-full-access | [1] | 2026-11-20 output-file | output-file | [1] | 2026-11-20 codex-version | codex-version | [1] | 2026-11-20 codex-home | codex-home | [1] | 2026-11-20 Sources: [1] OpenAI. "Codex GitHub Action". https://learn.chatgpt.com/docs/github-action.md Role: primary. Accessed: 2026-11-20T13:39:51Z Quote: "`prompt` or `prompt-file` (choose one): Inline instructions or a repository path to Markdown or text with your task." (Supports: prompt inputs) Quote: "`codex-args`: Extra CLI flags. Provide a JSON array (for example `["--ephemeral"]`) or a shell string (`--profile ci`) to configure sessions, profiles, or MCP settings." (Supports: codex-args) Quote: "`model` and `effort`: Pick the Codex agent configuration you want; leave empty for defaults." (Supports: model and effort) Quote: "`sandbox`: Match the sandbox mode (`workspace-write`, `read-only`, `danger-full-access`) to the permissions Codex needs during the run." (Supports: sandbox modes) Quote: "`output-file`: Save the final Codex message to disk so later steps can upload or diff it." (Supports: output-file) Quote: "`codex-version`: Pin a specific CLI release. Leave blank to use the latest published version." (Supports: codex-version) Quote: "`codex-home`: Point to a shared Codex home directory if you want to reuse configuration files or MCP setups across steps." (Supports: codex-home) Snapshot SHA-256: 3c3a244ef87fffb064114e388f4c7827b3ddc55b712f5aec50f2719a3cf1bc6a (captured 2026-11-13T03:51:29Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:51:30Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:39:51Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:39:51Z Last attempt: 2026-11-20T13:39:51Z Notes and limitations: Extracted automatically from a single official source (section "Configure `codex exec`"). Related: https://latestn.com/tool/codex/integrations/configure-mcp-tool-hook How do I configure an MCP tool hook in Codex? https://latestn.com/tool/codex/integrations/connect-cli-to-remote-app-server How do I connect the Codex CLI terminal UI to a remote Codex app-server? https://latestn.com/tool/codex/integrations/connect-codex-mcp-config-toml How do I connect Codex to an MCP server using config.toml? https://latestn.com/tool/codex/integrations/ci-api-key-setup How do I set up the API key for Codex Security scans in CI? https://latestn.com/tool/codex/integrations/ci-integration-options Which CI integrations does Codex Security support? https://latestn.com/tool/codex/integrations/codex-environment-repo-selection How does Codex choose which environment and repo to use for a Linear issue? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:51:30Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/integrations/configure-codex-exec/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/codex/integrations/configure-codex-exec POST: https://latestn.com/dispute/tool/codex/integrations/configure-codex-exec with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/integrations/configure-codex-exec?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I configure `codex exec` options in the Codex GitHub Action? Revision 1, last verified 2026-11-20T13:39:51Z. https://latestn.com/tool/codex/integrations/configure-codex-exec (accessed 2026-11-21T09:52:45Z). @misc{LatestN_tool_codex_integrations_configure_codex_exec_r1, title = {How do I configure `codex exec` options in the Codex GitHub Action?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/integrations/configure-codex-exec}}, note = {Revision 1; digest sha256:28e443274bddaa22; last verified 2026-11-20T13:39:51Z; accessed 2026-11-21T09:52:45Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/codex/integrations/configure-codex-exec