Repository Issue Activity (beta)

#150 v1.12: Linux run never returns after the turn completes; job dies on timeout with the output file already written

#168 Publish codex-action to GitHub Marketplace and request verified creator status

#160 drop-sudo (default safety-strategy) chmods /run service sockets to 0700, breaking D-Bus and systemd-resolved — GitHub-hosted runners die mid-job at ~55 minutes

#158 Install step can silently produce a broken Codex CLI (missing platform binary)

#154 Inline prompts are copied into the action helper process argv

#153 Fast Codex exits can crash the action with an unhandled stdin EPIPE

#152 drop-sudo treats signal-terminated helper commands as successful

#127 codex-responses-api-proxy rejects base64 API keys, blocking responses-api-endpoint (e.g. Bedrock bearer tokens)

#149 Duplicate of #144

#148 Duplicate of #144

#144 Server-info state collides across workflow re-run attempts

#141 Invalid prompt-file and working-directory paths fail only after setup side effects

#139 Mutually exclusive inputs are rejected only after irreversible setup steps

#137 Failed Codex runs can leave temporary output directories behind

#135 Custom codex-home fails when the target directory does not exist yet

#133 Stale server-info files can make later action invocations reuse a dead Responses proxy

#125 Coding

#107 Support AWS Bedrock as a provider backend

#84 Update the internal setup-node dependency to a Node 24-compatible version

#69 Failure on self-hosted runner with default safety-strategy=drop-sudo when runner/sudo setup is absent

#108 Responses API proxy hangs when using ARC runners with k8s

#27 Subscription auth

#103 `output-schema` with `runAsUser` fails to create temporary file

#105 write-proxy-config is not idempotent across repeated runs

#86 Feature request: allow-bots should support specifying individual bot accounts