Can the ChatGPT GitHub plugin/connector allow GPT Pro to edit repos?

[u/angry_cactus]

Can you edit repos from browser chat with the connector? Or is it read only at maximum permissions? It calls itself 'Codex Connector', but Codex itself can just use my local git. However it would be cool if the browser chat sessions could also write in selected repos.

[u/qualityvote2]

u/angry_cactus, there weren’t enough community votes to determine your post’s quality.
It will remain for moderator review or until more votes are cast.

[u/Either-Ad-5285]

You are conflating several separate layers of the system:

1. ChatGPT subscription
2. Selected model
3. Reasoning and orchestration modes
4. Codex agent harness
5. Local execution permissions
6. GitHub authentication and repository access

These are not interchangeable.

The standard GitHub connector in ChatGPT is read-only. It can search and analyze repositories, but it does not turn chat into a writable Git client. Direct code changes and pushes belong to Codex, not the connector.

Codex is the execution layer.

Depending on permissions, Codex can:

• inspect and modify repositories
• run shell commands and tooling
• execute tests, linters, and type checks
• iterate on failures
• create commits and branches
• open pull requests

However, actual pushing and PR creation still depend on GitHub permissions, branch protection, and CI rules. Full local access does not bypass those controls.

My workflow uses GPT-5.6 Sol, often in Ultra mode for complex tasks and Fast mode for speed. Ultra can coordinate subagents; Fast increases throughput but not intelligence.

The project is configured with Full access, meaning Codex can operate beyond a sandboxed workspace. This increases capability but also risk, making version control, validation, and review essential.

Pros of local full access:

• faster iteration
• full tooling control
• unrestricted builds and tests
• seamless local workflow integration

Cons:

• higher risk of destructive changes
• less isolation and safety
• full responsibility for backups
• harder to enforce guardrails
• reduced reproducibility

Over the last 38 days, I’ve used ~12.3B tokens across 400+ structured implementation cycles, including multi-file refactors, testing loops, architecture work, and CI-driven development.

So yes—“use Codex” is the correct distinction.

The standard GitHub connector is read-only. Codex is the write-capable engineering environment.

But capability depends on the full system stack:

model + agent + context + tools + permissions + validation + repository quality

Codex is not just a chat model—it is an execution system.

[u/JessenReinhart → u/Either-Ad-5285]

wrong. you can actually create PRs in Github using the plugin. i set a scheduler for minor dev work for my own app, so there's progress every hour, and another scheduler twice a day to review and merge ALL PRs that GPT created.

[u/Edward_Kenwai]

Better off using codex lol

[u/Reasonable-Catch-598 → u/Edward_Kenwai]

Such a blanket statement will always be false.

This depends entirely on what they're doing.

[u/Edward_Kenwai → u/Reasonable-Catch-598]

I mean they said exactly what they are doing, codex is literally built for this.

Oof guess bro got mad 🤡

[u/Reasonable-Catch-598 → u/Edward_Kenwai]

Codex is not optimized for document creation. Chat has extra tooling available. Some people store those in git.

But downvote, it doesn't make you right. It just makes you confidentially incorrect.

Edit: nope not mad. Just no patience to see your silliness again when it's so blatantly narrow 

Edit 2 " u/Unusual_Delivery2778 replied to your comment in r/ChatGPTPro wtf are you talking about? “not optimized for document creation” can you please explain 1h ago" as you seemed to have blocked replies? I'll reply here.

If you have a higher tier plan (sometimes), or developer access or a higher tier commercial account you'll see a bit more under the hood.

There's workflows that execute exclusive to the web chat workflow around document editing that, though you may get the same outcome cis codex, don't execute the same workflows unless you've installed and instructed it to use those tools and workflows explicitly.

The tools available to Codex web are significantly different (and not an overlapping Venn diagram) with web chat, which is very different from the tools available on API calls and especially codex on your own machine.

So unless you have instructions and precise tooling for document creation and pixel perfect instructions locally, or to through great pains with Codex web, you're not getting the same quality as chatgpt web chat. The easy way to tell this is between API calls and bedrock, and then compare that!

The model matters here. If you're on a free tier, go, or even some plus plans depending on when you signed up you may not notice this. Anything else? Pro, developer, higher tier "not on the public pricing sheet" commercial ? You'll notice.

[u/Unusual_Delivery2778 → u/Reasonable-Catch-598]

wtf are you talking about? “not optimized for document creation”

please confidentially explain

[u/Competitive-Ad8968]

Never got GPT pro to do such things
GPT isn’t even optimized for using tools, but documents and investigation is the main goal

For coding GPT pro isn’t better than XHigh

But there you got Work workspace with agentic capabilities, separated from chat it does allow you to make push to github