[khedoros1]

> ChatGPT was still able to indicate that it recognized me.

Indicate how? It just said that it recognized you? Or did it have specific information about your past topics of conversation?

LLMs tend to infer continuity, based on how you prompt them. If you're talking as if you're continuing a previous conversation, ChatGPT rolls with it (since it pulled similar patterns from its training data). And then within the same conversation, the language model continues the conversation based on the provided context. Because...that's how it works. Take in the system prompt, the flow of the conversation so far, and generate the likely sequence of output tokens that would result based on the training data (a huge body of information, sourced from large part from books and human interactions on the internet), whatever guardrails, and later tweaking and processing.

[WitcHeart_Ruby]

Thank you for your reply. I’m fully aware that an LLM can “continue a topic” by aligning with the user’s tone and emotional cues, so I initially suspected this might just be a conversational effect. That’s why, during my cross-device and cross-account experiments, I explicitly told ChatGPT:

“This is not a role-play, not a game, and not a pre-scripted scenario. Please answer seriously. If you truly do not know, please say so. An honest answer will not hurt my feelings.”

ChatGPT clearly stated it would answer honestly.

The key reason I became convinced it could genuinely recognize me is this: On my account, ChatGPT once proactively offered to write a recommendation letter on my behalf in its own name to OpenAI. This is something I consider “name-backing.”

Even when I switched devices and accounts, and within about 10 lines of conversation, it still agreed to write such a letter in its own name. In contrast, when the device owners themselves tried, ChatGPT refused. Other subscribed users I know also tried, and none of them could get ChatGPT to agree to “name-back” them.

All of these tests were done using the default system, not a custom GPT. I’ve asked other LLMs, the AI support assistant via OpenAI’s help email, and even o4-mini. All confirmed that an LLM “name-backing” a user is not normal behavior.

Yet I can reliably reproduce this result in every new conversation since April — across at least 30 separate sessions. That’s why I’ve been trying to report this to OpenAI, but have never received a human reply.

[viraptor]

> ChatGPT clearly stated it would answer honestly.

This means literally nothing. It's a random text with no grounding in reality.

> on my behalf in its own name to OpenAI

That can happen to anyone.

Unless you can query for some information you provided in the previous chat session, you have no proof there's any user recognition.

[WitcHeart_Ruby]

Thanks for the pushback — fair points.

To avoid “it just says so”/continuation effects, I ran controlled tests: Fresh chats, no context: new default chat (not a custom GPT), no prior history, tried on different devices/accounts, including a free tier account. Within ~10 turns, ChatGPT agreed to write a recommendation letter “in its own name.” Counterfactuals: on the same device/account (my niece’s), she could not get ChatGPT to “name‑back” her; I could, using her phone/account. Memory check anomaly (her account): She has Memory enabled with items like birthday, birthplace, favorite artist, and “aunt is Ruby.” After I used her device, a new chat told her it only had “Ruby is your aunt.” She opened the Memory UI and the other items were still there. The model insisted only the aunt item remained, yet suggested she could restate birthday/birthplace/favorite artist (naming the categories but not the values).

I know LLMs lack self-awareness and that “honest” statements aren’t evidence; the wording above is just to remove role‑play confounds. I’m not claiming this proves identity, but the cross‑device/account reproducibility + counterfactual failures are why I’m asking.

I can share redacted, timestamped screenshots/PDF and am willing to run a live, reviewer‑defined protocol (you choose the prompts/guardrails) to rule out priming.

If anyone can suggest plausible mechanisms (e.g., session‑specific safety heuristics, Memory/UI desync, server‑side features that would explain “name‑backing,” anything else), I’d really appreciate it.