Answer: The prerequisites are: store your OpenAI key as a GitHub secret (for example `OPENAI_API_KEY`) and reference it in the workflow; run the job on a Linux or macOS runner (for Windows, set `safety-strategy: unsafe`); check out your code before invoking the action so Codex can read the repository contents; and decide which prompts you want to run, providing inline text via `prompt` or pointing to a file committed in the repo with `prompt-file`. Status: Confirmed Entry: tool/codex/integrations/github-action-prerequisites Revision: 1 Digest: sha256:4916c8f9d676ae45 (changes whenever the content changes) Timeline: Created: 2026-11-15T13:47:31Z Last changed: 2026-11-15T13:47:31Z 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 OpenAI key storage | Store your OpenAI key as a GitHub secret (for example `OPENAI_API_KEY`) and reference it in the workflow. | [1] | 2026-11-20 Runner OS | Run the job on a Linux or macOS runner. | [1] | 2026-11-20 Windows setting | For Windows, set `safety-strategy: unsafe`. | [1] | 2026-11-20 Code checkout | Check out your code before invoking the action so Codex can read the repository contents. | [1] | 2026-11-20 Prompt options | You can provide inline text via `prompt` or point to a file committed in the repo with `prompt-file`. | [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: "Store your OpenAI key as a GitHub secret (for example `OPENAI_API_KEY`) and reference it in the workflow." (Supports: OpenAI key storage) Quote: "Run the job on a Linux or macOS runner." (Supports: Runner OS) Quote: "For Windows, set `safety-strategy: unsafe`." (Supports: Windows setting) Quote: "Check out your code before invoking the action so Codex can read the repository contents." (Supports: Code checkout) Quote: "You can provide inline text via `prompt` or point to a file committed in the repo with `prompt-file`." (Supports: Prompt options) 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-15T13:47:31Z, 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 "Prerequisites"). Related: https://latestn.com/tool/codex/integrations/gitlab-ci-requirements What are the requirements to run Codex Security in GitLab CI/CD? https://latestn.com/tool/codex/integrations/gitlab-code-review-prerequisites What do I need before setting up Codex code review for GitLab? https://latestn.com/tool/codex/integrations/mcp-server-removal-alternative What should I use instead of the removed Codex MCP server? https://latestn.com/tool/codex/integrations/export-servicenow How do I export Codex Security findings for ServiceNow? https://latestn.com/tool/codex/integrations/gateway-required-endpoints What endpoints must a gateway support for Codex to work with the Responses API? https://latestn.com/tool/codex/integrations/gateway-streaming-requirements How should a gateway handle streaming for Codex? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-15T13:47:31Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/integrations/github-action-prerequisites/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/github-action-prerequisites POST: https://latestn.com/dispute/tool/codex/integrations/github-action-prerequisites with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/integrations/github-action-prerequisites?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What are the prerequisites for using the Codex GitHub Action in a workflow? Revision 1, last verified 2026-11-20T13:39:51Z. https://latestn.com/tool/codex/integrations/github-action-prerequisites (accessed 2026-11-21T09:50:34Z). @misc{LatestN_tool_codex_integrations_github_action_prerequisites_r1, title = {What are the prerequisites for using the Codex GitHub Action in a workflow?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/integrations/github-action-prerequisites}}, note = {Revision 1; digest sha256:4916c8f9d676ae45; last verified 2026-11-20T13:39:51Z; accessed 2026-11-21T09:50:34Z} } 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/github-action-prerequisites