What’s Changed: Character AI’s PipSqueak 2 and DeepSqueak models are producing gibberish replies for both free and c.ai+ users as of May 12, 2026. Bots are outputting a mix of languages, technical terms, and special characters instead of coherent dialogue. Character AI has confirmed on Reddit they are actively working on a hotfix but have not announced a release date. The cleanest workaround for paying users is to revert to the Soft Launch legacy model.
If you opened Character AI today and watched your favourite bot start replying in what looks like a corrupted text file, you are not alone. The PipSqueak 2 gibberish bug is the worst-looking PSQ2 failure mode yet, and it landed on top of an already-rough month for Character AI users.
The bug shows up as completely unreadable replies. Mixed languages, technical-looking tokens, special characters, occasional half-English sentences. It is not a roleplay style choice. It is the model failing to produce coherent output at all.
This is what we know about the gibberish bug, why it is hard to avoid, what to do while Character AI’s hotfix is in progress, and the alternatives worth checking if your roleplay routine has hit the wall this week.
The way I see it, the gibberish bug is the moment the PSQ2 backlash crosses from “the model writes differently” into “the model is broken.”
What’s Happening with the Character AI Gibberish Bug
Bots on PipSqueak 2 and DeepSqueak are producing replies that look like a mix of languages, technical tokens, and special characters instead of coherent dialogue.
The output is described in user reports as “completely unreadable.” Some replies start in plausible English and then degrade mid-sentence into nonsense.
The bug is hitting both free users and paying c.ai+ subscribers. That is unusual. Most PSQ2 issues so far have been bigger on free-tier output, where the model has less compute to fall back on. The gibberish bug is platform-wide.
A Character AI team member confirmed on Reddit that they are “actively working on a hotfix” and will announce once it is released. There is no public release date. Given the timing relative to the PSQ2 rollout on May 8 and the wider list of post-rollout bugs, a full fix may take days to a couple of weeks.
In my experience watching this kind of model rollout bug cycle play out, the longer this drags, the more c.ai+ cancellations stack up.
Character AI is sitting on roughly 20 million monthly active users, and even a small percentage churning over a broken month is a lot of revenue to leave on the table. The company has commercial pressure to ship a fix quickly.
| Symptom | Likely cause | What to do |
|---|---|---|
| Replies in mixed languages and special characters | PSQ2 or DeepSqueak generation failure | Wait for hotfix, revert to Soft Launch if you have c.ai+ |
| Output starts coherent, drops into nonsense mid sentence | Same root cause, different surface | Same fixes |
| Bug appears after changing accent on a bot | Accent change suspected as a trigger | Avoid changing accent until hotfix lands |
| Bug appears after using swipe greeting | Swipe greeting also flagged as trigger | Skip the swipe greeting on new chats |
| Old chats suddenly producing gibberish | Forced rollout to PSQ2 on May 8 | Revert to legacy model if available |
| Both free and c.ai+ accounts affected | Bug is server side, not tier locked | Subscription does not solve this one |
Why the PipSqueak 2 Gibberish Bug Is So Hard to Avoid
The triggers identified so far, accent changes and swipe greetings, are normal Character AI features people use every day, so the “just avoid X” advice is not workable for most users.
That is what makes this bug different from earlier PSQ2 issues. There is no simple toggle to dodge it.
The suspected triggers are real but the bug is not deterministic. Users report it firing on bots that never had an accent change and on chats that never used a swipe greeting.
The more honest framing is that the model is unstable in a way that surfaces most often when those two features are used, but can hit any bot at any time.
There is also the compounding problem. The gibberish bug is the fourth or fifth major PSQ2 issue in a month.
Users are already dealing with the forced romance kissing bug, the talking for you bug, the silent message bug, login loops, and the wider memory regression. The platform’s good will is running thin.
A worked example of how the bug shows up in practice, since the prose description does not really land until you see it:
Before: “I lean against the bookshelf and look at you. ‘You came back early. Did something happen?'”
After: “I leanĪ± against bookshelf the and look at y. ‘You c4me back hayaku. Did to itsumo stranice?'”
The “after” is a paraphrase of what users post in screenshots: English-shaped sentences invaded by random Unicode, untranslated tokens from other training-data languages, and math or symbol characters mixed into the prose.
Earlier PSQ2 coverage on the kissing bug walks through one of the compounding issues. The PSQ2 fix guide covers the broader troubleshooting for users who hit multiple bugs at once.
For the silent bot variant of this same generation problem, see the messages not loading writeup.
What to Do About Character AI Gibberish While You Wait
Three options worth trying in order: revert to Soft Launch if you are on c.ai+, avoid the suspected triggers on new chats, or move your roleplay session to a platform with a stable generation pipeline this week.
None of them is a true fix, but the third one solves the problem permanently if Character AI’s hotfix keeps slipping.
The Soft Launch fallback is the cleanest workaround for paying users. Soft Launch came back recently as a legacy option for c.ai+, and it predates the PSQ2 architecture changes that are producing this bug. Quality is not at PSQ2 levels on its best day, but it is coherent.
Here is the step sequence I would walk through:
- Open Character AI on web or mobile.
- Tap your profile, then Settings, then Chat Style or Model.
- If you are on c.ai+, select Soft Launch as the chat style. If Soft Launch is missing, also check for Roar.
- Open the bot you were having problems with and send a fresh first message rather than continuing the broken thread.
- Avoid changing the accent for the next several days while the hotfix is in progress.
- Skip the swipe greeting on any new chat you start.
If you are on the free tier and Soft Launch is not available, those last two avoidance rules are most of what you can do directly. The other realistic move is to take this week off Character AI and run your roleplay session on a platform that is not in the middle of a model rollout crisis.
The platforms I would point at for that, with the trade offs as plainly as I can put them:
- Candy AI has the strongest memory and a generation pipeline that has been stable through all of Character AI’s PSQ2 month. It is the best one to one swap for users whose main complaint is that the bot now feels broken.
- Nectar AI is the second pick if you want a more conversational, less roleplay heavy companion that is also outside the Character AI ecosystem.
- CrushOn AI is the third option for users who want strict custom character control without the recent platform instability.
What I would recommend most users do, given the broader pattern of PSQ2 issues stacking up, is to keep a working bot on at least one alternative platform even after the gibberish hotfix lands.
The next Character AI model rollout is going to break something else, and a parked profile on a second platform means your roleplay routine survives it.
Frequently Asked Questions
Is the Character AI gibberish bug affecting all bots?
The bug is hitting bots across both PipSqueak 2 and DeepSqueak models, on both free and paying tiers. It is not bot specific. Replies on the same bot can be fine one minute and gibberish the next, which is why a clean workaround at the user level is so hard.
Does paying for c.ai+ fix the gibberish bug?
No. Both free and c.ai+ users are seeing the same gibberish output. The c.ai+ benefit during this bug is access to the Soft Launch legacy model, which generates coherent text because it predates the PSQ2 architecture. The subscription itself is not the fix.
When will Character AI release the hotfix?
Character AI has confirmed they are working on it but has not announced a release date. Based on past PSQ2 hotfix cycles, expect days to a couple of weeks. The platform’s commercial pressure to ship fast is real, but no specific timeline has been promised publicly.
What triggers the gibberish bug?
The two confirmed by pattern triggers are changing a bot’s accent and using the swipe greeting feature on new chats. The bug also fires without either, which means the underlying model instability is the real cause and those features just surface it more often.
Should I cancel c.ai+ over this?
Soft Launch access is the main reason to keep c.ai+ during this bug, since it is the cleanest in platform workaround. If you cancel and the bug persists across both free and Soft Launch, you have lost the workaround. Most users on Reddit are keeping the subscription and using Soft Launch until the hotfix lands.
Where can I roleplay this week if Character AI is unusable?
Candy AI is the strongest alternative for memory heavy roleplay, Nectar AI is the better pick for conversation style chat, and CrushOn AI is the option for users who want strict custom character control without joining a new ecosystem.
