Codex stopped working with github actions openai/codex-action@v1
Resolved 💬 5 comments Opened Jan 15, 2026 by novakDev Closed Jan 15, 2026
What version of Codex is running?
0.84.0
What subscription do you have?
ChatGPT Business
Which model were you using?
_No response_
What platform is your computer?
_No response_
What terminal emulator and version are you using (if applicable)?
_No response_
What issue are you seeing?
Yesterday our github actions codex script worked fine. It used version 0.80.0 . Today it's taking new version of 0.84.0 which make Landlock failure.
Action:
jobs:
codex:
runs-on: ubuntu-latest
permissions:
contents: read
outputs:
final_message: ${{ steps.run_codex.outputs['final-message'] }}
steps:
...
- name: Run Codex
id: run_codex
uses: openai/codex-action@v1
with:
openai-api-key: ${{ secrets.OPENAI_API_KEY }}
prompt: |
This is PR #${{ github.event.pull_request.number }} for ${{ github.repository }}.
Base SHA: ${{ github.event.pull_request.base.sha }}
Head SHA: ${{ github.event.pull_request.head.sha }}
Review ONLY the changes introduced by the PR.
Suggest any improvements, potential bugs, or issues.
Be concise and specific in your feedback.
Pull request title and body:
----
${{ github.event.pull_request.title }}
${{ github.event.pull_request.body }}
Error log:
thinking
**Reviewing code changes between SHAs**
2026-01-15T09:31:16.934869Z ERROR codex_core::codex: needs_follow_up: true
exec
/bin/bash -lc 'git diff --stat 4f6af8e90f6d7a6e2269b40f5d13518b050bd72b 44c207e5d208a014711742250deee789d3d80814' in /home/runner/work/api/api exited 101 in 3ms:
thread 'main' panicked at linux-sandbox/src/linux_run_main.rs:30:9:
error running landlock: Io(Os { code: 13, kind: PermissionDenied, message: "Permission denied" })
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
What steps can reproduce the bug?
Create github action from openai/codex-action@v1 codex readme and it should fail when using 0.84.0 version.
What is the expected behavior?
_No response_
Additional information
_No response_
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗