GitHub PR review still uses deactivated workspace after migrating from Business workspace to Personal Pro account

Open 💬 29 comments Opened Jun 7, 2026 by montella1507

What issue are you seeing?

Summary

Codex GitHub PR review fails with:

This workspace is deactivated. Select an active workspace and try again.

even though I have already switched to an active Personal Pro account and reconnected GitHub.

Environment

  • ChatGPT Personal Pro account
  • Previously member of a Business workspace
  • Business workspace is now deactivated
  • Repository is hosted in a GitHub organization
  • Review triggered both automatically and via @codex review

Troubleshooting Performed

  • Switched to active Personal Pro workspace
  • Verified Personal Pro workspace is selected in ChatGPT/Codex UI
  • Disconnected GitHub from ChatGPT/Codex
  • Reconnected GitHub
  • Reinstalled ChatGPT Codex Connector
  • Re-authorized GitHub access
  • Reproduced with both:
  • automatic PR review
  • @codex review

What steps can reproduce the bug?

  1. Use Codex with a Business workspace.
  2. The Business workspace becomes deactivated.
  3. Switch to a Personal Pro account/workspace.
  4. Disconnect GitHub from ChatGPT/Codex.
  5. Reconnect GitHub.
  6. Reinstall the ChatGPT Codex Connector in the GitHub organization.
  7. Open a PR.
  8. Trigger review using @codex review or wait for automatic review.

What is the expected behavior?

Codex should use the currently active Personal Pro workspace and perform the PR review normally.

Actual Behavior

The review fails with:

This workspace is deactivated. Select an active workspace and try again.

This suggests that the GitHub review integration is still referencing the previously deactivated Business workspace.

Additional information

The GitHub connection in ChatGPT shows the active Personal Pro account correctly.

The issue only appears when Codex attempts to perform a PR review.

This looks like a stale workspace association that was not cleared after the Business workspace was deactivated.

View original on GitHub ↗

29 Comments

praveentcom · 1 month ago

+1

hubeiqiao · 1 month ago

I experienced the same issue since yesterday.

samo33ddd · 1 month ago

same

umairnadeem · 1 month ago

+1. seeing this on all my PRs since a couple days ago. examples:

https://github.com/openslop/openslop/pull/210
https://github.com/openslop/openslop/pull/209

I've had my business workspace deactivated for a while, so this seems like a new regression.

Also likely related: when I visit chatgpt.com, the profile icon on the bottom left side panel shows the old, deactivated workspace. Upon clicking on the profile icon to open the menu dropdown, the profile suddenly changes to show my personal workspace. Definitely feels like a borked experience.

This is blocking my business critical workflows, would appreciate support!

yosriady · 1 month ago

seeing the same thing! I suspect it's related to being a member with multiple workspaces?

Q1CHENL · 1 month ago

have been seeing this problem for 3 days

praveentcom · 1 month ago

@yosriady, yes, seems like. I had a business workspace which is deactivated and the account is deleted. Still, Codex Code Review backend system doesn't auto remove the link I guess.

SoufBel · 1 month ago

+1

montella1507 · 1 month ago

Hopefully they will fix this soon. It is one of the paid features, important for lot of the paid users and they cannot use it :-/

snoo72 · 1 month ago

This is still happening on Pro max plan. @codex team please fix!

kaylanhua · 1 month ago

+1 still experiencing this issue

handong66 · 1 month ago

same here

Rqcker · 1 month ago

I tried deleting my codex environment and rebuilding it (which was really risky and costly), but it still didn't work :(

snoo72 · 1 month ago

Still no update @codex @codex-maintainers ?

montella1507 · 1 month ago

<img width="1810" height="328" alt="Image" src="https://github.com/user-attachments/assets/40b54219-c6d8-46a3-859c-114c586fd41c" />

<img width="2630" height="1574" alt="Image" src="https://github.com/user-attachments/assets/18845189-d9c4-4a20-ac16-4f1e65f5bd76" />

they have probably changed something (new error message)... but it is still nonsense.

How could i have no credits when codex did 0 reviews...

samo33ddd · 1 month ago
<img width="1810" height="328" alt="Image" src="https://github.com/user-attachments/assets/40b54219-c6d8-46a3-859c-114c586fd41c" /> <img width="2630" height="1574" alt="Image" src="https://github.com/user-attachments/assets/18845189-d9c4-4a20-ac16-4f1e65f5bd76" /> they have probably changed something (new error message)... but it is still nonsense. How could i have no credits when codex did 0 reviews...

same

umairnadeem · 1 month ago

^ Same usage issue now: https://github.com/openslop/openslop/pull/276

<img width="1907" height="1599" alt="Image" src="https://github.com/user-attachments/assets/4aa9d508-133f-4166-85b4-2096e49ffbb6" />

<img width="2595" height="831" alt="Image" src="https://github.com/user-attachments/assets/a4321eed-7022-46ed-86b6-37478d3d7db4" />

Opened a case with support and they're completely oblivious. How is this almost a trillion dollar company?

Rqcker · 1 month ago
^ Same usage issue now: openslop/openslop#276 <img alt="Image" width="1907" height="1599" src="https://private-user-images.githubusercontent.com/49003219/607523319-4aa9d508-133f-4166-85b4-2096e49ffbb6.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODEzNzQ0NzYsIm5iZiI6MTc4MTM3NDE3NiwicGF0aCI6Ii80OTAwMzIxOS82MDc1MjMzMTktNGFhOWQ1MDgtMTMzZi00MTY2LTg1YjQtMjA5NmU0OWZmYmI2LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjA2MTMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwNjEzVDE4MDkzNlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTk2MzA1ZDdmZjMxODJkMzgyN2IwMGE3YjMxYzlkMWEyZmUzOWQxZWMyNGQxN2RjMmVlZDk4NTNjNWZlZjBjOTImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JnJlc3BvbnNlLWNvbnRlbnQtdHlwZT1pbWFnZSUyRnBuZyJ9.vDRkYViDK6Jl1nigyDIesnJPwbbBg2-sSyLjRxmgNd4"> <img alt="Image" width="2000" height="640" src="https://private-user-images.githubusercontent.com/49003219/607523479-a4321eed-7022-46ed-86b6-37478d3d7db4.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODEzNzQ0NzYsIm5iZiI6MTc4MTM3NDE3NiwicGF0aCI6Ii80OTAwMzIxOS82MDc1MjM0NzktYTQzMjFlZWQtNzAyMi00NmVkLTg2YjYtMzc0NzhkM2Q3ZGI0LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjA2MTMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwNjEzVDE4MDkzNlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWMzN2NhMzAyNDk0YzE4NTM0YTdjYmY0ZWFjNDRlNDIzYzU3MmM2NThhMGExZWVmMmY2MTgzYWM1OTI4YmRmZGMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JnJlc3BvbnNlLWNvbnRlbnQtdHlwZT1pbWFnZSUyRnBuZyJ9.rmaOpgcydMlmNgOGkSB4lPihvd_uqUFWZ9eMDNuYkEY"> Opened a case with support and they're completely oblivious. How is this almost a trillion dollar company?

Same here today, they just changed the error display and tell us we are out of usage

Q1CHENL · 1 month ago
> ^ Same usage issue now: openslop/openslop#276 > <img alt="Image" width="1907" height="1599" src="https://private-user-images.githubusercontent.com/49003219/607523319-4aa9d508-133f-4166-85b4-2096e49ffbb6.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODEzNzQ0NzYsIm5iZiI6MTc4MTM3NDE3NiwicGF0aCI6Ii80OTAwMzIxOS82MDc1MjMzMTktNGFhOWQ1MDgtMTMzZi00MTY2LTg1YjQtMjA5NmU0OWZmYmI2LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjA2MTMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwNjEzVDE4MDkzNlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTk2MzA1ZDdmZjMxODJkMzgyN2IwMGE3YjMxYzlkMWEyZmUzOWQxZWMyNGQxN2RjMmVlZDk4NTNjNWZlZjBjOTImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JnJlc3BvbnNlLWNvbnRlbnQtdHlwZT1pbWFnZSUyRnBuZyJ9.vDRkYViDK6Jl1nigyDIesnJPwbbBg2-sSyLjRxmgNd4"> <img alt="Image" width="2000" height="640" src="https://private-user-images.githubusercontent.com/49003219/607523479-a4321eed-7022-46ed-86b6-37478d3d7db4.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODEzNzQ0NzYsIm5iZiI6MTc4MTM3NDE3NiwicGF0aCI6Ii80OTAwMzIxOS82MDc1MjM0NzktYTQzMjFlZWQtNzAyMi00NmVkLTg2YjYtMzc0NzhkM2Q3ZGI0LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjA2MTMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwNjEzVDE4MDkzNlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWMzN2NhMzAyNDk0YzE4NTM0YTdjYmY0ZWFjNDRlNDIzYzU3MmM2NThhMGExZWVmMmY2MTgzYWM1OTI4YmRmZGMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JnJlc3BvbnNlLWNvbnRlbnQtdHlwZT1pbWFnZSUyRnBuZyJ9.rmaOpgcydMlmNgOGkSB4lPihvd_uqUFWZ9eMDNuYkEY"> > Opened a case with support and they're completely oblivious. How is this almost a trillion dollar company? Same here today, they just changed the error display and tell us we are out of usage

Saaammee

montella1507 · 1 month ago

It looks like they don't care :-/ They are forcing users to do reseatch about Claude's PR review possibilities...

d3ming · 1 month ago

+1

I have not used any quota on my Pro account but Codex review via Github Connector keeps trying to use the deactivated workspace. Recently the error changed from This workspace is deactivated. Select an active workspace and try again. to You have reached your Codex usage limits for code reviews. You can see your limits in the [Codex usage dashboard](https://chatgpt.com/codex/cloud/settings/usage). but the symptom is exactly the same - can't get any code review usage even though there have been 0 code reviews done.

<img width="1291" height="1012" alt="Image" src="https://github.com/user-attachments/assets/c73495e3-8172-448b-974a-f2c2e8842794" />

langerkirill · 1 month ago

I’m hitting the same issue on Personal Pro.

@codex review returns the code-review usage-limit error even though my Codex dashboard still shows available usage:

  • 5-hour usage limit: 91% remaining
  • Weekly usage limit: 87% remaining
  • Code review analytics: 0 PRs reviewed for the selected period

I already tried the full disconnect/reconnect path:

  • disconnected GitHub from Codex/ChatGPT
  • revoked/removed GitHub app and connector access I could find
  • disconnected from every workspace/account I could find
  • re-authorized GitHub from the intended Personal Pro workspace
  • retried @codex review

The same issue persists. OpenAI support said a human would follow up, but I haven’t received a response yet.

This looks like a server-side stale GitHub PR-review workspace binding that the user-facing reconnect flow cannot clear. Please route this to the Codex/GitHub code-review backend team and provide a way to clear or reassign the PR-review binding for the affected GitHub account/repo.

praveentcom · 29 days ago

@codex-maintainers - can we please assign someone take a look on this issue, please? There are so many affected users and the least we can expect from the team is an acknowledgement and a timeline for the fix (if any). Lack of responses makes us feel we're talking to a wall.

montella1507 · 27 days ago

To be honest.. Codex Code review is the main factor which prevents me to move to Anthropic.. however it seems OpenAI do not care about their PAID features anymore... sad :-(

Q1CHENL · 27 days ago

still broken. unbelievable

montella1507 · 27 days ago

Did u try to complaint the invoice ? Cloud based cloud reviews is part of paid plans only... And we cannot use it for more than 2-3 weeks.

montella1507 · 18 days ago

They don't care. Sad.

deangabbai · 7 days ago

Broken

<img width="2032" height="962" alt="Image" src="https://github.com/user-attachments/assets/67648a04-7299-49b5-9971-ff60e53be78d" />

Q1CHENL · 5 days ago

good news: it's working for me now!