›_ Codex Issues
Codex Issues / #37330

GitHub plugin reconnect succeeds, but connector sees zero repositories and writes return 403

Open 💬 3 comments Opened Aug 6, 2026 by SenlerBot
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Summary

In Codex Desktop, reconnecting the GitHub plugin appears to succeed, but the connector exposes no GitHub installations or repositories. Write operations against a repository accessible to the connected account fail with 403 Resource not accessible by integration.

Environment

  • Codex Desktop on Windows with WSL2 Ubuntu 22.04
  • Codex CLI 0.146.0
  • GitHub plugin 0.1.8-2841cf9749ae
  • Target repository: SenlerBot/senler-io-codex-plugin (public, currently empty)

Steps to reproduce

  1. Install the GitHub plugin in Codex Desktop.
  2. Connect or reconnect a GitHub account that has access to the target organization and repository.
  3. Ask Codex to search the connector's installed repositories.
  4. Attempt to create a file in the target repository through the GitHub connector.

Actual behavior

  • Repository discovery reports zero installed repositories, including after reconnecting several times.
  • A direct create-file request fails with:

403 Resource not accessible by integration

  • Codex shows the account/plugin as connected, but GitHub repository settings show no GitHub App installed on the repository.
  • The UI does not provide an actionable prompt to install or approve the GitHub App for the organization/repository.

Expected behavior

The authorized repository should be visible and writable. If a separate GitHub App installation or organization approval is required, the reconnect flow should clearly request it and report that setup is incomplete rather than appearing successful.

Additional context

Local Git operations and the prepared commit are working. Missing gh in WSL and an unrelated read-only deploy key are separate local authentication limitations; they are not the connector failure described here.

No credentials or tokens are included in this report.

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 21 days ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #36547
  • #36473

Powered by Codex Action

Theblackcat98 · 12 days ago

Experiencing the same issue!

toumix-agents · 9 days ago

A closely related private-repository reproduction:

  • Codex Desktop showed the GitHub plugin as connected.
  • Connector calls against a private repository accessible to the user returned GitHub API 404 Not Found (including Actions workflow-job reads).
  • In the same task, the locally authenticated gh account had repo scope and successfully listed that repository's workflow runs.
  • The connector error gave no indication that the GitHub App installation or repository selection was incomplete; it looked like the repository/run did not exist.

This creates a bad fallback loop: connector 404 -> local CLI fallback -> permission/network prompts, while the UI still presents GitHub and Full Access as available.

Expected: either the connector should access repositories granted to the connected account, or the UI/error should clearly say that the GitHub App is not installed/authorized for that repository and provide the repository-selection remediation. Repository name and credentials omitted.