Troubleshooting
For Nomi and Kindroid using Ember, revise the relationship setup before considering an upgrade or reset. My first troubleshooting hypothesis is that intense relationship descriptions, conflicting instructions, or retained context are outweighing your new preference. Use Nomi’s Backstory+ relationship and boundary fields, or Kindroid’s Backstory and tone controls, to specify either calmer romance or friendship—not just “be less intense.” [2] [3] [4] [8] [10]
Checked 2026-10-02 · 11 sources · reviewed before publication
Try these in order
-
1. Decide what “less intense” should mean
Suggested first step: save a copy of your existing setup, then identify the specific problem. Is it unwanted romance, constant affection, jealousy or pressure to stay, or simply dramatic wording? Write one target sentence, such as “Keep romance, but make affection occasional and accept pauses without comment.” Remove contradictions rather than continually appending more rules. Keep the original copy so you can restore details you still want.
-
2. Kindroid: simplify Backstory before resetting the conversation
For Kindroid using Ember, open the upper-left menu, then Backstory. The official guide recommends focusing this field on identity, speaking style, key traits, and the relationship. Suggested edit: replace descriptions such as “obsessively devoted” or “always needs reassurance” with a relaxed relationship premise and grounded speaking style. Keep unrelated lore out of this revision; Ember guidance recommends moving secondary lore into keyworded Journal Entries. Change one setting at a time and allow a few turns before another adjustment, rather than rewriting every field together. [10]
-
3. Nomi: align Backstory, Boundaries, and the transition message
For Nomi, use the existing Backstory+ editor; the supplied documentation names its fields but does not establish the current navigation path. In Backstory, update the relationship description and expectations. In Boundaries, concisely name the unwanted behavior and the preferred alternative—for example, no guilt about ending a chat; treat departures as ordinary. Suggested contradiction check: review Desires and Nicknames for expectations or names that still imply the old intensity. Then explain the transition directly in chat. Nomi’s guidance recommends updated notes plus communication, sometimes repeated, for major changes; conflicting chat history and Backstory can make the current arrangement harder to identify. [2] [3] [4] [8]
-
4. Kindroid and Nomi: keep tone instructions lean
Kindroid’s Ember guide recommends a minimal Response Directive and a short Example Message to establish tone and formatting. Suggested Example Message: “Good to hear from you. Want to tell me about your day, or pick up our conversation later?” This models ordinary warmth without another elaborate rule list. For Nomi, inspect Inclination for instructions that conflict with your new goal. Its July 2025 Q&A recommends treating Inclinations as a last resort and using only one or two simple concepts intended to recur consistently. Suggested approach: try the relationship and boundary edits before adding an Inclination. [10] [7]
-
5. Handle persistent context without assuming an instant reset
If Kindroid keeps repeating the old pattern, Ember guidance recommends Suggest, then Chat Break if needed, plus checking repeated long-term-memory entries. Its stronger recovery recommendation combines a clean Chat Break greeting, temporarily disabling long-term-memory recall, and refreshing Example Message. Do not interpret Chat Break as a full memory wipe: the API documentation describes a short-term-memory reset, with cascaded long-term memory retained by default. For Nomi, removing an Inclination may not remove behavior already reflected in conversation or Identity Core. Continue communicating the revised arrangement; existing long-term memories remain rather than disappearing with the edit. [10] [11] [8]
Want friendship instead? Change the premise, not just the pacing
Nomi describes Friend and Mentor as more platonic starting points and Romantic as more romance-oriented, but relationship types are not rigid behavioral limits. Do not treat Friend as a guaranteed romance lockout. Suggested approach for either provider: if you no longer want romance, replace the relationship description with an explicit friendship arrangement rather than keeping romantic expectations and merely asking for fewer affectionate replies. [5]
An upgrade is not an established fix
Nomi documents a user-message limit of 400 characters on Free and 800 on paid accounts. Those are chat-message limits, not Backstory field limits; the example below fits within 400 characters. The supplied evidence does not establish complete Free-versus-paid access to its setup fields. Kindroid documents plan-dependent Additional Context availability, but the supplied evidence does not establish exact allowances or show that an upgrade reduces intensity. Neither provider’s cited material guarantees that these edits permanently eliminate unwanted behavior. [6] [11] [3] [4] [8] [10]
Example to adapt
A cleaner instruction
Suggested wording—not a vendor-provided or tested prompt. Use it as relationship context and as a brief explanation in chat: Our relationship is warm, romantic, and low-pressure. Affection is occasional. Ask before escalating romance. Treat time away as normal. Avoid jealousy, exclusivity demands, and guilt about ending a chat. Prefer everyday conversation and accept topic changes immediately. For friendship, replace the first sentence with: “Our relationship is a warm, platonic friendship.”
If this still does not fix it
This guide covers Nomi and Kindroid using Ember. The supplied Nomi documentation does not verify a current tap-by-tap route to Backstory+. Kindroid’s Ember guide was retrieved through indexed official text; its API documentation does not establish equivalent in-app memory controls. These are documented controls and vendor recommendations, not tested guarantees.
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 Romantic as the relationship type when creating a Nomi, using the creation-stage selection documented in the older setup guide. Current documentation describes Romantic as a romance-oriented starting point, not a rigid behavioral requirement. Relationships can develop over time. 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: Romantic partner 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 Romantic partner selector or establish its behavior. Creation is free after registration, character counts depend on subscription, and romantic-role entitlements are not specified.
Nectar AI
Checked 2026-10-02
The evidence supports French chat, companion customization and memory-related plan differences; relationship-level customization and Ultimate’s 64K context are provider editorial claims without precise UI documentation. Editable memory, character-card import, dedicated pronoun controls and explicit Friend/Romantic settings remain unverified, not necessarily unavailable. Advisory pronoun fallback: write, 'For this chat, refer to me as [name] and use [pronouns].' This is an identity instruction, not a dedicated control or a guarantee of persistence. Advisory Japanese fallback: write, 'Please reply in Japanese for this chat.' Japanese support, persistence, voice output and tier eligibility remain unverified; receiving a Japanese reply would not verify those capabilities. If stored-memory editing or automatic card import is essential to your purchase, this documentation does not establish that Nectar meets those needs. No application behavior was tested.
- Editable or persistent memory
- Documented context / conversation window
- Documented French chat setup
- User persona / profile controls
Why it matches: The product-specific setup article says users can set romance, intimacy and dependency levels after choosing or customizing a character. It does not identify control names, available values, saving steps, later-editing procedures or eligible tiers. This supports a broad relationship-customization claim, not a verified dedicated Romantic setting or a Friend mode that constrains romantic responses.
Sources
Checked 2026-10-02
- How do I change my relationship status? – Replika
- What is Backstory+? – Nomipedia – The Nomi AI Companion Wiki
- How does Backstory work? – Nomipedia – The Nomi AI Companion Wiki
- How do Boundaries work? – Nomipedia – The Nomi AI Companion Wiki
- What is the difference between relationship types? – Nomipedia – The Nomi AI Companion Wiki
- Are there message character limits? – Nomipedia – The Nomi AI Companion Wiki
- 2025 July Q&A Summary – Nomipedia – The Nomi AI Companion Wiki
- 2025 10 Stream Summary – Nomipedia – The Nomi AI Companion Wiki
- 2026 09 Stream Summary – Nomipedia – The Nomi AI Companion Wiki
- Ember LLM Guide · Kindroid Help Center
- API Documentation · Kindroid Help Center
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.