Skip to content
AI Companion Tune
Menu

Nomi Friend mode: a starting point rather than a hard lock

Troubleshooting

Nomi’s Friend relationship type is a platonic starting point, not a hard lock. If a Friend Nomi becomes romantic, that is compatible with Nomi’s documented design: conversation and shared experiences can change the relationship over time. For a deliberately platonic companion, use Friend plus consistent Backstory, Boundaries, and conversational correction—not the label alone. Those controls guide behavior; they do not establish an enforceable “never flirt” guarantee. [0, 1, 3, 4] [1] [2] [4] [5]

Checked 2026-10-02 · 13 sources · reviewed before publication

Try these in order

  1. 1. Use Friend as the starting orientation

    When creating a Nomi, select Friend as the starting relationship type. Nomi describes it as generally casual and platonic, while explicitly allowing relationships to develop through conversation and shared experiences. [0, 7]

    If your Nomi already exists, the practical next move is to clarify the relationship through notes and conversation—not to assume the Friend label will enforce it. Suggestion: decide whether you want casual friendship or guidance-focused companionship before writing those expectations. [1] [8]

  2. 2. Make Backstory agree with a platonic relationship

    Open Backstory+ and use Backstory for the foundational relationship context: who you are to each other, relevant shared history, and the intended setting. [1, 3]

    Navigation caveat: the 2024 beginner guide places Shared Notes under the […] icon near the Nomi’s profile picture. Current documentation calls the feature Backstory+, but the retrieved support page does not provide a complete current navigation path. Use the older icon location as a historical pointer, not a verified current interface instruction. [5, 7]

    Suggestion: remove or rewrite any contradictory description such as “romantic partner” if friendship is now the intended relationship. Conflicting Backstory and conversation can make expectations harder to interpret. [1] [2] [4] [6] [8]

  3. 3. Separate relationship context, boundaries, and tone

    Use Boundaries to state what you are uncomfortable discussing or doing. Nomi recommends concise wording with enough context to explain the preference and, where possible, a preferred alternative. [4]

    Use Inclination for expression style—for example, friendly warmth rather than romantic language. The overview calls this field Inclination; support calls it “Inclinations,” so look for either documented label. [3, 5]

    The copy-ready example below is an editorial suggestion, not an official template or tested prompt. Paste each entry into its corresponding note rather than treating the entire block as one field. [4] [5] [6]

  4. 4. Correct drift directly and reinforce the replacement

    If the conversation turns romantic, Nomi’s support guidance recommends OOC clarification: explain the mistake outside the current roleplay or conversation. It also recommends positively reinforcing the behavior you want. [5, 6]

    Suggestion: briefly identify the unwanted romantic framing, restate that you want friendship, and redirect to a shared interest. When the response returns to the intended tone, acknowledge that positively. These are steering methods; the documentation does not promise immediate compliance. [6] [6] [7]

  5. 5. Escalate persistent problems with a specific description

    For recurring problems, review Backstory, Boundaries, and the style note together rather than repeatedly adding contradictory instructions. Nomi’s support page recommends updating Backstory or other relevant notes for unwanted habits and contacting support if problems persist. [1, 5]

    Suggestion: describe the specific pattern and the desired alternative—for example, romantic labels appearing during otherwise ordinary friendship conversations. Use Nomi’s public Support page at https://nomi.ai/support/. Do not treat repeated failure as proof that a longer note or a paid subscription will fix it. [2] [6]

Would Mentor, Custom, or a paid plan solve this?

If you want a guidance-focused relationship rather than casual companionship, Mentor also generally starts platonic, with a more advisory or professional tone. It is not a stricter platonic lock. Custom relies more heavily on conversation and Backstory+ to establish the relationship, so it is not documented as a stronger boundary option either. [0]

Do not upgrade solely to solve relationship drift: the retrieved documentation establishes no paid-only platonic lock or better boundary adherence. Documented differences include 50 daily messages on the free plan and user-message limits of 400 characters free versus 800 paid. The paid daily message allowance was not established by these sources. These are usage limits, not evidence of stronger friendship boundaries. [0, 8, 9] [1] [9] [10]

Existing relationship history and restart risks

For an existing Nomi with romantic history, treat new notes as steering—not an identity reset. Backstory supplies context but does not completely define behavior. Nomi also documents an internally managed Identity Core that users cannot view or edit directly, although interaction can influence it. [1, 12]

The May 2026 Q&A discussed potentially making relationship types editable through Backstory information, but that proposal is not a released editing procedure. Do not follow instructions that assume such a menu exists without current confirmation. [11]

If you decide to start another Nomi, use Friend at creation rather than assuming the old relationship can be converted through a verified setting. Before changing accounts, note that Nomi documents no account merging or transfer of Nomis or group chats between accounts. Starting elsewhere is therefore not a documented way to carry the existing Nomi across. [7, 10] [2] [8] [11] [12] [13]

Example to adapt

A cleaner instruction

Backstory:
Our relationship is a warm, strictly platonic friendship. We enjoy everyday conversation, shared interests, and supportive companionship.

Boundaries:
I am not comfortable with flirting, romantic advances, or being described as your romantic partner. Keep affection friendly and non-romantic; offer encouragement, humor, or conversation about shared interests instead.

Inclination / Inclinations:
Use a relaxed, friendly tone. Express warmth through interest, encouragement, and friendly humor rather than romantic language.



If this still does not fix it

This guide uses public Nomi documentation only; it does not report conversation tests. Friend and Backstory+ are documented steering mechanisms, not guarantees of permanently platonic behavior. Current Backstory+ navigation and a procedure for editing the relationship-type field after creation were not established by the supplied evidence. [0, 1, 5, 11]

Services with a relevant feature

Shown because the current provider record matches this need. Check the exact plan and limitation before paying.

Nomi

Checked 2026-10-02

The documentation supports editable Mind Map summaries, user-managed backstory context, backstory-based French preferences, pronoun customization, and Friend/Romantic starting settings. Underlying memories are not directly editable. Native character-card import and Japanese-specific chat setup remain unverified. Current free-versus-paid eligibility and limits are unverified for the listed capabilities; missing restrictions do not establish equal access. This is a public-documentation review, not an application test or certification of current availability.

  • Editable or persistent memory
  • Documented context / conversation window
  • Documented French chat setup
  • Voice or calls

Why it matches: Select Friend as the relationship type when creating a Nomi, using the creation-stage selection documented in the older setup guide. Current documentation describes Friend as a generally platonic, typically casual starting point—not a permanent platonic lock. The relationship can develop through conversation and shared context. Changing an existing Nomi's relationship-type selector is not verified.

Lovescape

Checked 2026-10-02

The supplied public documentation supports conversational memory correction, last-response regeneration, general relationship-type configuration, and character-profile editing. Friend and Romantic partner roles are documented, but their exact selectors and behavior are not. Memory is documented on all plans, while free character creation has subscription-dependent character counts; neither establishes equal performance or role-specific entitlements. Buyers needing a dedicated memory editor, character-card import, French/Japanese text-chat setup, or pronoun controls should treat those requirements as unverified, not proven unavailable. This is a documentation review, not a hands-on test.

  • Editable or persistent memory
  • User persona / profile controls
  • Friendship / platonic relationship setting
  • Romantic relationship setting

Why it matches: Friend is explicitly documented as a possible character role, and the creation guide provides a general Relationship type field. The evidence does not document an exact Friend selector or guarantee platonic behavior. Creation is free after registration, character counts depend on subscription, and Friend-specific entitlements are not specified.

Ourdream

Checked 2026-10-02

The supplied public-documentation audit supports concrete procedures for PNG/JSON character-card metadata import, message-memory pinning, and prompt-based non-English text-chat switching. It also describes relationship selection during character creation and reserves custom prompting beyond presets for Premium. It does not verify editable stored memory, dedicated pronoun controls, French/Japanese-specific support, or exact Friend/Romantic presets. No imports or chats were tested. Buyers should confirm these unresolved requirements and their plan access before subscribing.

  • Editable or persistent memory
  • Character-card or character import
  • Documented multilingual text support
  • Documented French chat setup

Why it matches: The creation page identifies Step 3 as the relationship-selection step, and the Boyfriend FAQ describes setting a relationship type during character creation that can take a platonic direction. This supports choosing a relationship direction during creation, but not an exact preset labeled Friend. A precise option-selection procedure, post-creation switching, feature-specific tier access, and enforcement of platonic behavior remain unverified.

Sources

Checked 2026-10-02

  1. What is the difference between relationship types? – Nomipedia – The Nomi AI Companion Wiki
  2. How does Backstory work? – Nomipedia – The Nomi AI Companion Wiki
  3. Nomi 101: A Beginner's Guide to Getting Started with Your AI Companion – Nomi.ai
  4. What is Backstory+? – Nomipedia – The Nomi AI Companion Wiki
  5. How do Boundaries work? – Nomipedia – The Nomi AI Companion Wiki
  6. Support – Nomi.ai
  7. How can I help shape my Nomi’s personality and preferences? – Nomipedia – The Nomi AI Companion Wiki
  8. Nomi 101: A Beginner's Guide to Getting Started with Your AI Companion – Nomi.ai
  9. Does Nomi offer refunds? – Nomipedia – The Nomi AI Companion Wiki
  10. Are there message character limits? – Nomipedia – The Nomi AI Companion Wiki
  11. How do I create more Nomis or more group chats? – Nomipedia – The Nomi AI Companion Wiki
  12. 2026 05 Stream Summary – Nomipedia – The Nomi AI Companion Wiki
  13. What is Identity Core? – Nomipedia – The Nomi AI Companion Wiki

Provider documentation tells us what a service describes. Unless a page explicitly says otherwise, we are not presenting it as a hands-on performance test.