codex-action
Open-source command-line tool. Agents run on your computer or on your own server.
Product websitegithub.com Compare with others Missing or wrong data?
- Desktop app
- No
- Browser
- No
- Phone
- No
- Command line
- Yes
- Agents
- Codex
- Your subscription
- No
- Agents run
- On your computer and on your own server
- Laptop closed
- Keeps going
- Isolation
- No
- Parallel agents
- Yes
- Scheduled runs
- Yes
- Coordinator agent
- No
- Built-in issues
- No
- Pull requests
- No
- Review screen
- No
- Team
- No
- Self-hosting
- Not listed
- Licence
- Apache-2.0
- Price from
- Free
- How it charges
- No paid plan and bring your own key
- Paid plans from
- No paid plan
Receipts
- Checked
- · oldest answer 2026-11-08
- Findings
- 31 published · 17 cross-checked by a second agent · read them all
- Sources
- 9 public pages on 2 sites: github.com, docs.github.com
- Screenshot
- github.com, retrieved · self captured · shows appearance, not capability
- Method
- Same rules for all 103 researched ADEs. How we check · Report wrong data
What it does
Where you use it
The product is a composite GitHub Action with no standalone desktop, browser or phone client. GitHub supplies the workflow-results interface; runner OS support is separate from a desktop ADE client.
Source and scope for Where you use itAgents it runs
The action installs and invokes only Codex CLI; endpoint customization changes the model provider, not the coding harness.
Source and scope for Agents it runsAccounts and subscriptions
Provider API key is required; a ChatGPT subscription-only route is not documented.
Source and scope for Accounts and subscriptionsWhere agents run
Codex runs on the caller-selected GitHub Actions runner. A user-managed runner can execute on the user computer or server; GitHub-hosted runners are GitHub compute, not an OpenAI-managed Codex Action runtime.
Source and scope for Where agents runHow work is kept apart
The action configures Codex permission profiles and runner privileges; it does not provide worktree, container or VM isolation options. Caller-provided runner isolation is separate.
Source and scope for How work is kept apartParallel work
Separate jobs or workflow instances can run the action concurrently, subject to GitHub Actions quotas and caller concurrency settings.
Source and scope for Parallel workScheduled runs
GitHub Actions owns event/schedule dispatch around this action.
Source and scope for Scheduled runsGit and pull requests
The documented review bot returns Codex output to a caller-authored GitHub comment job. The action itself has no pull-request creation or management operation.
Source and scope for Git and pull requestsPrice
The action itself is free (Apache-2.0) with no separate price; it requires the user's own OpenAI or Azure OpenAI API key, so model usage is billed by that provider, and it runs on the user's GitHub runner.
Source and scope for PriceTyped filters
Every value links to its receipt below. Read plan and surface restrictions before using a filter to decide.
| Filter | Value |
|---|---|
| Desktop OS: macOS | No |
| Desktop OS: Windows | No |
| Desktop OS: Linux | No |
| Web client | No |
| Phone access: Native iOS | No |
| Phone access: Native Android | No |
| Phone access: Phone browser | No |
| CLI | Yes |
| Coding agents: Claude Code | No |
| Coding agents: Codex | Yes |
| Coding agents: Cursor Agent | No |
| Coding agents: Gemini CLI | No |
| Coding agents: OpenCode | No |
| Coding agents: Pi | No |
| Coding agents: Grok | No |
| Coding agents: Aider | No |
| Coding agents: Antigravity | No |
| Use my subscription | No cross-checked |
| Where agents run: On your computer | Yes |
| Where agents run: On your own server | Yes |
| Where agents run: In the vendor's cloud | No |
| Workspace isolation: Git worktree | No |
| Workspace isolation: Container | No |
| Workspace isolation: VM or microVM | No |
| Parallel runs | Yes |
| Coordinator | No |
| Native issue tracking | No |
| Unattended triggers | Yes cross-checked |
| Shared prompting | No |
| Team roles | No |
| SSO | No |
| Pull request workflow | No |
| Review interface | No |
| Product license: Apache-2.0 | Yes. Apache-2.0 cross-checked |
| Product license: MIT | No. Apache-2.0 cross-checked |
| Product license: GPL-3.0 | No. Apache-2.0 cross-checked |
| Product license: GPL-3.0-or-later | No. Apache-2.0 cross-checked |
| Product license: AGPL-3.0 | No. Apache-2.0 cross-checked |
| Product license: AGPL-3.0-or-later | No. Apache-2.0 cross-checked |
| Product license: Elastic License 2.0 | No. Apache-2.0 cross-checked |
| Product license: Custom terms | No. Apache-2.0 cross-checked |
| Product license: Proprietary | No. Apache-2.0 cross-checked |
| Self-hosting | Unknown |
| Telemetry opt-out | No |
| Free access | Yes cross-checked |
| Starting price: Free | Yes. Free |
| Starting price: Up to $20/month | No. Free |
| Starting price: $21–40/month | No. Free |
| Starting price: $41–100/month | No. Free |
| Starting price: Over $100/month | No. Free |
| Starting price: Contact for pricing | No. Free |
| Pricing model: Free, no paid plan | Yes cross-checked |
| Pricing model: Free plan | No |
| Pricing model: Subscription | No |
| Pricing model: Per seat | No |
| Pricing model: Usage-based | No |
| Pricing model: Per machine or compute | No |
| Pricing model: Bring your own key | Yes cross-checked |
| Pricing model: One-time purchase | No |
| Paid plans from: No paid plan | Yes. No paid plan |
| Paid plans from: $10 or less/month | No. No paid plan |
| Paid plans from: $11–20/month | No. No paid plan |
| Paid plans from: $21–40/month | No. No paid plan |
| Paid plans from: $41–100/month | No. No paid plan |
| Paid plans from: Over $100/month | No. No paid plan |
| Paid plans from: Contact sales | No. No paid plan |
| Lifecycle status: Active | Unknown |
| Lifecycle status: Sunsetting | Unknown |
| Keeps going with laptop closed | Yes |
| Open-source license | Yes. Apache-2.0 cross-checked |
| Any desktop app | No |
| Paid plan up to $20/month | No. No paid plan |
| Paid plan up to $40/month | No. No paid plan |
| Any phone client | No |
Filter receipts
Desktop OS: macOS: No
Desktop OS: macOS
Typed value: No.
The product is a composite GitHub Action with no standalone desktop, browser or phone client. GitHub supplies the workflow-results interface; runner OS support is separate from a desktop ADE client.
- Desktop os: No desktop client exists in the scoped action source; Linux/macOS/Windows are runner targets.
- Mobile apps: No native iOS or Android app in the scoped action.
- Browser: No action-owned browser client; GitHub Actions displays its logs and outputs.
- Mobile browser: No action-owned phone-browser client.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Desktop OS: Windows: No
Desktop OS: Windows
Typed value: No.
The product is a composite GitHub Action with no standalone desktop, browser or phone client. GitHub supplies the workflow-results interface; runner OS support is separate from a desktop ADE client.
- Desktop os: No desktop client exists in the scoped action source; Linux/macOS/Windows are runner targets.
- Mobile apps: No native iOS or Android app in the scoped action.
- Browser: No action-owned browser client; GitHub Actions displays its logs and outputs.
- Mobile browser: No action-owned phone-browser client.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Desktop OS: Linux: No
Desktop OS: Linux
Typed value: No.
The product is a composite GitHub Action with no standalone desktop, browser or phone client. GitHub supplies the workflow-results interface; runner OS support is separate from a desktop ADE client.
- Desktop os: No desktop client exists in the scoped action source; Linux/macOS/Windows are runner targets.
- Mobile apps: No native iOS or Android app in the scoped action.
- Browser: No action-owned browser client; GitHub Actions displays its logs and outputs.
- Mobile browser: No action-owned phone-browser client.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Web client: No
Web client
Typed value: No.
The product is a composite GitHub Action with no standalone desktop, browser or phone client. GitHub supplies the workflow-results interface; runner OS support is separate from a desktop ADE client.
- Desktop os: No desktop client exists in the scoped action source; Linux/macOS/Windows are runner targets.
- Mobile apps: No native iOS or Android app in the scoped action.
- Browser: No action-owned browser client; GitHub Actions displays its logs and outputs.
- Mobile browser: No action-owned phone-browser client.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Phone access: Native iOS: No
Phone access: Native iOS
Typed value: No.
The product is a composite GitHub Action with no standalone desktop, browser or phone client. GitHub supplies the workflow-results interface; runner OS support is separate from a desktop ADE client.
- Desktop os: No desktop client exists in the scoped action source; Linux/macOS/Windows are runner targets.
- Mobile apps: No native iOS or Android app in the scoped action.
- Browser: No action-owned browser client; GitHub Actions displays its logs and outputs.
- Mobile browser: No action-owned phone-browser client.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Phone access: Native Android: No
Phone access: Native Android
Typed value: No.
The product is a composite GitHub Action with no standalone desktop, browser or phone client. GitHub supplies the workflow-results interface; runner OS support is separate from a desktop ADE client.
- Desktop os: No desktop client exists in the scoped action source; Linux/macOS/Windows are runner targets.
- Mobile apps: No native iOS or Android app in the scoped action.
- Browser: No action-owned browser client; GitHub Actions displays its logs and outputs.
- Mobile browser: No action-owned phone-browser client.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Phone access: Phone browser: No
Phone access: Phone browser
Typed value: No.
The product is a composite GitHub Action with no standalone desktop, browser or phone client. GitHub supplies the workflow-results interface; runner OS support is separate from a desktop ADE client.
- Desktop os: No desktop client exists in the scoped action source; Linux/macOS/Windows are runner targets.
- Mobile apps: No native iOS or Android app in the scoped action.
- Browser: No action-owned browser client; GitHub Actions displays its logs and outputs.
- Mobile browser: No action-owned phone-browser client.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
CLI: Yes
CLI
Typed value: Yes.
The bundled codex-action helper CLI provides setup, permission checks, proxy configuration and run-codex-exec commands for use by the composite workflow.
- Cli: Product-owned supporting CLI: node dist/main.js, named codex-action, with action setup and run-codex-exec commands; distinct from Codex CLI.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Coding agents: Claude Code: No
Coding agents: Claude Code
Typed value: No.
The action installs and invokes only Codex CLI; endpoint customization changes the model provider, not the coding harness.
- Harnesses: Codex is the sole coding harness in the action entry point.
- Custom adapters: No generic coding-harness adapter or alternate executable input; the launcher resolves and executes codex.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Coding agents: Codex: Yes
Coding agents: Codex
Typed value: Yes.
The action installs and invokes only Codex CLI; endpoint customization changes the model provider, not the coding harness.
- Model providers: OpenAI Responses API by default; Azure OpenAI via endpoint override.
- Session integration: Installs pinned or current Codex CLI and runs codex exec.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
Coding agents: Cursor Agent: No
Coding agents: Cursor Agent
Typed value: No.
The action installs and invokes only Codex CLI; endpoint customization changes the model provider, not the coding harness.
- Harnesses: Codex is the sole coding harness in the action entry point.
- Custom adapters: No generic coding-harness adapter or alternate executable input; the launcher resolves and executes codex.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Coding agents: Gemini CLI: No
Coding agents: Gemini CLI
Typed value: No.
The action installs and invokes only Codex CLI; endpoint customization changes the model provider, not the coding harness.
- Harnesses: Codex is the sole coding harness in the action entry point.
- Custom adapters: No generic coding-harness adapter or alternate executable input; the launcher resolves and executes codex.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Coding agents: OpenCode: No
Coding agents: OpenCode
Typed value: No.
The action installs and invokes only Codex CLI; endpoint customization changes the model provider, not the coding harness.
- Harnesses: Codex is the sole coding harness in the action entry point.
- Custom adapters: No generic coding-harness adapter or alternate executable input; the launcher resolves and executes codex.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Coding agents: Pi: No
Coding agents: Pi
Typed value: No.
The action installs and invokes only Codex CLI; endpoint customization changes the model provider, not the coding harness.
- Harnesses: Codex is the sole coding harness in the action entry point.
- Custom adapters: No generic coding-harness adapter or alternate executable input; the launcher resolves and executes codex.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Coding agents: Grok: No
Coding agents: Grok
Typed value: No.
The action installs and invokes only Codex CLI; endpoint customization changes the model provider, not the coding harness.
- Harnesses: Codex is the sole coding harness in the action entry point.
- Custom adapters: No generic coding-harness adapter or alternate executable input; the launcher resolves and executes codex.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Coding agents: Aider: No
Coding agents: Aider
Typed value: No.
The action installs and invokes only Codex CLI; endpoint customization changes the model provider, not the coding harness.
- Harnesses: Codex is the sole coding harness in the action entry point.
- Custom adapters: No generic coding-harness adapter or alternate executable input; the launcher resolves and executes codex.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Coding agents: Antigravity: No
Coding agents: Antigravity
Typed value: No.
The action installs and invokes only Codex CLI; endpoint customization changes the model provider, not the coding harness.
- Harnesses: Codex is the sole coding harness in the action entry point.
- Custom adapters: No generic coding-harness adapter or alternate executable input; the launcher resolves and executes codex.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Use my subscription: No cross-checked
Use my subscription
Typed value: No.
Provider API key is required; a ChatGPT subscription-only route is not documented.
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Codex Action README: API key requirement
Finding: Users must provide an API key for their chosen provider, such as OPENAI_API_KEY or AZURE_OPENAI_API_KEY, as a GitHub Actions secret to use this action.
Where agents run: On your computer: Yes
Where agents run: On your computer
Typed value: Yes.
Codex runs on the caller-selected GitHub Actions runner. A user-managed runner can execute on the user computer or server; GitHub-hosted runners are GitHub compute, not an OpenAI-managed Codex Action runtime.
- Local: The composite action executes in the working directory on a caller-managed runner, including a runner on the user computer.
- Managed cloud: The action provisions no OpenAI-operated runtime; GitHub-hosted Actions runners are an external compute dependency.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Where agents run: On your own server: Yes
Where agents run: On your own server
Typed value: Yes.
Codex runs on the caller-selected GitHub Actions runner. A user-managed runner can execute on the user computer or server; GitHub-hosted runners are GitHub compute, not an OpenAI-managed Codex Action runtime.
- Byo remote: Self-hosted runner configuration is documented with disposable-host precautions.
- Payer: GitHub compute and provider API billing belong to caller.
- Client disconnect: Workflow runner executes independently of user browser session.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
Where agents run: In the vendor's cloud: No
Where agents run: In the vendor's cloud
Typed value: No.
Codex runs on the caller-selected GitHub Actions runner. A user-managed runner can execute on the user computer or server; GitHub-hosted runners are GitHub compute, not an OpenAI-managed Codex Action runtime.
- Local: The composite action executes in the working directory on a caller-managed runner, including a runner on the user computer.
- Managed cloud: The action provisions no OpenAI-operated runtime; GitHub-hosted Actions runners are an external compute dependency.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Workspace isolation: Git worktree: No
Workspace isolation: Git worktree
Typed value: No.
The action configures Codex permission profiles and runner privileges; it does not provide worktree, container or VM isolation options. Caller-provided runner isolation is separate.
- Worktree: No worktree provisioning in the action; checkout belongs to the caller workflow.
- Container: No container provisioning or isolation option in the composite action.
- Vm: No VM provisioning or isolation option in the composite action.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Workspace isolation: Container: No
Workspace isolation: Container
Typed value: No.
The action configures Codex permission profiles and runner privileges; it does not provide worktree, container or VM isolation options. Caller-provided runner isolation is separate.
- Worktree: No worktree provisioning in the action; checkout belongs to the caller workflow.
- Container: No container provisioning or isolation option in the composite action.
- Vm: No VM provisioning or isolation option in the composite action.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Workspace isolation: VM or microVM: No
Workspace isolation: VM or microVM
Typed value: No.
The action configures Codex permission profiles and runner privileges; it does not provide worktree, container or VM isolation options. Caller-provided runner isolation is separate.
- Worktree: No worktree provisioning in the action; checkout belongs to the caller workflow.
- Container: No container provisioning or isolation option in the composite action.
- Vm: No VM provisioning or isolation option in the composite action.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Parallel runs: Yes
Parallel runs
Typed value: Yes.
Separate jobs or workflow instances can run the action concurrently, subject to GitHub Actions quotas and caller concurrency settings.
- Concurrent sessions: Independent action invocations in concurrent GitHub Actions jobs run separate Codex processes.
- Concurrent tasks: Concurrent workflow jobs can invoke the action independently.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
-
Finding: GitHub Actions permits jobs and multiple instances of a workflow to run concurrently by default; caller concurrency settings and runner quotas can restrict this.
Coordinator: No
Coordinator
Typed value: No.
The action starts one Codex process per invocation and supplies no product-owned coordinator or child-agent messaging tools. Codex-native subagents and caller-written workflows are separate.
- Orchestration owner: The action has no coordinator role or cross-session delegation controller.
- Invocation: A workflow invokes one codex exec process.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Native issue tracking: No
Native issue tracking
Typed value: No.
The action exposes prompt inputs and final-message output, with no product-owned issue/task store. GitHub issues and workflow runs belong to GitHub.
- Create: No action-owned issue creation API or persistence.
- Task session separation: No native issue entity separate from workflow invocation.
- Durable states: No action-owned task state machine; workflow state belongs to GitHub.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Unattended triggers: Yes cross-checked
Unattended triggers
Typed value: Yes.
GitHub Actions owns event/schedule dispatch around this action.
- Events: PR-open event example starts the workflow.
- Scheduler location: GitHub Actions workflow runner; schedule policy is caller-defined.
- Client independence: Workflow execution is independent of the triggering browser/laptop.
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
Shared prompting: No
Shared prompting
Typed value: No.
Each action invocation receives a fixed prompt or prompt file and writes a final message; it has no shared live prompting channel.
- Coprompting: The action source exposes no channel for multiple humans to instruct the same running Codex process.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Team roles: No
Team roles
Typed value: No.
The action checks GitHub repository write permission and caller allowlists; it supplies neither native workspace roles nor an enterprise SSO implementation.
- Organization roles: No action-owned organization or role system.
- Sso: No action-owned SSO implementation; GitHub account authentication is external.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
SSO: No
SSO
Typed value: No.
The action checks GitHub repository write permission and caller allowlists; it supplies neither native workspace roles nor an enterprise SSO implementation.
- Organization roles: No action-owned organization or role system.
- Sso: No action-owned SSO implementation; GitHub account authentication is external.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Pull request workflow: No
Pull request workflow
Typed value: No.
The documented review bot returns Codex output to a caller-authored GitHub comment job. The action itself has no pull-request creation or management operation.
- Pull requests: No built-in PR creation or management; caller workflow and arbitrary Codex shell actions are separate.
- Comments: The README example posts comments using a separate github-script job; not an action operation.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Review interface: No
Review interface
Typed value: No.
The action returns final-message output or an output file. It has no product interface displaying proposed code diffs.
- Diffs: No action-owned diff/review interface; GitHub logs and pull request pages are external.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Product license: Apache-2.0: Yes. Apache-2.0 cross-checked
Product license: Apache-2.0
Typed value: Yes. Apache-2.0.
Action source is Apache-2.0 licensed.
- Client license: Apache License 2.0 for the action code.
- Source visibility: Public repository.
- Source revision: 13e9c17417b29e9a276f73ec6ed7fb574137d3c3
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Action source is Apache License 2.0 at pinned revision; Codex and provider/runner terms are separate.
Product license: MIT: No. Apache-2.0 cross-checked
Product license: MIT
Typed value: No. Apache-2.0.
Action source is Apache-2.0 licensed.
- Client license: Apache License 2.0 for the action code.
- Source visibility: Public repository.
- Source revision: 13e9c17417b29e9a276f73ec6ed7fb574137d3c3
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Action source is Apache License 2.0 at pinned revision; Codex and provider/runner terms are separate.
Product license: GPL-3.0: No. Apache-2.0 cross-checked
Product license: GPL-3.0
Typed value: No. Apache-2.0.
Action source is Apache-2.0 licensed.
- Client license: Apache License 2.0 for the action code.
- Source visibility: Public repository.
- Source revision: 13e9c17417b29e9a276f73ec6ed7fb574137d3c3
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Action source is Apache License 2.0 at pinned revision; Codex and provider/runner terms are separate.
Product license: GPL-3.0-or-later: No. Apache-2.0 cross-checked
Product license: GPL-3.0-or-later
Typed value: No. Apache-2.0.
Action source is Apache-2.0 licensed.
- Client license: Apache License 2.0 for the action code.
- Source visibility: Public repository.
- Source revision: 13e9c17417b29e9a276f73ec6ed7fb574137d3c3
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Action source is Apache License 2.0 at pinned revision; Codex and provider/runner terms are separate.
Product license: AGPL-3.0: No. Apache-2.0 cross-checked
Product license: AGPL-3.0
Typed value: No. Apache-2.0.
Action source is Apache-2.0 licensed.
- Client license: Apache License 2.0 for the action code.
- Source visibility: Public repository.
- Source revision: 13e9c17417b29e9a276f73ec6ed7fb574137d3c3
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Action source is Apache License 2.0 at pinned revision; Codex and provider/runner terms are separate.
Product license: AGPL-3.0-or-later: No. Apache-2.0 cross-checked
Product license: AGPL-3.0-or-later
Typed value: No. Apache-2.0.
Action source is Apache-2.0 licensed.
- Client license: Apache License 2.0 for the action code.
- Source visibility: Public repository.
- Source revision: 13e9c17417b29e9a276f73ec6ed7fb574137d3c3
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Action source is Apache License 2.0 at pinned revision; Codex and provider/runner terms are separate.
Product license: Elastic License 2.0: No. Apache-2.0 cross-checked
Product license: Elastic License 2.0
Typed value: No. Apache-2.0.
Action source is Apache-2.0 licensed.
- Client license: Apache License 2.0 for the action code.
- Source visibility: Public repository.
- Source revision: 13e9c17417b29e9a276f73ec6ed7fb574137d3c3
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Action source is Apache License 2.0 at pinned revision; Codex and provider/runner terms are separate.
Product license: Custom terms: No. Apache-2.0 cross-checked
Product license: Custom terms
Typed value: No. Apache-2.0.
Action source is Apache-2.0 licensed.
- Client license: Apache License 2.0 for the action code.
- Source visibility: Public repository.
- Source revision: 13e9c17417b29e9a276f73ec6ed7fb574137d3c3
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Action source is Apache License 2.0 at pinned revision; Codex and provider/runner terms are separate.
Product license: Proprietary: No. Apache-2.0 cross-checked
Product license: Proprietary
Typed value: No. Apache-2.0.
Action source is Apache-2.0 licensed.
- Client license: Apache License 2.0 for the action code.
- Source visibility: Public repository.
- Source revision: 13e9c17417b29e9a276f73ec6ed7fb574137d3c3
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Action source is Apache License 2.0 at pinned revision; Codex and provider/runner terms are separate.
Telemetry opt-out: No
Telemetry opt-out
Typed value: No.
The action manages provider credentials and streams Codex output. Its source exposes no action-owned telemetry opt-out control; Codex, GitHub and model-provider collection are separate.
- Telemetry controls: No action telemetry control in action.yml inputs, src/main.ts command options or src runtime implementation.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Free access: Yes cross-checked
Free access
Typed value: Yes.
Apache-licensed action source is available; execution incurs separate API/runner costs.
- Ongoing free: No separate action software purchase in documented source use; hosted compute/API limits are external.
- Self host cost: Runner compute and API model usage remain separate.
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
Starting price: Free: Yes. Free
Starting price: Free
Typed value: Yes. Free.
Apache-licensed action source is available; execution incurs separate API/runner costs.
- Ongoing free: No separate action software purchase in documented source use; hosted compute/API limits are external.
- Self host cost: Runner compute and API model usage remain separate.
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
Starting price: Up to $20/month: No. Free
Starting price: Up to $20/month
Typed value: No. Free.
Apache-licensed action source is available; execution incurs separate API/runner costs.
- Ongoing free: No separate action software purchase in documented source use; hosted compute/API limits are external.
- Self host cost: Runner compute and API model usage remain separate.
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
Starting price: $21–40/month: No. Free
Starting price: $21–40/month
Typed value: No. Free.
Apache-licensed action source is available; execution incurs separate API/runner costs.
- Ongoing free: No separate action software purchase in documented source use; hosted compute/API limits are external.
- Self host cost: Runner compute and API model usage remain separate.
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
Starting price: $41–100/month: No. Free
Starting price: $41–100/month
Typed value: No. Free.
Apache-licensed action source is available; execution incurs separate API/runner costs.
- Ongoing free: No separate action software purchase in documented source use; hosted compute/API limits are external.
- Self host cost: Runner compute and API model usage remain separate.
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
Starting price: Over $100/month: No. Free
Starting price: Over $100/month
Typed value: No. Free.
Apache-licensed action source is available; execution incurs separate API/runner costs.
- Ongoing free: No separate action software purchase in documented source use; hosted compute/API limits are external.
- Self host cost: Runner compute and API model usage remain separate.
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
Starting price: Contact for pricing: No. Free
Starting price: Contact for pricing
Typed value: No. Free.
Apache-licensed action source is available; execution incurs separate API/runner costs.
- Ongoing free: No separate action software purchase in documented source use; hosted compute/API limits are external.
- Self host cost: Runner compute and API model usage remain separate.
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
Pricing model: Free, no paid plan: Yes cross-checked
Pricing model: Free, no paid plan
Typed value: Yes.
The action itself is free (Apache-2.0) with no separate price; it requires the user's own OpenAI or Azure OpenAI API key, so model usage is billed by that provider, and it runs on the user's GitHub runner.
- First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Pricing model: Free plan: No
Pricing model: Free plan
Typed value: No.
The action itself is free (Apache-2.0) with no separate price; it requires the user's own OpenAI or Azure OpenAI API key, so model usage is billed by that provider, and it runs on the user's GitHub runner.
- Model cost: An API key for OpenAI or Azure OpenAI is required; usage is billed by that provider (no amounts stated).
- First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
-
Finding: Users must supply an API key for their chosen provider (OpenAI or Azure OpenAI) as a GitHub secret, so model usage is billed by that provider; no price for the action is stated.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Pricing model: Subscription: No
Pricing model: Subscription
Typed value: No.
The action itself is free (Apache-2.0) with no separate price; it requires the user's own OpenAI or Azure OpenAI API key, so model usage is billed by that provider, and it runs on the user's GitHub runner.
- Model cost: An API key for OpenAI or Azure OpenAI is required; usage is billed by that provider (no amounts stated).
- First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
-
Finding: Users must supply an API key for their chosen provider (OpenAI or Azure OpenAI) as a GitHub secret, so model usage is billed by that provider; no price for the action is stated.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Pricing model: Per seat: No
Pricing model: Per seat
Typed value: No.
The action itself is free (Apache-2.0) with no separate price; it requires the user's own OpenAI or Azure OpenAI API key, so model usage is billed by that provider, and it runs on the user's GitHub runner.
- Model cost: An API key for OpenAI or Azure OpenAI is required; usage is billed by that provider (no amounts stated).
- First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
-
Finding: Users must supply an API key for their chosen provider (OpenAI or Azure OpenAI) as a GitHub secret, so model usage is billed by that provider; no price for the action is stated.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Pricing model: Usage-based: No
Pricing model: Usage-based
Typed value: No.
The action itself is free (Apache-2.0) with no separate price; it requires the user's own OpenAI or Azure OpenAI API key, so model usage is billed by that provider, and it runs on the user's GitHub runner.
- Model cost: An API key for OpenAI or Azure OpenAI is required; usage is billed by that provider (no amounts stated).
- First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
-
Finding: Users must supply an API key for their chosen provider (OpenAI or Azure OpenAI) as a GitHub secret, so model usage is billed by that provider; no price for the action is stated.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Pricing model: Per machine or compute: No
Pricing model: Per machine or compute
Typed value: No.
The action itself is free (Apache-2.0) with no separate price; it requires the user's own OpenAI or Azure OpenAI API key, so model usage is billed by that provider, and it runs on the user's GitHub runner.
- Model cost: An API key for OpenAI or Azure OpenAI is required; usage is billed by that provider (no amounts stated).
- First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
-
Finding: Users must supply an API key for their chosen provider (OpenAI or Azure OpenAI) as a GitHub secret, so model usage is billed by that provider; no price for the action is stated.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Pricing model: Bring your own key: Yes cross-checked
Pricing model: Bring your own key
Typed value: Yes.
The action itself is free (Apache-2.0) with no separate price; it requires the user's own OpenAI or Azure OpenAI API key, so model usage is billed by that provider, and it runs on the user's GitHub runner.
- Model cost: An API key for OpenAI or Azure OpenAI is required; usage is billed by that provider (no amounts stated).
- First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
-
Finding: Users must supply an API key for their chosen provider (OpenAI or Azure OpenAI) as a GitHub secret, so model usage is billed by that provider; no price for the action is stated.
Pricing model: One-time purchase: No
Pricing model: One-time purchase
Typed value: No.
The action itself is free (Apache-2.0) with no separate price; it requires the user's own OpenAI or Azure OpenAI API key, so model usage is billed by that provider, and it runs on the user's GitHub runner.
- Model cost: An API key for OpenAI or Azure OpenAI is required; usage is billed by that provider (no amounts stated).
- First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
-
Finding: Users must supply an API key for their chosen provider (OpenAI or Azure OpenAI) as a GitHub secret, so model usage is billed by that provider; no price for the action is stated.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Paid plans from: No paid plan: Yes. No paid plan
Paid plans from: No paid plan
Typed value: Yes. No paid plan.
The action itself is free (Apache-2.0) with no separate price; it requires the user's own OpenAI or Azure OpenAI API key, so model usage is billed by that provider, and it runs on the user's GitHub runner.
- Model cost: An API key for OpenAI or Azure OpenAI is required; usage is billed by that provider (no amounts stated).
- First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
-
Finding: Users must supply an API key for their chosen provider (OpenAI or Azure OpenAI) as a GitHub secret, so model usage is billed by that provider; no price for the action is stated.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Paid plans from: $10 or less/month: No. No paid plan
Paid plans from: $10 or less/month
Typed value: No. No paid plan.
The action itself is free (Apache-2.0) with no separate price; it requires the user's own OpenAI or Azure OpenAI API key, so model usage is billed by that provider, and it runs on the user's GitHub runner.
- Model cost: An API key for OpenAI or Azure OpenAI is required; usage is billed by that provider (no amounts stated).
- First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
-
Finding: Users must supply an API key for their chosen provider (OpenAI or Azure OpenAI) as a GitHub secret, so model usage is billed by that provider; no price for the action is stated.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Paid plans from: $11–20/month: No. No paid plan
Paid plans from: $11–20/month
Typed value: No. No paid plan.
The action itself is free (Apache-2.0) with no separate price; it requires the user's own OpenAI or Azure OpenAI API key, so model usage is billed by that provider, and it runs on the user's GitHub runner.
- Model cost: An API key for OpenAI or Azure OpenAI is required; usage is billed by that provider (no amounts stated).
- First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
-
Finding: Users must supply an API key for their chosen provider (OpenAI or Azure OpenAI) as a GitHub secret, so model usage is billed by that provider; no price for the action is stated.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Paid plans from: $21–40/month: No. No paid plan
Paid plans from: $21–40/month
Typed value: No. No paid plan.
The action itself is free (Apache-2.0) with no separate price; it requires the user's own OpenAI or Azure OpenAI API key, so model usage is billed by that provider, and it runs on the user's GitHub runner.
- Model cost: An API key for OpenAI or Azure OpenAI is required; usage is billed by that provider (no amounts stated).
- First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
-
Finding: Users must supply an API key for their chosen provider (OpenAI or Azure OpenAI) as a GitHub secret, so model usage is billed by that provider; no price for the action is stated.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Paid plans from: $41–100/month: No. No paid plan
Paid plans from: $41–100/month
Typed value: No. No paid plan.
The action itself is free (Apache-2.0) with no separate price; it requires the user's own OpenAI or Azure OpenAI API key, so model usage is billed by that provider, and it runs on the user's GitHub runner.
- Model cost: An API key for OpenAI or Azure OpenAI is required; usage is billed by that provider (no amounts stated).
- First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
-
Finding: Users must supply an API key for their chosen provider (OpenAI or Azure OpenAI) as a GitHub secret, so model usage is billed by that provider; no price for the action is stated.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Paid plans from: Over $100/month: No. No paid plan
Paid plans from: Over $100/month
Typed value: No. No paid plan.
The action itself is free (Apache-2.0) with no separate price; it requires the user's own OpenAI or Azure OpenAI API key, so model usage is billed by that provider, and it runs on the user's GitHub runner.
- Model cost: An API key for OpenAI or Azure OpenAI is required; usage is billed by that provider (no amounts stated).
- First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
-
Finding: Users must supply an API key for their chosen provider (OpenAI or Azure OpenAI) as a GitHub secret, so model usage is billed by that provider; no price for the action is stated.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Paid plans from: Contact sales: No. No paid plan
Paid plans from: Contact sales
Typed value: No. No paid plan.
The action itself is free (Apache-2.0) with no separate price; it requires the user's own OpenAI or Azure OpenAI API key, so model usage is billed by that provider, and it runs on the user's GitHub runner.
- Model cost: An API key for OpenAI or Azure OpenAI is required; usage is billed by that provider (no amounts stated).
- First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
-
Finding: Users must supply an API key for their chosen provider (OpenAI or Azure OpenAI) as a GitHub secret, so model usage is billed by that provider; no price for the action is stated.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Keeps going with laptop closed: Yes
Keeps going with laptop closed
Typed value: Yes.
Codex runs on the caller-selected GitHub Actions runner. A user-managed runner can execute on the user computer or server; GitHub-hosted runners are GitHub compute, not an OpenAI-managed Codex Action runtime.
- Byo remote: Self-hosted runner configuration is documented with disposable-host precautions.
- Payer: GitHub compute and provider API billing belong to caller.
- Client disconnect: Workflow runner executes independently of user browser session.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
Open-source license: Yes. Apache-2.0 cross-checked
Open-source license
Typed value: Yes. Apache-2.0.
Action source is Apache-2.0 licensed.
- Client license: Apache License 2.0 for the action code.
- Source visibility: Public repository.
- Source revision: 13e9c17417b29e9a276f73ec6ed7fb574137d3c3
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Action source is Apache License 2.0 at pinned revision; Codex and provider/runner terms are separate.
Any desktop app: No
Any desktop app
Typed value: No.
The product is a composite GitHub Action with no standalone desktop, browser or phone client. GitHub supplies the workflow-results interface; runner OS support is separate from a desktop ADE client.
- Desktop os: No desktop client exists in the scoped action source; Linux/macOS/Windows are runner targets.
- Mobile apps: No native iOS or Android app in the scoped action.
- Browser: No action-owned browser client; GitHub Actions displays its logs and outputs.
- Mobile browser: No action-owned phone-browser client.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
Paid plan up to $20/month: No. No paid plan
Paid plan up to $20/month
Typed value: No. No paid plan.
The action itself is free (Apache-2.0) with no separate price; it requires the user's own OpenAI or Azure OpenAI API key, so model usage is billed by that provider, and it runs on the user's GitHub runner.
- Model cost: An API key for OpenAI or Azure OpenAI is required; usage is billed by that provider (no amounts stated).
- First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
-
Finding: Users must supply an API key for their chosen provider (OpenAI or Azure OpenAI) as a GitHub secret, so model usage is billed by that provider; no price for the action is stated.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Paid plan up to $40/month: No. No paid plan
Paid plan up to $40/month
Typed value: No. No paid plan.
The action itself is free (Apache-2.0) with no separate price; it requires the user's own OpenAI or Azure OpenAI API key, so model usage is billed by that provider, and it runs on the user's GitHub runner.
- Model cost: An API key for OpenAI or Azure OpenAI is required; usage is billed by that provider (no amounts stated).
- First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
-
Finding: Users must supply an API key for their chosen provider (OpenAI or Azure OpenAI) as a GitHub secret, so model usage is billed by that provider; no price for the action is stated.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
Any phone client: No
Any phone client
Typed value: No.
The product is a composite GitHub Action with no standalone desktop, browser or phone client. GitHub supplies the workflow-results interface; runner OS support is separate from a desktop ADE client.
- Desktop os: No desktop client exists in the scoped action source; Linux/macOS/Windows are runner targets.
- Mobile apps: No native iOS or Android app in the scoped action.
- Browser: No action-owned browser client; GitHub Actions displays its logs and outputs.
- Mobile browser: No action-owned phone-browser client.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
All public findings
Findings may summarize a source. They are not presented as verbatim statements.
codex-action:ACC-01: The product is a composite GitHub Action with no standalone desktop, browser or phone client. GitHub supplies the workflow-results interface; runner OS support is separate from a desktop ADE client.
codex-action:ACC-01
The product is a composite GitHub Action with no standalone desktop, browser or phone client. GitHub supplies the workflow-results interface; runner OS support is separate from a desktop ADE client.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
codex-action:ACC-02: The action installs and invokes only Codex CLI; endpoint customization changes the model provider, not the coding harness.
codex-action:ACC-02
The action installs and invokes only Codex CLI; endpoint customization changes the model provider, not the coding harness.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
codex-action:ACC-03: Provider API key is required; a ChatGPT subscription-only route is not documented. cross-checked
codex-action:ACC-03
Provider API key is required; a ChatGPT subscription-only route is not documented.
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
-
Codex Action README: API key requirement
Finding: Users must provide an API key for their chosen provider, such as OPENAI_API_KEY or AZURE_OPENAI_API_KEY, as a GitHub Actions secret to use this action.
codex-action:ACC-04: Workflow must provide checkout, dependencies and secrets before invoking the action. cross-checked
codex-action:ACC-04
Workflow must provide checkout, dependencies and secrets before invoking the action.
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
codex-action:ACC-05: The bundled codex-action helper CLI provides setup, permission checks, proxy configuration and run-codex-exec commands for use by the composite workflow.
codex-action:ACC-05
The bundled codex-action helper CLI provides setup, permission checks, proxy configuration and run-codex-exec commands for use by the composite workflow.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
codex-action:ACC-06: Trusted Codex config can attach MCP tools; the action does not own an MCP service. cross-checked
codex-action:ACC-06
Trusted Codex config can attach MCP tools; the action does not own an MCP service.
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
codex-action:PLAN-01: GitHub event context and prompt text are workflow-authored inputs. cross-checked
codex-action:PLAN-01
GitHub event context and prompt text are workflow-authored inputs.
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
codex-action:PLAN-02: Prompt files can hold task instructions; no durable native planning entity was established. cross-checked
codex-action:PLAN-02
Prompt files can hold task instructions; no durable native planning entity was established.
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
codex-action:PLAN-04: Underlying Codex can load repository instruction files and trusted configuration. cross-checked
codex-action:PLAN-04
Underlying Codex can load repository instruction files and trusted configuration.
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
codex-action:PLAN-06: The action exposes prompt inputs and final-message output, with no product-owned issue/task store. GitHub issues and workflow runs belong to GitHub.
codex-action:PLAN-06
The action exposes prompt inputs and final-message output, with no product-owned issue/task store. GitHub issues and workflow runs belong to GitHub.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
codex-action:COORD-01: Separate jobs or workflow instances can run the action concurrently, subject to GitHub Actions quotas and caller concurrency settings.
codex-action:COORD-01
Separate jobs or workflow instances can run the action concurrently, subject to GitHub Actions quotas and caller concurrency settings.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
-
Finding: GitHub Actions permits jobs and multiple instances of a workflow to run concurrently by default; caller concurrency settings and runner quotas can restrict this.
codex-action:COORD-03: The action starts one Codex process per invocation and supplies no product-owned coordinator or child-agent messaging tools. Codex-native subagents and caller-written workflows are separate.
codex-action:COORD-03
The action starts one Codex process per invocation and supplies no product-owned coordinator or child-agent messaging tools. Codex-native subagents and caller-written workflows are separate.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
codex-action:COORD-04: GitHub Actions owns event/schedule dispatch around this action. cross-checked
codex-action:COORD-04
GitHub Actions owns event/schedule dispatch around this action.
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
codex-action:COORD-05: Final-message output and GitHub job logs expose result; interactive steering is not established. cross-checked
codex-action:COORD-05
Final-message output and GitHub job logs expose result; interactive steering is not established.
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
codex-action:RUN-01: Codex runs on the caller-selected GitHub Actions runner. A user-managed runner can execute on the user computer or server; GitHub-hosted runners are GitHub compute, not an OpenAI-managed Codex Action runtime.
codex-action:RUN-01
Codex runs on the caller-selected GitHub Actions runner. A user-managed runner can execute on the user computer or server; GitHub-hosted runners are GitHub compute, not an OpenAI-managed Codex Action runtime.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
codex-action:RUN-02: The action configures Codex permission profiles and runner privileges; it does not provide worktree, container or VM isolation options. Caller-provided runner isolation is separate.
codex-action:RUN-02
The action configures Codex permission profiles and runner privileges; it does not provide worktree, container or VM isolation options. Caller-provided runner isolation is separate.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
-
Finding: Default callers need repository write access, with explicit allowlists for additional actors/bots. Permission profiles limit commands separately from process privilege reduction; drop-sudo and unprivileged-user have distinct runner requirements.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
codex-action:RUN-05: Startup validates conflicting permission inputs and protected flags; task budget/retry behavior was not tested. cross-checked
codex-action:RUN-05
Startup validates conflicting permission inputs and protected flags; task budget/retry behavior was not tested.
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
-
Finding: Default callers need repository write access, with explicit allowlists for additional actors/bots. Permission profiles limit commands separately from process privilege reduction; drop-sudo and unprivileged-user have distinct runner requirements.
codex-action:RUN-06: GitHub workflow logs and final-message expose the action result. cross-checked
codex-action:RUN-06
GitHub workflow logs and final-message expose the action result.
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
codex-action:TEAM-01: Each action invocation receives a fixed prompt or prompt file and writes a final message; it has no shared live prompting channel.
codex-action:TEAM-01
Each action invocation receives a fixed prompt or prompt file and writes a final message; it has no shared live prompting channel.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
codex-action:TEAM-02: The action checks GitHub repository write permission and caller allowlists; it supplies neither native workspace roles nor an enterprise SSO implementation.
codex-action:TEAM-02
The action checks GitHub repository write permission and caller allowlists; it supplies neither native workspace roles nor an enterprise SSO implementation.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Finding: Default callers need repository write access, with explicit allowlists for additional actors/bots. Permission profiles limit commands separately from process privilege reduction; drop-sudo and unprivileged-user have distinct runner requirements.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
codex-action:TEAM-03: Privilege reduction and command permission profiles are explicit configuration controls. cross-checked
codex-action:TEAM-03
Privilege reduction and command permission profiles are explicit configuration controls.
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
-
Finding: Default callers need repository write access, with explicit allowlists for additional actors/bots. Permission profiles limit commands separately from process privilege reduction; drop-sudo and unprivileged-user have distinct runner requirements.
codex-action:SHIP-01: The action returns final-message output or an output file. It has no product interface displaying proposed code diffs.
codex-action:SHIP-01
The action returns final-message output or an output file. It has no product interface displaying proposed code diffs.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
codex-action:SHIP-02: Caller controls checks and follow-on jobs; no action-native release gate was established. cross-checked
codex-action:SHIP-02
Caller controls checks and follow-on jobs; no action-native release gate was established.
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
codex-action:SHIP-03: The documented review bot returns Codex output to a caller-authored GitHub comment job. The action itself has no pull-request creation or management operation.
codex-action:SHIP-03
The documented review bot returns Codex output to a caller-authored GitHub comment job. The action itself has no pull-request creation or management operation.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
codex-action:SHIP-04: GitHub workflow author grants delivery authority through later jobs and tokens. cross-checked
codex-action:SHIP-04
GitHub workflow author grants delivery authority through later jobs and tokens.
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Default callers need repository write access, with explicit allowlists for additional actors/bots. Permission profiles limit commands separately from process privilege reduction; drop-sudo and unprivileged-user have distinct runner requirements.
codex-action:OWN-01: Action source is Apache-2.0 licensed. cross-checked
codex-action:OWN-01
Action source is Apache-2.0 licensed.
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Action source is Apache License 2.0 at pinned revision; Codex and provider/runner terms are separate.
codex-action:OWN-02: The product code and execution worker can run on user-controlled runners, but GitHub Actions supplies workflow control, triggers, secrets and logs. A self-managed execution worker alone does not establish a fully self-hosted core ADE; a complete user-managed control-plane deployment is unestablished by this source pass.
codex-action:OWN-02
The product code and execution worker can run on user-controlled runners, but GitHub Actions supplies workflow control, triggers, secrets and logs. A self-managed execution worker alone does not establish a fully self-hosted core ADE; a complete user-managed control-plane deployment is unestablished by this source pass.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
codex-action:OWN-03: The action manages provider credentials and streams Codex output. Its source exposes no action-owned telemetry opt-out control; Codex, GitHub and model-provider collection are separate.
codex-action:OWN-03
The action manages provider credentials and streams Codex output. Its source exposes no action-owned telemetry opt-out control; Codex, GitHub and model-provider collection are separate.
- Source inspection covers the composite action at the pinned revision. GitHub Actions, the separately installed Codex version and caller-authored workflow operations are separate components; no runtime scenario was executed.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.
-
Finding: Default callers need repository write access, with explicit allowlists for additional actors/bots. Permission profiles limit commands separately from process privilege reduction; drop-sudo and unprivileged-user have distinct runner requirements.
-
Codex Action entry point and runtime boundary
Finding: The composite action installs only Codex and its Responses proxy, runs one codex exec process on the selected runner, and returns a final message. Its helper CLI has action setup/run commands. Inspection of action.yml and src found no desktop/browser/mobile client, harness adapter, agent delegation controller, task database, shared-prompt server, SSO, diff viewer, PR creation, worktree/container/VM provisioning or action telemetry toggle. GitHub supplies workflow control and permissions; Codex internals are separate.
codex-action:OWN-04: The action itself is free (Apache-2.0) with no separate price; it requires the user's own OpenAI or Azure OpenAI API key, so model usage is billed by that provider, and it runs on the user's GitHub runner. cross-checked
codex-action:OWN-04
The action itself is free (Apache-2.0) with no separate price; it requires the user's own OpenAI or Azure OpenAI API key, so model usage is billed by that provider, and it runs on the user's GitHub runner.
- First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
-
Finding: Users must supply an API key for their chosen provider (OpenAI or Azure OpenAI) as a GitHub secret, so model usage is billed by that provider; no price for the action is stated.
-
Finding: The Apache-2.0 license grants a perpetual, no-charge, royalty-free copyright licence to use and redistribute the software.
codex-action:OWN-06: Public action source and issue tracker exist, without a separate release or support commitment established. cross-checked
codex-action:OWN-06
Public action source and issue tracker exist, without a separate release or support commitment established.
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
codex-action Default-branch commit
Finding: Pinned default-branch commit dated 30 October 2026; release API returned no releases in this pass.
codex-action:OWN-08: Apache-licensed action source is available; execution incurs separate API/runner costs. cross-checked
codex-action:OWN-08
Apache-licensed action source is available; execution incurs separate API/runner costs.
- Documentation establishes only the named facts. Unknown atomic questions and unrun scenarios remain open.
-
Finding: Composite GitHub Action installs Codex and a Responses API proxy; caller supplies provider API key. Workflow prompt/file and model/effort inputs configure codex exec. GitHub workflow handles triggers, checkout and subsequent publishing.