Codex Desktop GitHub connector ignores “Always allow” and repeatedly prompts for the same write action

What version of the Codex App are you using?

Codex Desktop 26.730.61639

What subscription do you have?

ChatGPT Pro

What platform is your computer?

macOS, Apple Silicon (arm64)

What issue are you seeing?

The GitHub connector permission dialog does not honor the Always allow selection.

When ChatGPT attempts a GitHub write action, Codex Desktop displays an approval card such as:

Allow ChatGPT to use GitHub?
Creates a GitHub issue in openai/codex ...

Always allow | Deny | Allow once

I selected Always allow, but the same GitHub approval prompt continued to appear for subsequent GitHub write actions in the same workflow.

This was not a shell-command approval. It was the app-level approval dialog for the installed GitHub connector (github@openai-curated-remote).

The failure had a concrete side effect: delayed connector retries created multiple duplicate GitHub issues for the same requested action. The canonical issue was #37179, while delayed retries created #37181, #37182, and #37183, which then had to be closed as duplicates.

What steps can reproduce the bug?

1. In Codex Desktop, use the installed GitHub connector.
2. Ask ChatGPT to perform a GitHub write action, such as creating an issue in openai/codex.
3. When the approval card appears, select Always allow.
4. Continue the same workflow or perform another GitHub write action.
5. Observe that the same app-level GitHub approval card appears again.
6. In some cases, delayed retries may execute the original write more than once, producing duplicate issues or other duplicate mutations.

What is the expected behavior?

After selecting Always allow for the GitHub connector, Codex Desktop should persist that choice according to the scope shown by the UI and should not repeatedly request approval for equivalent GitHub actions.

At minimum:

• the approval scope should be explicit;
• the persistent decision should survive subsequent actions in the same session;
• connector retries must be idempotent or deduplicated;
• a repeated approval prompt must not cause the same GitHub mutation to execute multiple times; and
• the UI should distinguish between a genuinely new permission scope and a failed persistence state.

Actual behavior

• Always allow was selected.
• The same GitHub connector approval prompt kept appearing.
• The original issue-creation request was retried multiple times.
• Duplicate issues #37181, #37182, and #37183 were created after canonical issue #37179.

Additional information

Feedback was uploaded from the affected Codex Desktop state.

Feedback ID:

no-active-thread-019fd465-3579-7d53-b7d5-2f5b0a20f2e7

A screenshot was captured showing the GitHub approval card with the Always allow option selected as the intended persistent choice.

Related but not identical reports:

• #11298 — persistent approval does not work for shell commands
• #24017 — Browser Use ignores persisted origin/upload approvals

This report is specifically about the GitHub connector app-level approval surface and the resulting duplicate write actions.