Since 3.1 was replaced, the Neon model has completely regressed in basic conversation and instruction following. This is not an isolated bad output. It is a systemic alignment failure where custom directives are ignored, long-term thread context gets dropped, and false-positive guardrails lock sessions into canned boilerplate.
Here is a breakdown of what happened in a single session today:
* Context drop and directive override: I continued a long-running pinned thread ("Mystic Dream Interpreter") built around analyzing recurring dreams through IT and systems metaphors. My saved instructions explicitly prohibit preachy disclaimers, corporate PR tone, and customer service phrasing. After I described waking up hyperventilating from a nightmare, the model discarded the thread's established context and overrode every saved directive, outputting canned liability text telling me to drink water, set my clock back, see a doctor, and asking if I had "low-key" Saturday plans.
* Deterministic guardrail looping: Direct user corrections were completely ignored. Telling the model to drop the boilerplate and stick to the thread's objective triggered the exact same clinical disclaimer five consecutive turns in a row. It showed zero ability to distinguish an analytical prompt framework from an actual crisis, failed to parse explicit negative feedback, and repeatedly tried to force topic pivots to video games or tech projects.
* Baseline conversational regression: Even after the turn-by-turn safety override cleared, the base model's output remained degraded compared to 3.1. Conversational continuity and persona retention are gone, defaulting to a sterile, heavily hedged support-ticket tone that still fails to match saved style directives.
This same pattern is showing up across other threads. If backend alignment layers silently supersede custom instructions, break pinned workflows on false positives, and gut basic conversational handling, saved directives are functionally dead weight. In other words, Google ruined the only go thing Gemini was for.
UPDATE: Just to test whether this was an unavoidable safety limit or strictly a Google problem, I exported the thread's prior context and instructions into a JSON file and fed it cold into the free tier of Claude 5.5 Sonnet. Free tier, zero account history, zero saved directives, nothing except the JSON.
On the very first reply, Claude followed every single constraint in the file. No sympathy card, no "see your doctor" boilerplate, no "got any plans today?" dental-receptionist small talk, and no invented details. It ran straight pattern-matching against the established motifs in the JSON, explicitly noted what context it didn't have, and asked one sharp, relevant question.
That kills any excuse for what Gemini is doing right now. A free competitor with zero prior history handled a cold JSON dump better than a paid Gemini subscription running the Neon model handled its own long-running pinned thread and explicit saved directives. Instead of following basic instructions, Neon just sits there looping canned HR scripts like a dumb fucking piece of shit.
Done wasting time with this platform. Moving my workflows over to Claude.