The web version of codex cannot search the github repository

Resolved 💬 11 comments Opened Oct 2, 2025 by 21888 Closed Jan 7, 2026
💡 Likely answer: A maintainer (gpeal, contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

_No response_

Which model were you using?

_No response_

What platform is your computer?

_No response_

What steps can reproduce the bug?

Codex web can’t add new GitHub repos, the repo search request just times out.

https://chatgpt.com/backend-api/wham/github/repositories/search

{"detail":"Request timeout"}

What is the expected behavior?

_No response_

What do you see instead?

_No response_

Additional information

_No response_

View original on GitHub ↗

11 Comments

21888 · 9 months ago

So I can’t add new projects to Codex web. Wondering if anyone else is seeing this too.

21888 · 9 months ago
CodeAlexx · 9 months ago

its a joke -- it modifies, then i ask to commit, it tells me it does not have the ability to add, modify code. turning out just as stupid as the cli version

gpeal contributor · 9 months ago

Can you try again? Some updates have rolled out this week.

21888 · 9 months ago
Can you try again? Some updates have rolled out this week.

Still timed out

Sgw32 · 9 months ago

I have the same trouble. Previously it worked
Tells:

Failed to load repositories. Please ensure you have connected your GitHub account. This list only includes repositories that you have access to in GitHub and can use with Codex. Missing a repo? Configure repository access.

Google Chrome | 140.0.7339.210 (Official build) (64 бит) (cohort: Control)
-- | --
Version| e94a84e11c533d3723422f76dee4f79d6394dac8-refs/branch-heads/7339@{#2367}
ОС | Windows 11 Version 23H2 (Build 22631.5909)
JavaScript | V8 14.0.365.10
User Agent | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36

alexchexes · 9 months ago

same issue

21888 · 9 months ago

If OpenAI doesn’t fix the issue, we’ll handle it ourselves. You can use any packet capture tool that supports request overriding.

Steps:

  1. Go to the repository list page

Visit https://chatgpt.com/codex/settings/code-review and check whether your repository appears there, since the list is quite long.

  1. Locate the code review request

While on that page, find the request to
https://chatgpt.com/backend-api/wham/settings/code_review?page=1&per_page=100.
Identify the repository you want to add and copy the corresponding JSON data for later use.

  1. Open the environment creation page

Go to https://chatgpt.com/codex/settings/environment/create.

  1. Capture and modify the repository request

Capture the request to
https://chatgpt.com/backend-api/wham/github/repositories/v2/*******?page=1&per_page=20,
and override it so that the "repositories" array contains only the repository you want to add.

  1. Add the repository via the web interface

Once you’ve modified the request, you should be able to add the repository directly from the web page.

  1. (Optional) Direct API call

Alternatively, you can capture the “add” request and directly call the same API endpoint to add the repository manually.

If OpenAI doesn’t resolve this for a long time, I might just write a Chrome extension to automate the entire process.

21888 · 8 months ago

Using the Override content feature in Chrome's DevTools makes it easier to override API addresses.

rasmusrygaard contributor · 6 months ago

@21888 Sorry this has been open for a while. Are you still seeing this issue? We've made some optimizations since you first reported this but I want to make sure this is working well for you.

The search should be much more performant if you specify <orgname>/<reponame> in the search (ie just paste the full name of your repo), but even basic search should perform better now.

21888 · 6 months ago
@21888 Sorry this has been open for a while. Are you still seeing this issue? We've made some optimizations since you first reported this but I want to make sure this is working well for you. The search should be much more performant if you specify <orgname>/<reponame> in the search (ie just paste the full name of your repo), but even basic search should perform better now.

Thanks for following up — the search behavior is working correctly for me now, and I’m no longer seeing the original issue. This can be closed. Thanks!