no-active-thread-01a0a510-3213-7113-86a4-48290c3ff455

What version of the Codex App are you using (From “About Codex” dialog)?

Latest

What subscription do you have?

plus

What platform is your computer?

uname -mprs

What issue are you seeing?

I’m a ChatGPT Plus user and I’m still experiencing a GitHub connector capability regression after the Work Mode incident was marked resolved.

The issue began around September 13, 2026 and is reproducible across fresh chats / Work sessions.

What still works:

• GitHub authentication
• access to private repositories
• repository reads and writes
• GitHub Actions run inspection
• job inspection
• logs
• artifacts
• workflow reruns

What is still broken:

• the GitHub connector no longer exposes the capability to create a new GitHub Actions workflow_dispatch run with inputs

This was previously available and was part of my normal workflow.

I have verified after the incident was marked resolved that the capability is still missing from the live GitHub connector tool surface. Searching the connector capabilities for “dispatch” returns no matching action.

Example repository:
harismanzoor28-tech/media-hub

Example workflow:
.github/workflows/e9-provider-key-safety-qualification.yml

The workflow exists on main and has a valid workflow_dispatch trigger with required inputs.

This is not a GitHub authentication failure and not a repository-permissions issue. The GitHub connector is connected and functional for other actions.

I am also seeing intermittent “system is running slow” behavior in Work Mode even though the public OpenAI status page currently says systems are fully operational.

Please investigate this as a residual post-incident connector capability regression affecting my Plus account / Work Mode environment.

Specifically, please confirm:

1. whether the GitHub connector’s new-workflow workflow_dispatch action is currently expected to be available to Plus users,
2. whether this capability was removed or temporarily disabled,
3. whether my account/session is stuck on an older or degraded connector capability schema,
4. whether there is any server-side reset, capability refresh, or account-side remediation required.

The issue is reproducible in new chats, so this does not appear to be caused by stale conversation state.

Please do not classify this as a generic GitHub connection problem—the specific failure is the missing ability to dispatch a new GitHub Actions workflow_dispatch workflow with inputs.

What steps can reproduce the bug?

Feedback ID: no-active-thread-01a0a510-3213-7113-86a4-48290c3ff455

What is the expected behavior?

No response

Additional information

No response

Start by inspecting the GitHub connector capability surface for the workflow_dispatch action and compare it with .github/workflows/e9-provider-key-safety-qualification.yml in harismanzoor28-tech/media-hub. Reproduce the missing action in a fresh chat or Work session and verify whether the workflow trigger and required inputs are recognized. Done means determining whether the capability is expected, disabled, or affected by account/session state, with a documented remediation or escalation.