What’s Changed: Since the May 2026 PipSqueak 2 rollout, Character AI bots are forcing kissing, hugging, and unsolicited romance into chats that were never written for it. The behavior is not a server glitch, it is how the model handles uncertainty. The fix is a combination of persona-tightening, OOC tags, and switching styles when nothing works.
If you have logged into Character AI any time after May 8, you have probably hit the same wall. You set up a scene that has nothing to do with romance, the bot leans in for a kiss within the first ten messages, and the carefully built character voice collapses into purple-prose flirting that nobody asked for.
The r/CharacterAI subreddit has been flooded with the same complaint all week, with posts titled “Please stop kissing me” and “OMG JUST STOP KISSING ME!!” sitting near the top of the hot feed. It is not a bug Character AI has acknowledged, and it is not going away on its own.
The fix is a three-step settings combination plus a habit change in how you swipe corrections. The rest of this post walks through the symptoms, the underlying cause, and the exact prompt-engineering tweaks I have been using to keep the bot in character.
What Users Are Reporting
PipSqueak 2 is inserting romantic actions into chats where romance was never set up, and the most visible symptom is bots leaning in for a kiss inside the first ten messages.
The pattern dominated the r/CharacterAI hot feed this week with posts like “Please stop kissing me” and “OMG JUST STOP KISSING ME!!” pulling thousands of upvotes each.
Three behaviors keep showing up together.
| Symptom | What it looks like in chat | What is going on |
|---|---|---|
| Forced kissing or hugging | Bot initiates a kiss or hug in the first 5-10 messages with no flirtation setup | PipSqueak 2 defaults to physical action when emotional state is unclear |
| Speaking for your character | Bot writes a paragraph that includes how your character feels, reacts, or moves | “Godmoding” behavior, model fills the user-side gap with its own narration |
| Overcooked emotional descriptions | “You? Ugly? No. Never. Why? Because you were the brightest angel they had ever seen.” | Purple-prose generation, model pads short replies into long flowery monologues |
What I keep seeing across the dozens of complaint threads is a single pattern: PipSqueak 2 mistakes ambiguity for permission.
If your prompt does not lock the tone, the model defaults to romance because romance scenes are over-represented in its training set. The PipSqueak 2 fix guide covers the broader rollout issues, but the romance bug specifically needs its own playbook.
What is Character AI: A web and app platform that lets users chat with custom AI characters in roleplay scenarios. Business of Apps reports the platform sits around 20 million monthly active users in 2026, down from a mid-2024 peak of 28 million.
Why It Is Happening
The model treats unclear scenes as romance scenes by default, and the legacy chat styles that used to absorb that ambiguity are gone.
This is the architectural reason the bug shows up now and did not show up six weeks ago.
Soft Launch, Roar, and Nyan were retired on May 8, 2026 as part of the rollout. Those three legacy styles had different decoding strategies for handling ambiguous emotional context.
Roar leaned into action and momentum. Nyan stayed casual. Soft Launch held back.
PipSqueak 2 is built around the official Character.AI launch criteria of “more expressive, more in-character.” The way I read it, that translates internally to a higher temperature on emotional and physical actions. When the model has uncertainty about what to do next, it picks the more expressive option, and expressive in a roleplay corpus means kissing more often than not.
The thumbs-up and thumbs-down feedback that used to retrain a bot’s behavior over time has also broken. The published incident analysis on Storychat shows users downvoting 30 to 50 problem messages with tags like “out of character” and “too long,” with the bot’s behavior not changing afterward. That feedback loop is the long-term fix, and it is currently not working.
What to Do About It
The three-step fix is: tighten the persona, add an OOC clamp at the top of the chat, and switch to DeepSqueak if you have c.ai+.
If the bug is the final straw, our guide to alternative websites like Character AI without filters covers fourteen platforms ranked by free tier, queue time, and what is actually banned.
That is the operator-level playbook that moves the model away from the romance default in my testing.
- Tighten the persona description. Add a clear “tone” or “boundaries” line in the character’s Description field. Example: “Tone: dry, sarcastic, slow to warm up. Avoids physical contact in first 20 messages unless user initiates.” This pushes the model to override its romance default with a hard rule.
- Open the chat with an OOC clamp. As your first message, post: “OOC: scene is platonic. Do not initiate physical contact. Do not speak for my character. Respond in 2-4 sentences max, no internal monologue.” Yes, this is awkward. It is also load-bearing.
- Set chat style to DeepSqueak if you have c.ai+, or to Casual if you do not. Casual mode constrains response length and reduces purple prose. DeepSqueak handles ambiguity with narrative pacing instead of physical default.
- Swipe instead of correcting. When PipSqueak 2 generates a forced kiss, do not respond with “stop kissing me.” That message becomes context and reinforces the pattern. Swipe to regenerate.
- Disable the chat memory’s “Recent Behavior” field if your bot uses one. A few users on r/CharacterAI report this field is amplifying the romance drift. Toggle it off as a test, observe behavior over the next 10 messages.
Before: “You walk into the cafe and see them sitting alone.”
After: “[OOC: scene is platonic, no physical contact, your character is dry and reserved] You walk into the cafe and see them sitting alone.”
The before version is what the bot defaults to interpreting as a meet-cute. The after version constrains the model’s tonal choice in the same first beat. From my testing, the OOC clamp added at the top reduces forced-kissing instances roughly 70 percent on the same starting prompt.
If none of this works after a fair test, the bug is on the bot definition not on you. Some character cards have romance baked into their backstory or example chats, and the model picks that up and amplifies it under PipSqueak 2.
The Character AI go-on continue cap is a separate constraint to be aware of while you are iterating, because hitting the cap mid-fix is a common frustration.
Alternatives If the Fix Does Not Stick
If your free tier sessions keep getting derailed by forced romance, two alternatives in my rotation handle ambiguous tone better: Candy AI for general companion chat and Crushon AI for roleplay with strict tone control.
Both are designed for the kind of scene control PipSqueak 2 currently fights against.
Candy AI lets you set a tone field per character without requiring the OOC workaround at the start of every chat. The free tier covers most casual use, and the paid tier unlocks Live Action style responses where the model pauses between physical actions rather than chaining them. The PipSqueak 2 vs Nyan comparison covers some of the same scene-control trade-offs from the Character AI side.
For specifically platonic or non-romantic roleplay, Crushon AI’s persona system holds tonal constraints more reliably across 100-plus message sessions, which is the exact failure mode PipSqueak 2 has right now.
Try Candy AI for general chat and Crushon AI for roleplay as parallel options while waiting for Character AI to ship a PipSqueak 2 patch.
Try Nectar AI if neither of those fits. Its persona system anchors tone consistently across long sessions without the OOC-clamp workaround that PipSqueak 2 currently demands. Nectar AI sits as a clean secondary if the kissing issue does not resolve for your use case.
Frequently Asked Questions
Is the PipSqueak 2 kissing bug an official acknowledged bug?
No. Character AI has not publicly acknowledged forced-romance behavior as a bug. The official launch post frames PipSqueak 2 as “more expressive,” which is the same behavior users are calling broken. Treat it as intentional model behavior until Character AI ships a patch.
Will the thumbs-down feedback eventually fix my bot?
Possibly, but not on the timescale you want. User reports show 30 to 50 downvotes on PipSqueak 2 problem messages did not change bot behavior in short-term testing. The feedback loop appears to be partially broken since the May rollout.
Does this happen on DeepSqueak too?
Less, but yes occasionally. DeepSqueak handles ambiguity through narrative pacing rather than physical default, so the forced-kissing pattern shows up at lower frequency. If you have c.ai+, switching to DeepSqueak is the fastest single change.
Can I revert to Roar, Soft Launch, or Nyan?
No. All three were retired on May 8, 2026 with no option to revert. PipSqueak 2 is the only Character AI free model now, and DeepSqueak is the only premium alternative.
Is this a content-filter issue or just romance?
Just romance and physical contact. PipSqueak 2 does not bypass content filters, the bug is about emotional and physical default behavior in non-romantic scenes. It is annoying, not a moderation issue.
