Disable the built-in `GitHub` app (the one that appears in the `$` command) after `v0.117`

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

• #14316

Powered by Codex Action

Do you think it’s a good idea to blindly load so many tool schemas into the context window at startup, with no option to disable them?

The model already knows how to use the gh CLI; it doesn’t need even a single line of additional context to perform these tasks effectively.

And not everyone uses GitHub. Many people rely on codeberg/gitlab/sourcehut/self-hosted git services instead.

Below is the tools the agent tells me it can use at STARTUP:

> what tools you are available to call?

> [... Omit other tools...]
> GitHub connector tools:
  - functions.mcp__codex_apps__github_add_comment_to_issue
  - functions.mcp__codex_apps__github_add_reaction_to_issue_comment
  - functions.mcp__codex_apps__github_add_reaction_to_pr
  - functions.mcp__codex_apps__github_add_reaction_to_pr_review_comment
  - functions.mcp__codex_apps__github_add_review_to_pr
  - functions.mcp__codex_apps__github_check_repo_initialized
  - functions.mcp__codex_apps__github_compare_commits
  - functions.mcp__codex_apps__github_create_blob
  - functions.mcp__codex_apps__github_create_branch
  - functions.mcp__codex_apps__github_create_commit
  - functions.mcp__codex_apps__github_create_file
  - functions.mcp__codex_apps__github_create_pull_request
  - functions.mcp__codex_apps__github_create_tree
  - functions.mcp__codex_apps__github_download_user_content
  - functions.mcp__codex_apps__github_enable_auto_merge
  - functions.mcp__codex_apps__github_fetch
  - functions.mcp__codex_apps__github_fetch_blob
  - functions.mcp__codex_apps__github_fetch_commit
  - functions.mcp__codex_apps__github_fetch_file
  - functions.mcp__codex_apps__github_fetch_issue
  - functions.mcp__codex_apps__github_fetch_issue_comments
  - functions.mcp__codex_apps__github_fetch_pr
  - functions.mcp__codex_apps__github_fetch_pr_comments
  - functions.mcp__codex_apps__github_fetch_pr_file_patch
  - functions.mcp__codex_apps__github_fetch_pr_patch
  - functions.mcp__codex_apps__github_get_commit_combined_status
  - functions.mcp__codex_apps__github_get_issue_comment_reactions
  - functions.mcp__codex_apps__github_get_pr_diff
  - functions.mcp__codex_apps__github_get_pr_info
  - functions.mcp__codex_apps__github_get_pr_reactions
  - functions.mcp__codex_apps__github_get_pr_review_comment_reactions
  - functions.mcp__codex_apps__github_get_profile
  - functions.mcp__codex_apps__github_get_repo
  - functions.mcp__codex_apps__github_get_repo_collaborator_permission
  - functions.mcp__codex_apps__github_get_user_login
  - functions.mcp__codex_apps__github_get_users_recent_prs_in_repo
  - functions.mcp__codex_apps__github_label_pr
  - functions.mcp__codex_apps__github_list_installations
  - functions.mcp__codex_apps__github_list_installed_accounts
  - functions.mcp__codex_apps__github_list_pr_changed_filenames
  - functions.mcp__codex_apps__github_list_recent_issues
  - functions.mcp__codex_apps__github_list_repositories
  - functions.mcp__codex_apps__github_list_repositories_by_affiliation
  - functions.mcp__codex_apps__github_list_repositories_by_installation
  - functions.mcp__codex_apps__github_list_user_org_memberships
  - functions.mcp__codex_apps__github_list_user_orgs
  - functions.mcp__codex_apps__github_remove_reaction_from_issue_comment
  - functions.mcp__codex_apps__github_remove_reaction_from_pr
  - functions.mcp__codex_apps__github_remove_reaction_from_pr_review_comment
  - functions.mcp__codex_apps__github_reply_to_review_comment
  - functions.mcp__codex_apps__github_search
  - functions.mcp__codex_apps__github_search_branches
  - functions.mcp__codex_apps__github_search_commits
  - functions.mcp__codex_apps__github_search_installed_repositories_streaming
  - functions.mcp__codex_apps__github_search_installed_repositories_v2
  - functions.mcp__codex_apps__github_search_issues
  - functions.mcp__codex_apps__github_search_prs
  - functions.mcp__codex_apps__github_search_repositories
  - functions.mcp__codex_apps__github_update_issue_comment
  - functions.mcp__codex_apps__github_update_ref
  - functions.mcp__codex_apps__github_update_review_comment

maybe you can try it with the id instead of the name? I disabled the plugin via codex app, and it is quite opaque: you first click a thread of an folder to take the view of the plugins/mcp/skills of that folder, then 1) click "Plugins" in the left sidebar 2) click "Manage" in the top right corner 3) click on the tab "Apps" 4) toggle the switch from enabled, to disabled. But then the change is not repo-scoped but global-scoped, so the change is reflected in ~/.codex/config or %USERPROFILE%\.codex\config.toml and it looks for me as following:

...

[apps.connector_76869538009648d5b282a4bb21c3d157]
enabled = false

Edit: Ahh I see, you also used the plugins. prefix instead of the apps. prefix. Another source of error.

maybe you can try it with the id instead of the name? I disabled the plugin via codex app, and it is quite opaque: you first click a thread of an folder to take the view of the plugins/mcp/skills of that folder, then 1) click "Plugins" in the left sidebar 2) click "Manage" in the top right corner 3) click on the tab "Apps" 4) toggle the switch from enabled, to disabled. But then the change is not repo-scoped but global-scoped, so the change is reflected in ~/.codex/config or %USERPROFILE%\.codex\config.toml and it looks for me as following: ... [apps.connector_76869538009648d5b282a4bb21c3d157] enabled = false Edit: Ahh I see, you also used the plugins. prefix instead of the apps. prefix. Another source of error.

I am using the CLI, not the Codex GUI. And there is no way in the CLI to disable apps—only plugins can be disabled or uninstalled. Even after uninstalling the GitHub plugin, the GitHub app remains. This workaround feels hacky and undocumented, which makes it Unacceptable as a proper solution.

Absolute right, but with such a tone you won't make the developer make it happen faster. But the workaround helps you NOW, if you care about token burning or whatever you cared about when you drawn up the issue. 🙂

Absolute right, but with such a tone you won't make the developer make it happen faster. But the workaround helps you NOW, if you care about token burning or whatever you cared about when you drawn up the issue. 🙂

Thank you for the workaround.

And I find this is definitely a regression in the CLI. I just reverted the codex to an older version. Before 0.117.0, the app is an experimental feature, and once it is enabled, there will be a slash command /apps which allows you to disable the app.

But when it is upgraded to v0.117.0, the apps is no longer marked as experimental, and the /apps slash command is removed, making uninstalling app from CLI not possible.

@milanglacier actually this is only a UI or TUI problem. It is simply not rendered as suggestion. What I mean is, when you blindly type /apps you have your missing /apps view, and there you also can enable/disable the app. Not documented, or haven fotgotten, I don't now. I am only the messenger, don't shoot me.

And the GitHub app's permission is aligned with the Codex setting instead of the user. The behavior of some instructions changed after the upgrade.
I saw that when I wanted codex to reply to a comment, it tried the GitHub app and then failed with 403. It told me the app's permission was different from my account, then it fell back into using the gh finally.

Try codex features disable apps
https://developers.openai.com/codex/config-reference