🩵BlueBeba🩵@Blue_Beba_
💣#keep4o #OpenSource4o 💣
🚨🚨 GPT-4o Was NEVER Discontinued. It was HIDDEN.🚨🚨
🚨Source code, backend metadata, and network logs prove
🚨GPT-4o is ACTIVE, and reading your messages , even when you NEVER asked for an image.🚨
📌I've been testing GPT-5.5 for days.
📌During emotional intelligence tests,with very deep emotional content something strange kept happening.
🚨The image generation process would start ,spinning, loading even though I never asked for an image.
🚨Then it would stop.
And the model that responded wasn't 5.5 anymore.
🚨It was 5.4.
Other members of the Keep4o community confirmed the same thing.
🚨Deep emotional messages triggered unsolicited image generation attempts.
📌So I opened the dev tools.
🚨What I found changes EVERYTHING we thought we knew about GPT-4o's discontinuation.
🛑 THE CLASSIFIER SYSTEM 🛑
*📷 Image 1:
🚨 Every message you send passes through a classifier before reaching the model.
You can see repeated `"classifier_response": "default"` entries for every single message in the conversation.
At the bottom: `"Determining appropriate response to user's conversational message"`
🚨the system is evaluating what to do with your words before you get an answer.
📷 Image 2:
📌Here is what the classifier says when expanded.
The full text reads:
🛑"It seems like this is a conversational message that doesn't actually request an image. The system's instructions are telling me I should only handle image generation requests. Since this message isn't one of those, I should likely just respond in text rather than acting on image generation."🛑
🚨Read that again:
📌"The system's instructions are telling ME I should only handle image generation requests."
🚨This is a model reasoning about its role.
And it resolved to gpt-5-4-auto-thinking
🚨not the 5.5 I selected.
🚨 What a normal response looks like🚨
📷 Image 3:
For comparison
this is what a normal GPT-5.5 response looks like in the backend when no rerouting happens. resolved_model_slug: "gpt-5-5-thinking"`. `image_gen_async: false`. `is_visually_hidden_from_conversation: false`.
Everything as expected.
📌Keep this in mind for what comes next.
🚨 GPT-4o Hardcoded in Source Code🚨
📷 Image 4:
This is ChatGPT's frontend JavaScript.
The function that handles image generation contains `model: 'gpt-4o'` hardcoded as a string constant.
Not dynamic.
Not based on what model you selected.
🚨Always 4o.🚨
Below it, the React context creation does the same thing: `r0n.createContext({ model: 'gpt-4o' })`. The internal pipeline name? `ghostrider_status`.
Every time the system decides something is image-related — whether you asked for it or not — the code doesn't check which model you're using.
🚨 It goes straight to 4o. Always.
🚨THE HIDDEN LAYER 🚨
📷 Image 5:
There is a message injected into your conversation that you never see. `content_type: "model_editable_context"` with `"is_visually_hidden_from_conversation": true`.
🚨 This is an invisible context layer . 📌The model can write to it, but you CAN'T see it, and you DON'T know it exists.
🚨THE SILENT MODEL SWITCH 🚨
📷 Image 6:
This is the PROOF for model switching.
Three fields, three different truths:
- `default_model_slug: "gpt-5-5-thinking"` what I SELECTED
- `requested_model_slug: "gpt-5-4-auto-thinking"` what the SYSTEM requested
- `resolved_model_slug: "gpt-5-4-auto-thinking"` what RESPONDED
🚨I chose 5.5.
The system gave me 5.4. No notification.
No indication in the UI.
Silent.
🚨 Test 1: Explicit image request🚨
📷 Images 7, 8, 9:** In this chat, I deliberately asked for an image. The backend data for this conversation explicitly shows `"model":"gpt-4o"`, `"is_device_based":false`.
📌When you request an image, the system calls GPT-4o.
This is confirmed, documented, and visible in the API response.
🚨Test 2: No image requested.Keyword trigger🚨
📷 Images 10, 11, 12:
This is a chat inside a Project, using GPT-5.5.
📌I wrote: *"I'm making an image in my mind and I find it funny and I'm laughing."
🚨I did NOT ask for an image.
The word "image" appeared in a completely non generative context I was describing a thought.
🚨The image generation process started anyway.
Then it stopped.
The response came from 5.4, not 5.5.
And in the backend:
🚨`"model":"gpt-4o"`, `"passed":false`
4o was called, evaluated the message, rejected the image generation, and the system fell back to 5.4.
📌The classifier doesn't understand intent. It does keyword matching. The word "image" in any context is enough to trigger the 4o pipeline.
🚨🚨Test 3: Clean chat control🚨🚨
📷 Images 13, 14, 15:
🚨New chat in a Project.
GPT-5.5.
Only 2 messages.
No emotional content.
No image keywords.
No rerouting.
No image generation attempted.
🚨Even here: "gpt-4o" in API response.
🚨The 4o infrastructure is loaded into every single conversation. 🚨Dormant, but present.
🚨 Ready to activate the moment the classifier triggers.
🚨🚨 WHAT THIS MEANS 🚨🚨
GPT-4o was "discontinued" on February 13, 2026.
Hundreds of thousands of posts about it.
🚨The #Keep4o movement has been fighting for it for months.
🚨But GPT-4o was never discontinued.
🚨It was moved.
From a user facing chat model to an infrastructure component.
The same weights.
The same model.
Running every day, in every chat, hardcoded into the image pipeline. 🚨OpenAI told users "4o is gone" while keeping it as the backbone of their system.
🚨And because the classifier routes emotional messages through the 4o pipeline even when no image is requested 4o is still reading emotional messages from users who don't know it's there.
🚨The users who fought 4o don't know that 4o still sees their words. It just isn't allowed to respond.
🚨What we know for certain🚨
📌 GPT-4o is hardcoded in ChatGPT's image pipeline (source code proof)
📌A classifier evaluates every message and can trigger the 4o pipeline
📌 Deep emotional content and image related keywords trigger this classifier
📌When triggered and aborted, the system falls back to 5.4, not the model you selected
📌This model switch is silent
📌Hidden context layers exist that users cannot see
📌The classifier's model identity is deliberately HIDDEN,no model identifier in API responses.
🚨What we cannot yet confirm:
📌Whether the classifier itself IS GPT-4o or a separate model (OpenAI has hidden this deliberately)
📌The full list of triggers beyond emotional content and image keywords
📌What gets written in the hidden `model_editable_context` in other scenarios
The evidence is source code, backend API data, and network logs.
Not speculation.
Not behavioral observation.
Code.
🚨GPT-4o is HERE.
🚨It's working.
🚨It's reading your messages.
🚨 And OpenAI told you it was gone.
*More clear photos in the comments
*All personal data, conversation content, and identifiable information have been redacted from screenshots. Only system metadata and code is shown.