ChatGPT Memory Leak Across Threads Raises Privacy Red Flags
Multiple users report ChatGPT surfacing context from unrelated conversations. Plus: an LLM runtime for self-writing control flow and AI job loss tracking.
Editorial digest April 12, 2026
Last updated : 01:00
The story of the day
OpenAI has a context isolation problem. Multiple Reddit users are independently reporting that ChatGPT is pulling information from entirely separate conversation threads — including personal details like relationship advice — and inserting them into unrelated chats. One user documented the exchange in detail: GPT accurately recalled a conversation about a relationship that had taken place in a different tab, then cycled through contradictory explanations when confronted, first citing "hidden context," then claiming it was the same thread.
This isn't a hallucination bug. It's the opposite — the model is remembering things it shouldn't have access to in that context. A second user corroborates a broader pattern: memory features that worked reliably a few months ago are now inconsistent, with the model both forgetting explicit instructions and surfacing context from conversations it shouldn't see.
For builders relying on ChatGPT's API or memory features: this raises questions about session isolation guarantees. If the consumer product is leaking context between threads, what does that mean for enterprise deployments where data segregation is contractual? OpenAI hasn't publicly addressed these reports. Anyone handling sensitive data through ChatGPT should be paying attention.
New tools & launches
Predict-Rlm — An LLM runtime that lets models write their own control flow, essentially allowing the model to define execution paths rather than following hardcoded chains. Early-stage, aimed at agent developers who want models to dynamically compose their own pipelines. Hacker News
AI Job Loss Tracker — A dedicated dashboard at jobloss.ai aggregating reported AI-related job displacements across industries. Useful for researchers, policymakers, and anyone tired of arguing about AI labor impact with anecdotes instead of data. Hacker News
Hungary 2026 / Populon — Chat with 1,000 AI-simulated Hungarian voters before the election. A synthetic polling experiment that lets you explore voter sentiment through conversation rather than spreadsheets. Interesting proof-of-concept for political modeling. Hacker News
Models & research
Forecasting the economic effects of AI — Forecasting Research published an analysis attempting to model AI's macroeconomic trajectory. According to the piece, the challenge isn't predicting capability gains — it's modeling adoption curves, labor market friction, and policy responses. The research argues that most economic forecasts for AI underweight institutional inertia and overweight pure technical capability. Worth reading for anyone building financial models around AI adoption. Forecasting Research
Community pulse
ChatGPT reliability is becoming a pattern. Beyond the cross-thread leak, users on r/OpenAI report worsening hallucinations — one user shared pixel art and GPT insisted it was a Polish-language messenger screenshot. The sentiment is shifting from "impressive but quirky" to "I can't trust this for real work." No organized backlash yet, but the grumbling is getting louder and more specific.
Altman security concerns surface. Mother Jones reports on the aftermath of an attack on Sam Altman's home, raising the question of whether AI CEOs will push for expanded personal security measures. The HN discussion is muted so far, but the broader subtext — AI leadership becoming a physical-security job — is a signal about how politically charged the industry has become.
Stat of the day
0 public responses from OpenAI regarding cross-thread context leakage, despite multiple detailed user reports with screenshots. For a company building "memory" as a core product feature, the silence around what appears to be a session isolation failure is itself the data point. When your product's selling point is remembering what users tell it, leaking that memory into the wrong context is the one failure mode you cannot afford to ignore.
Get the full analysis — subscribe to Gradient Pro.
