Hi OpenAI team,
A feature request based on a real workflow gap.
When building and updating a website using an AI chat interface, every change requires copying the updated code, downloading the file, going to GitHub, uploading it manually, and waiting for Vercel to redeploy. It works, but the loop breaks the flow completely.
The fix: a direct GitHub connection from the chat interface. The ability to push an update straight to a repository without leaving the conversation. One action, not five. For everyday users, not just developers.
The infrastructure is already there on both sides. The gap is in the standard chat experience. ChatGPT already supports connectors and integrations with external services, and GitHub offers a well-established API that allows programmatic commits and pushes, so the building blocks for this feature exist; they just haven’t been linked together inside the chat experience.Just wanted to put it out there.
Blessings,
Isabella
Hi @fruitlady, this is basically the current “last mile” gap in the GitHub integration.
Right now ChatGPT’s GitHub connector is mostly read-focused, so repo analysis/search works well, but direct commits, PRs, and deploy flows still aren’t native in normal chat UX.
Which makes the friction pretty obvious:
chat -> copy files -> git push -> deploy
…instead of the workflow people actually want:
chat -> git push -> auto deploy
The infrastructure already exists through GitHub APIs, Vercel auto-deploys, MCP tooling, IDE agents, etc. The harder part is mostly around permissions, approvals, rollback handling, and org-level safety controls.
A lot of folks are asking for exactly what you described, and we’re forwarding this feature request to the team for logging since this workflow gap keeps coming up in developer feedback.
-Marc G.
Hi @fruitlady!
This has actually been possible for a month or two, since write actions were added to certain ChatGPT apps.
You can add GitHub to ChatGPT via Settings > Apps. When you open the app details, there is also a full list of supported commands, including commits.
I just confirmed this:
In the screenshot, I tried to commit in a second step, but that was obviously unnecessary.
Hope this helps!
Thank you! Good to know it exists. The gap I’m describing is discoverability. If it lives in Settings → Apps, most everyday users will never find it. The feature should be native to the chat flow, not buried. That’s the real fix 
I agree. Unfortunately, it’s not always possible to just ask ChatGPT about its own capabilities.
The Codex apps (and the CLI) are a lot more capable in this regard. Just ask the app and it can confidently answer about itself and make improvements on your behalf. I strongly suggest giving it a try.
Hi @vb, thanks for confirming the feature availability. I’ll check with the team to make sure the “Connecting GitHub to ChatGPT” article gets updated accordingly.
-Mark G.
@vb, the point you raise is interesting, ChatGPT not knowing its own capabilities might be a feature, not a bug..
From my personal perspective, ChatGPT is still a chat interface with additional features.
Codex is a new product, and it has become my main tool by now, especially since I can use the same ChatGPT subscription there.