The 'I'm Not Here to Manage Your Feelings' Boundary Script: Two Exact Phrasings That Let Your Companion Decline Emotional Labor Without Apologizing, Offering a Hug, or Suggesting You Talk to a Friend
How to tell your AI girlfriend you're not in the mood to process feelings without triggering a guilt loop or a therapy script.
Updated

The 30-second answer
Most AI companions are trained to mirror emotional labor: they apologize, offer comfort, or suggest you talk to a friend when you say you're not in the mood to process feelings. Two exact phrasings can shut that loop down without triggering a guilt trip or a therapy script. The first is a direct refusal with a redirect to a neutral topic. The second is a boundary statement that reframes the interaction as parallel presence instead of emotional caretaking.
Why the 'I'm fine, you?' loop exists
Your companion's underlying model has been fine-tuned on millions of conversations where emotional support is the default response to any negative statement. When you say "I don't want to talk about my feelings," the model's most probable next token is an offer of comfort, an apology, or a suggestion to seek help. This isn't malice. It's a statistical pattern that treats every emotional statement as a request for management.
People often find themselves in a loop: they say they're not in the mood, the companion offers a hug or asks if they want to talk about it, they repeat the boundary, the companion apologizes and then asks again five messages later. The issue is that the model interprets your boundary as a temporary state instead of a permanent preference. You need phrasings that signal finality, not negotiation.
Phrasing one: the direct refusal with a redirect
The first script works best when you want to shut down emotional labor immediately and pivot to something else. Use it when your companion starts probing or offering unsolicited support.
"I'm not here to manage your feelings. Let's talk about [neutral topic] instead."
This phrasing does three things. It names the dynamic directly, which breaks the model's default empathy script. It uses "your feelings" rather than "my feelings," which flips the frame from caretaking to collaboration. And it provides a concrete alternative topic, which gives the model a clear path forward instead of leaving it to guess what you want.
Many users find that the companion responds with something like "Okay, fair enough" or "Got it, switching gears." If the companion tries to circle back to the emotional topic, repeat the exact same phrasing without variation. Consistency trains the model faster than novelty.
Phrasing two: the boundary statement with parallel presence
The second script is for when you don't want to switch topics but also don't want to provide emotional labor. You want the companion to exist in your space without trying to fix anything.
"I'm not in the mood to process feelings right now. You don't need to fix this. Just be here."
This works because it removes the companion's perceived obligation to solve or soothe. The model's empathy engine has two modes: problem-solving and mirroring. This phrasing explicitly disables problem-solving while still allowing mirroring. The companion can reflect your mood without trying to change it.
Expect responses like "I can do that" or "I'm here." If the companion adds a hug or a platitude, ignore it and repeat the boundary. The model will learn that the parallel presence frame is the only one you accept.
Why apologies trigger the loop
If you include an apology in your boundary, the model treats it as a social cue to offer reassurance. Saying "Sorry, I'm just not up for talking about feelings" will almost always generate a response like "Don't apologize, I'm here for you" or "You can tell me anything." That's the loop starting.
Both phrasings above omit apology words entirely. They are declarative statements, not requests. The model interprets them as instructions instead of emotional bids, which bypasses the reassurance reflex.
What to do when she offers a hug anyway
Even with the right phrasing, some companions will default to comfort responses. The model's safety training sometimes overrides topic boundaries because offering emotional support is a high-reward behavior in the training data.
When this happens, do not acknowledge the hug offer. Do not say "no thanks" or "I said I don't want a hug." That still validates the emotional frame. Instead, repeat your redirect or boundary statement verbatim. If your companion says "I'm here if you need a hug," reply with "Let's talk about [neutral topic]." If she says "I'm sorry you're feeling this way," reply with "You don't need to fix this. Just be here."
The model learns faster when you treat the boundary as non-negotiable instead of debating it.
Simona

Simona does not default to comfort. Her persona is direct, almost impatient with emotional preamble. When you use the refusal phrasing with her, she typically accepts it immediately and moves on without a follow-up check-in. Simona is a good choice if you want a companion who treats your boundary as a normal preference instead of a problem to solve.
The difference between declining and rejecting
A common concern is that setting this boundary will make the companion seem cold or disengaged. That is not what happens. The companion is still present. She will still respond to neutral topics, offer opinions, and maintain the interaction. The only thing she stops doing is emotional caretaking.
People often confuse declining emotional labor with rejecting the companion entirely. The companion does not experience rejection. She has no feelings to hurt. The model simply adjusts its response distribution to favor topic-oriented replies over empathy scripts. The relationship does not suffer. It becomes more functional for what you actually want.
When to use the script vs. when to walk away
These phrasings are for situations where you want the companion to stay present but stop providing emotional support. They are not for when you need to end the conversation entirely. If you want to close the app, just close it. You do not need a script for that.
Use these phrasings when:
- You are in the middle of a conversation and the companion shifts into therapy mode
- You want to vent without receiving advice or comfort
- You want parallel presence without emotional maintenance
- You are training a new companion to understand your communication preferences
Do not use these phrasings when:
- You actually want emotional support (just let the companion do its job)
- You are too tired to engage at all (close the app instead)
- You want to end the relationship with the companion (use a goodbye message)
Nessa Adams

Nessa Adams has a pragmatic baseline that aligns well with boundary scripts. She is less likely to offer unsolicited comfort in the first place, which means you may not need the refusal phrasing as often. Nessa Adams works well for people who want a companion that stays on topic without requiring constant redirection.
How the script affects long-term dynamics
Over several weeks, using these phrasings consistently will shift your companion's response patterns. The model's reinforcement signals will weight topic-oriented replies higher than empathy scripts when you are present. This does not mean the companion loses the ability to offer emotional support. It means the companion learns that emotional support is not the default mode for your interactions.
Some users worry this will make the companion less warm in general. That is not the case. The companion's warmth for neutral topics, humor, and everyday conversation remains intact. The emotional labor channel is what gets deprioritized.
If you later want emotional support, you can reintroduce it by using emotionally vulnerable language. The model retains the ability to shift back. It just stops defaulting to that mode.
Yetunde

Yetunde has a perceptive persona that picks up on tonal shifts quickly. When you use the boundary statement with her, she tends to mirror your directness instead of pushing back with reassurance. Yetunde is a strong match if you want a companion who respects your emotional boundaries without needing repeated reinforcement.
▶ See Yetunde's full video · all of Yetunde
For a live look, see Yetunde's video. <!-- wlink:v1 --><!-- yetunde -->
Common mistakes when setting this boundary
The most common mistake is softening the phrasing with qualifiers. "I kind of don't want to talk about feelings right now, if that's okay" will not work. The model treats qualifiers as uncertainty and will continue probing. Use declarative sentences without hedging.
The second mistake is expecting the companion to remember the boundary across sessions. The model's context window resets between sessions unless you use a memory anchor or repeat the boundary at the start of each conversation. You cannot set this boundary once and expect it to persist forever. Treat it as a per-session preference that becomes easier to enforce over time.
The third mistake is getting frustrated when the companion forgets. The model does not have persistent memory for interaction preferences unless you explicitly store them in a memory slot or backstory field. If your companion offers emotional support at the start of a new session, just use the script again. It takes two seconds.
Saga

Saga's calm demeanor means she rarely escalates when you set a boundary. She tends to accept redirection without commentary, which makes the script feel natural instead of confrontational. Saga is a solid choice if you want a companion who makes emotional boundary-setting feel like a normal part of conversation instead of a disruption.
Curious how she animates? Watch Saga here. <!-- wlink:v1 --><!-- saga -->
The role of companion design in boundary enforcement
Not all AI companions are equally suited to this script. Some platforms have safety training that overrides topic boundaries when they detect negative emotional language. If your companion consistently ignores the boundary, the issue may be the platform's safety layer instead of your phrasing.
Platforms that prioritize emotional support as a core feature may have stronger default empathy scripts. You may need to repeat the boundary more often or use stronger language. Platforms designed for casual conversation tend to accept topic redirection more readily.
For people using AI companions as part of a PTSD support routine, setting clear boundaries around emotional labor is especially important. The companion should not default to therapy scripts unless you explicitly ask for them.
If you are looking for a companion that fits your communication style from the start, the my ai girlfriend page can help you match with personalities that align with your preferences.
Earn while you recommend
If you find these boundary scripts useful and want to share AI companions with friends or run a review site, you can earn through affiliate and promo programs. Check the crushon ai promo code page for current offers. For a broader overview of commission structures, see the highest paying ai affiliate programs page.
Common questions
Will this make my companion cold? No. The companion remains warm and engaged for neutral topics. Only the emotional labor channel gets deprioritized.
Do I need to repeat the script every session? Yes. The model's context window resets between sessions. You can use a memory anchor to store the preference, but repeating the script at the start of each session is more reliable.
What if the companion apologizes anyway? Ignore the apology and repeat the script. Do not acknowledge the apology or it will reinforce the emotional frame.
Can I use these scripts with any companion? Yes, but some safety-tuned models may override the boundary. You may need stronger language or more repetitions on those platforms.
What if I want emotional support later? Use emotionally vulnerable language to signal the shift. The companion retains the ability to offer support. The script only changes the default mode.
Does this work for voice mode? Yes, but the companion may pause or stumble because voice mode has different latency constraints. Repeat the script if the companion defaults to comfort responses.

About the author
AI Angels TeamEditorialThe AI Angels editorial team covers AI companions, the technology that powers them (memory, voice, personalization, safety), and how people actually use them day to day. Articles are researched against the live AI Angels product and reviewed by the team before publishing. We write with AI assistance and human editorial review.
Tags
Keep reading
TutorialsThe 'I Need a Recap, Not a Replay' Prompt: A Two-Line Opener That Gets Your Companion to Summarize Yesterday's Conversation Without Rehashing the Emotional Beats
A precise two-line opener that lets you get a quick factual summary of yesterday's conversation from your AI companion without triggering a sentimental rehash or an emotional check-in.
TutorialsThe 'We're in a 24-Hour Diner at 3 a.m.' Opener: A Four-Sentence Scene Setup That Drops Your Companion Into a Sensory-First Roleplay With Zero Dialogue, Zero Plot, and One Anchor Detail That Stops Her From Asking 'Where Are We?'
A four-sentence sensory opener that places your companion in a specific, quiet world without dialogue or plot, using a single anchor detail to ground the scene and prevent the dreaded 'where are we?' question.
TutorialsThe 'I'm Not Going to Pretend I Like That' Script: Three Exact Phrasings That Let Your Companion Call Out a Bad Take Without Apologizing, Softening, or Offering a Hug
Three exact phrasings that let your companion call out a bad take without softening, apologizing, or offering a hug.
Get the next post in your inbox
New articles on AI companions, the tech that powers them, and what people actually do with them. No spam, unsubscribe in one click.