codex - 💡(How to fix) Fix Codex Git commit prompt does not work when using ChatGPT for iOS remote control on macOS

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.513.31313 (2867)

What subscription do you have?

ChatGPT Pro 20x (for OSS)

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

When using ChatGPT for iOS remote control to control macOS, the Codex Git commit prompt does not take effect after triggering the commit flow.

What steps can reproduce the bug?

  1. Open Codex App settings on macOS.
  2. Configure a custom Git commit prompt / Git commit instructions.
  3. Open ChatGPT for iOS.
  4. Connect to the macOS device using the remote control feature.
  5. Start a Codex coding session with Git changes.
  6. Trigger the Git commit prompt / commit flow.
  7. Observe that the configured Git commit prompt is ignored or does not take effect.

What is the expected behavior?

The configured Git commit prompt should be applied normally during the commit flow, even when Codex is being controlled through ChatGPT for iOS remote control on macOS.

Additional information

  1. The issue appears to be specific to the ChatGPT for iOS remote control workflow. The same Git commit prompt configuration works correctly when using Codex directly on macOS without remote control.
  2. Codex can read ~/.codex/.codex-global-state.json correctly when explicitly instructed to do so manually. In that case, it is able to retrieve and apply the configured Git commit prompt successfully. This suggests the issue may be related to the remote control workflow not automatically loading or propagating the global state configuration.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING