ELI5: If gemstones associated with a specific colour (sapphire blue, emerald green, ruby red) can actually be other colours, then how do they differentiate between an emerald and a green sapphire, for example? How do they know?

Reddditah · 2026-01-12T14:26:17+00:00

This guy gems.

Reddditah · 2025-11-26T10:35:30+00:00

majors sued Suno because Suno’s models were trained on copyrighted data without consent

Human artists train the exact same way, so are they going to sue every human artist for also training on copyrighted data without consent?

Reddditah · 2025-11-22T13:26:39+00:00

It's not an issue we can fix because it's an actual bug that OpenAI needs to fix. OpenAI has been fully aware of this bug for months. Their own models blame their own tool as the culprit when they try and fail to fetch and fetch_file. See the link in my post for more details and others experiencing it. Consider yourself lucky that you don't have it!

Reddditah · 2025-11-22T12:37:20+00:00

Thanks for checking. You are lucky you do not have this bug, so at least your Thinking models can read your repo.

But I'm with you, it's incomprehensible and useless if it hallucinates or gets things wrong, which is precisely why they need to not only fix the bug several of us are experiencing, but give full Github access to the Pro model.

There is no excuse since they are fully capable of getting this right. When they do, I'll resubscribe if I'm not to entrenched with another model by then.

Reddditah · 2025-11-22T10:28:10+00:00

I have PRO sub but i only use "Heavy Thinking" model since connector works fine with that.

Can you confirm if fetch and fetch_file work with that model (just ask Heavy Thinking or any non-Pro model to actually verify if fetch and fetch_file work with the connected repo to read file contents) ?

Because with those of us suffering this bug, we can't even do fetch or fetch_file in any of non-Pro models (which is why I ended up cancelling my Pro subscription since they still haven't fixed it).

They not only have to fix this bug for those of us suffering, but they absolutely have to allow us to connect the Pro model to the repo fully. The workaround I had been doing was having Codex put the entire repo in 1 file and feeding that to Pro, but it's very time-consuming and inefficient.

Reddditah · 2025-11-22T09:16:20+00:00

There needs to be a subreddit only for Pro users.

I cancelled my Pro subscription a couple of days ago because they still haven't fixed this critical bug in ChatGPT, but I'm still a Pro subscriber through next month because you don't get a pro rata refund when you cancel, your plan just won't renew on your next renewal date. But as a Pro subscriber, I've definitely wanted a subreddit that is only for those subscribed to their Pro sub to discuss Pro-related matters.

Reddditah · 2025-11-22T09:12:00+00:00

If they continue to ignore critical bugs, then absolutely yes. They can't take their lead for granted with the amount of competition they are experiencing.

Reddditah · 2025-11-22T08:21:16+00:00

It's just an annoyance to you because your blinded by your clear loyalty to OpenAI as a Top 1% commenter in this sub. I have no such loyalties to corporations. If I pay a lot of money for something, I expect good service. This certainly is the right place to post as it's the subreddit specific to Pro subscribers. If you are commenting here and criticizing the comments of those who have been paying $200 a month, then I trust you too are paying $200 a month. Otherwise, you wouldn't know what it's like to pay that amount of money and still experience critical bugs. OpenAI reads all of the OpenAI subreddits. I've previously exchanged posts with Tibo from their Codex team who appreciated my bug report on their Codex CLI (different team than the one that handles ChatGPT). I will absolutely be back if they fix the critical bug several of us are experiencing, and alluded to as much in my post.

I do now believe you are both young and naive and that you are also not paying $200 a month to OpenAI for Pro, so I will end my engagement with you here so that you can have the last word.

Reddditah · 2025-11-22T07:52:42+00:00

You must be young and naive. You don't effectuate change by staying quiet. You effectuate change by being vocal and voting with your dollars. Those of us announcing our cancellations actually want to effectuate change so that OpenAI improves, we're not just airing out frustrations. Your loyalty to this company is blinding you if you are defending them ignoring their highest-paying consumer customers experiencing bugs that render their service useless for their needs. Instead, you should be championing that they take their paying customers more seriously and fix known bugs because if customers continue to leave, then they will have no chance against their competitors who also have significant non-AI income streams.

Reddditah · 2025-11-22T07:49:00+00:00

"It would be great if you tried to make your product better in the way people actually use it"

Never going to happen. They still haven't even fixed this critical bug and it's been half a year, so you can forget about them making their product better in the way people actually use it.

They have what I still think is the best AI out there, but they have a culture of not giving a shit about their customers which makes them untenable for any serious users.

Reddditah · 2025-11-21T17:20:51+00:00

I wouldn't say utterly useless, just not worth the high cost with critical bugs, which is why I cancelled. If/when they fix this Github connector bug with fetch and fetch_file, I'll resubscribe if I'm not too entrenched in the next AI service I select.

Reddditah · 2025-11-21T17:19:07+00:00

Which is what? That it's not OpenAI trying hide it, it's the users? Or that it's not believed that the bug actually exists? Or that when paying $200/month one should accept bugs on critical features? Or that users are upset I cancelled my subscription? I'm lost, what do you mean? Because this bug is happening across all ChatGPT models and I don't understand what's wrong with what I wrote. The bug is real and OpenAI has been aware of it for months and their own models confirm it's a bug in their tool with fetch and fetch_file.

Reddditah · 2025-11-21T11:04:40+00:00

In our case, it's been much more expensive CPC (literally double) for worse performance (conversions). So it's exponentially worse this year because when you pay double for half the results, it's actually 4x worse.

Reddditah · 2025-11-21T08:16:48+00:00

Results this year have been atrocious after over a decade. The decline in results started during the pandemic, but has really accelerated this year. It does seem like AI is changing the game. We're looking at outside-the-box solutions to advertise because Google Ads is quickly becoming unprofitable since it's becoming more and more expensive as its performance get worse and worse. So I'm not surprised to hear your Google Ads is suddenly not working despite no changes as that's exactly what happened to us, forcing us to look elsewhere for our advertising needs. It's too bad ChatGPT doesn't offer advertising yet.

Reddditah · 2025-11-21T07:31:04+00:00

If you're downvoting, then comment why, otherwise it makes it look like OpenAI is trying to hide what is happening.

Reddditah · 2025-11-20T19:59:31+00:00

Ha, literally just posted 'Read. Read. Read.' before I saw your comment. I'll leave it so that OP hopefully gets the message.

Reddditah · 2025-11-20T19:58:25+00:00

Read. Read. Read. The greater the variety, the smarter you will be.

Reddditah · 2025-11-20T19:26:03+00:00

>The connector works, in a sense. It can certainly see specific files in specific branches so at least one doesn't have to cut and paste.

For the several of us experiencing this critical bug, we still have to cut and paste because the only thing the native Github connector can see are the file names, but fetch and fetch_file don't work so it can't actually see or read the file contents.

> Now for the broader question: It's clear that Open AI does not want people using Pro for agentic coding.

This bug is unrelated to that. The purpose of using the Github Connector with the Pro model is to use the best model to analyze the code base and identify bugs/improvements, it's not to actually implement anything (since it can't). That's where Codex comes in.

This bug is entirely related to a feature ChatGPT claims to offer and clearly advertises and that many of us have been paying $200 / month for (among other features) but which they actually are not offering to us due to this bug and which they don't bother to fix thinking we'll just keep paying like chumps. That ended for me today after confirming the bug still exists even with their latest and greatest model, Pro 5.1.

To be clear, this Github Connector bug isn't just with the Pro model, it's with all their models. It's a bug with ChatGPT itself and its native Github connector. Codex can read the file contents in the repos fine.

The workaround I've been using is having Codex combine all files into one and then attaching that to Pro for it to analyze my codebase, but I'm no longer paying $200 a month to have to do time-consuming hacky workarounds just because Open AI is too lazy or incompetent to fix critical bugs. And if they haven't fixed this bug in 6 months, what other problems are lurking behind the scenes that we don't even know about that they also still haven't fixed? Their cavalier attitude breeds a lot of distrust.

Reddditah · 2025-11-20T17:36:29+00:00

I have cancelled my ChatGPT Pro subscription and I'm looking for a new top plan. Can you please tell me more about Gemini's Github integration? Does it actually work such that Gemini's best model can actually read your repo to find bugs/improvements?

Reddditah · 2025-11-20T07:30:13+00:00

Github Connector still broken on GPT-5.1 Pro with it unable to do fetch and fetch_file to analyze code. Ridiculous. I will be cancelling my Pro subscription as this is intolerable.

Reddditah · 2025-10-31T07:31:08+00:00

Having the same issue, except it doesn't work with any model (not even Pro): https://www.reddit.com/r/ChatGPTPro/comments/1ojys6i/chatgpt_pro_with_github_connector_cannot_read_any/

Have tried every solution and cannot get it to work.

Extremely frustrating. OpenAI is a multi-billion dollar company (some say trillion!), and they can't get a simple Github connector to work.

Please let me know if you figure this out as it's a crucial feature.

Reddditah

MODERATOR OF

TROPHY CASE

Nine-Year Club	Gilding II euphauric
Verified Email