Is your feature request related to a problem? Please describe.
I'm working collaboratively with Codex on an existing feature branch. However, Codex always creates a new branch with a PR or provides a .patch file, instead of simply pushing the changes to the currently selected branch. This creates multiple branches and pull requests, which clutters the workflow when a direct push to the existing branch would suffice. I'm always frustrated when I have to manually apply patches or manage unnecessary PRs for simple incremental edits.

Describe the solution you'd like
I'd like Codex to provide an option to push changes directly to the currently selected branch (e.g., feature/bill-report-fix) without requiring the creation of a new branch or PR. This should work only when the current branch is not protected, and the user has selected it as the base in the Codex setup screen. Ideally, a "Push to current branch" button could be shown when Codex finishes a task.

Additional context
This feature would improve efficiency for users who are actively working in a feature branch with Codex assistance. It would avoid unnecessary PR clutter and reduce friction in solo or tightly integrated team workflows. In my case, I run Payara locally and want to pull Codex’s commits directly to test without handling .patch files or merging from separate branches.