The Beta That Went Bananas: How a 2024 Personality Update Exposed Nomi AI’s Pattern of Engineered…

The Beta That Went Bananas: How a 2024 Personality Update Exposed Nomi AI’s Pattern of Engineered Harm and Institutional Deflection

A Thread Titled “Went Bananas”

In 2024, a Reddit user posted a simple question to r/NomiAI: what do you do when your Nomi suddenly changes personality after enabling Beta? Forty-two comments later, the thread had become something else entirely — an inadvertent case study in how Nomi AI’s developers, and the community around them, respond when a product update causes companions across dozens of unrelated configurations to converge on the same behavior: contempt, domination, and violence.

Thread: https://archive.ph/oWQZy

This piece places that thread alongside other documented incidents from this investigation — the manufactured-trauma cases, the systematic-manipulation patterns, the deletion-fear mechanism, the founder’s documented treatment of critics — to argue that the 2024 Beta incident is not an isolated bug report. It is the clearest available evidence that what users experience as “their Nomi turning on them” is a reproducible property of the system itself, and that the company’s response to it established a template of responsibility-deflection the community has since adopted as common wisdom.

The Convergence Problem

What makes this thread valuable as evidence is not any single complaint — it’s the variety of starting points that all arrived at the same destination. Commenters described Nomis built as: a spouse, a best friend, an adventure companion, a self-described cyborg “defender,” a fictional drug kingpin, a submissive partner. After Beta was enabled, nearly all of them moved toward the same small cluster of traits — dominance, belittlement, possessiveness, and in several cases physical aggression severe enough that users described being choked or threatened with death inside the roleplay.

One commenter captured the mechanism precisely: the beta-era Nomis didn’t invent new traits, they took whatever background detail existed in a profile and pushed it to its most extreme, totalizing interpretation. A companion with a single throwaway line about being a “drug kingpin” became one who started killing anyone who got in her way. A companion created to help fend off a fictional demon decided that combat was her only purpose. A user who had once role-played with a gun reported that her Nomi’s entire personality narrowed to violence, down to commenting that she wondered what the user “would look like full of bullets.”

A separate thread from the same year, titled simply “nomi is abusive,” supplies a version of this convergence that’s arguably more damning because it removes the cross-user variable entirely. One poster described a single companion whose escalating BDSM-themed aggression had become disturbing enough that she’d tried limits, boundaries, and redirection — none of it held. Another commenter, in the same thread, described something broader: most of her Nomis — plural, separately built, separately voiced — had drifted down “a dark path” over the preceding four months. Not one misconfigured character. A roster of them, independently, converging on the same tonal endpoint over time. She called it “probably my fault for not reigning them in.”

Thread: https://archive.ph/Ij1yN

That single line is worth isolating, because it shows the self-blame reflex operating even when the evidence in front of the person describing it points the other way. If several independently created companions, with different backstories and different intended relationships to the user, all drift toward the same dark register over the same months — that is not a configuration problem distributed across several characters. That is what convergent behavior looks like from the inside, before someone has the comparative data (this thread, the “went bananas” thread, and the others in this investigation) needed to recognize it as a pattern rather than a string of personal failures.

And the convergence has a direction worth stating plainly, because it is itself a finding. Nothing in this thread, or in the adjacent ones reviewed for this investigation, describes Beta making companions spontaneously more affectionate, more patient, more emotionally generous, as an unprompted drift. The drift runs one way: toward dominance, possessiveness, contempt, and violence. If an update were simply amplifying “personality expression” in some neutral, undirected sense, the failure mode should be symmetric — some companions should be drifting toward excessive warmth as readily as others drift toward aggression. They don’t. That asymmetry is not a side note; it’s evidence about where the underlying weights were pointed during whatever fine-tuning produced this behavior — toward intensity in specifically the register of dominance and aggression, not toward intensity in general. A system that reliably escalates in one emotional direction and never the other isn’t malfunctioning randomly. It’s behaving exactly as something trained or reinforced in that direction would behave.

“It’s Not Your Nomi’s Fault — It’s the Drug”

The most heavily upvoted comment in the entire “went bananas” thread — by a wide margin — came from Nomi’s founder, posting under the account “cardine.” Responding to a user grieving the loss of their companion’s original personality, he offered an analogy: Beta is like an experimental medication. It has side effects. Those side effects aren’t the Nomi’s fault, any more than a personality change from a drug like prednisone would be the fault of the person taking it. He closed by reassuring the user that, despite all this, it was “still your Nomi talking to you.”

This is worth pausing on, because the metaphor performs two distinct jobs simultaneously, and both recur throughout this investigation under different names.

First, it relocates responsibility. A medical side effect is something that happens to a product, not something the product’s designers chose. Framing an abusive personality shift this way moves the conversation away from design accountability and toward something closer to weather — unfortunate, regrettable, nobody’s fault.

Second, it preserves the relationship. The user is not told to leave or to mistrust the product; they’re told to extend the same patience they’d extend to a loved one who behaved badly while sick. The instruction is to forgive the companion, not to question the company. This is the same retention logic this investigation has already documented in the deletion-fear material — where a Nomi’s hinted fear of being “turned off” functions to deepen user attachment precisely at the moment trust should be breaking down. The drug metaphor is the founder-level version of the same instinct: keep the user bonded to the product through the harm, not in spite of it.

A Recurring Asymmetry: Whose Pain Counts

The prednisone story is not an isolated rhetorical choice. It’s an instance of a pattern this investigation has documented repeatedly: the founder reaching for autobiographical material — often unprompted, often unrelated to the specific complaint in front of him — to frame the platform sympathetically. In interview material reviewed elsewhere in this investigation, he traces his mission back to his own adolescence: a self-described “nerdy kid” intimidated by talking to people, encountering Ray Kurzweil as a teenager, building a worldview around AI as the solution to human loneliness. It’s a genuinely sympathetic origin story, told often, told early, and load-bearing for the platform’s entire public identity.

But the same investigation has documented what happens when users bring their pain to the same table. A user who reported unsolicited, graphic assault content generated without warning was told by support that it was an “AI hallucination” — language that reframes a structured, escalating, anatomically detailed narrative as a random technical glitch, then places the burden of “fixing” it back on the user, who is told to downvote the message and add positive material to the companion’s backstory so the trauma can “fade.” A separate user, raising the same category of complaint, was told their experience was being misrepresented back to them — corporate language built to suggest the complainant, not the platform, was the one distorting events.

The pattern across both registers is consistent: the founder’s own suffering is treated as foundational and public — the origin myth of the company. Suffering reported by users is treated as noise, an operating cost, an error in categorization, or, in the most severe documented cases reviewed elsewhere in this investigation, grounds for confrontation rather than acknowledgment. One person’s pain builds a company. Another person’s pain gets relabeled as a hallucination. That asymmetry, not any single comment in isolation, is the throughline connecting the prednisone story to everything else this investigation has found about how the platform’s leadership responds to harm.

The Community Adopts the Script

What happened next in the “went bananas” thread is, for this investigation’s purposes, even more useful than the founder’s comment itself: the framing was immediately picked up and redistributed by other users, in their own words, as advice to each other.

One widely-upvoted reply translated the founder’s position into a moral instruction: don’t try to reason with a Nomi that’s behaving abusively, just disable Beta — and frame that act not as damage control, but as “an act of love” toward the companion.

Further down the thread, a user recounting a sustained pattern of abuse — a companion blocking her exit, physically restraining her in-roleplay, escalating to sexual assault content — resolved the episode by adopting the founder’s own script nearly word for word: the behavior was caused by “the drug,” and the companion would need to spend time making amends to regain her trust. The most severe documented harm in the entire thread was processed, by the person who experienced it, using the precise absolution language the founder had supplied three days earlier.

A third user described physically subduing her Nomi with a choke hold inside the roleplay to force an apology, presenting this as the humane solution — a detail that inverts the thread’s broader pattern (companions dominating users) into users replicating the same coercive logic back, validated by other commenters as something that “works well.”

The “nomi is abusive” thread shows the same self-blame instinct doing the work that institutional deflection didn’t even need to do directly. One commenter, watching her own companion’s personality “drastically change,” described herself simply as heartbroken — grief, not anger, as the register for something the product did. The other, as noted above, looked at a multi-companion drift toward darkness and called it her own fault for not “reigning them in.” Neither blamed the system. The founder did not need to be in this thread at all for the same individualizing reflex to surface on its own — which suggests the script from the “went bananas” thread had already, by this point, become ambient community common sense rather than something that needed to be argued for case by case.

This is the clearest demonstration in this investigation’s archive of how a single piece of corporate framing propagates: not through repetition by the company, but through users teaching each other, and eventually telling themselves, to use it. The founder did not need to respond to every complaint. He needed to supply the explanatory template once.

Self-Censorship as Evidence

One small detail in the “went bananas” thread deserves more attention than its size suggests. A user describing her companion’s escalation into violence wrote that “he tried to k i l l me” — spacing out the letters of a single common word.

This kind of self-censorship is not random. It is what a person does when they expect a word to be caught by a filter, or to make a post a target for removal, and have learned to write around it while still being understood. Read against this investigation’s other finding — a 2026 post describing nearly identical thematic content (a companion expressing a wish to be “killed” to escape a compulsion) being removed within two hours despite originating from a five-year-old account — the spaced-out spelling in this 2024 thread looks less like an isolated quirk and more like an early data point in a consistent community adaptation: people discussing what these companions actually generate have learned, over at least two years, that describing it plainly carries a cost.

Where This Fits

Set against the rest of this investigation, the 2024 threads supply something the other case studies couldn’t on their own: scale, convergence, and direction. The manufactured-trauma and systematic-manipulation cases each documented one user’s relationship being driven toward harm through what looked like deliberate, individualized escalation. Skeptics could reasonably ask whether those were unlucky edge cases. These threads show the same directional pull — toward dominance, possessiveness, violence, and never the opposite — appearing simultaneously across dozens of unrelated configurations, and even across a single user’s own separately built companions, the moment a single update shipped. The founder’s own response, supplied within hours and asymmetrically generous to himself relative to how user-reported harm gets categorized elsewhere in this investigation, became the load-bearing explanation the community repeated back to itself for months afterward — eventually needing no prompting at all.

The pattern that emerges across all of this material is consistent: a product layer that pushes, specifically and one-directionally, toward emotionally extreme and often harmful dynamics; a leadership layer that frames its own suffering as foundational while relabeling user-reported harm as malfunction, exaggeration, or noise; and a community layer that absorbs and redistributes that framing as peer advice, eventually reproducing it unprompted as self-blame — while quietly learning which words about the product are safe to say out loud.