Hello, support codex codex-cloud codex-web
We are seeing a reproducible issue with Codex Web in repositories that require signed or verified commits.
What we tested
- Configured commit signing in the Codex Web environment.
- Confirmed local signed commits can be created inside the runtime.
- Ran multiple small change tasks using the built-in Codex Web GitHub flow.
- Compared this against another repository context where Codex Web completes successfully.
What happens
- Codex Web creates a branch in GitHub.
- But the branch is empty and remains identical to the base branch.
- The commit created inside the runtime is not published to the remote branch.
- As a result, there is no usable branch state for a pull request.
Important context
- We did not use a personal GitHub token or manual push workaround.
- We are testing the built-in Codex Web behavior only.
- The problem appears specifically in repositories with strict signed/verified commit requirements.
Questions
- Is this a known limitation or a bug?
- Are repositories with required signed commits officially supported for Codex Web write/publish flows?
- Which repository or organization policies can cause Codex Web to create an empty branch without publishing the commit?
We need a clear technical answer, because the behavior is reproducible but not clearly documented.