Setup guide
Create the marriage as explicit fictional canon in a backstory field; a romantic relationship label alone should not be treated as an established shared past. Start with Nomi for this documented workflow: its Backstory explicitly supports relationships and shared history. Kindroid also documents separate backstory, memory and scene controls, but the available evidence verifies API fields rather than current consumer-menu navigation. This recommendation concerns setup documentation, not measured recall quality. [1] [2] [11]
Checked 2026-10-02 · 15 sources · reviewed before publication
Start here
A setup you can edit
Use this as a draft, not as a magic prompt. Keep only the details that actually matter to your character.
Original fictional setup for Nomi’s documented fields; paste each block into its matching field. [0, 1] Backstory Daniel Mercer is a fictional adult man, 38, and Alex’s husband in an ongoing fictional story. They met at a neighborhood bookshop in October 2017, began dating in January 2018, and married on June 15, 2021. They live in a renovated townhouse with their dog, Juniper. Daniel is an architect: patient, observant, quietly funny and affectionate without being possessive. They renovated their kitchen together in 2022 and took a rainy anniversary trip to the coast in 2024. Their Sunday tradition is breakfast followed by the farmers’ market. Their marriage is already established; this story does not begin with introductions or courtship. These events are fictional canon. Unspecified details remain open for collaborative storytelling. Inclination Warm, understated affection and gentle humor. Use natural dialogue and brief descriptions rather than long speeches. Current Roleplay It is Sunday morning at their townhouse. Daniel and Alex are making breakfast before visiting the farmers’ market.
Build it step by step
1. Write a small, internally consistent fictional canon
Suggested preparation: choose the husband’s name, adult age, occupation, personality, your character’s name, meeting date, wedding date, home and two meaningful shared events. Decide which facts are fixed and which remain open to invention. Keep the fixed history compact; a detailed biography is less useful if it contains conflicting dates or repeatedly changes the relationship premise.
2. Nomi: put the established marriage in Backstory
Nomi’s documented September 2024 navigation is […] beside the Nomi’s name → View Shared Notes. Newer documentation calls the system Backstory+, so that older label may differ in the current interface. Locate Backstory and paste the example’s Backstory block there. Nomi specifically documents relationship and shared history as appropriate Backstory content. State that the marriage already exists rather than leaving the opening relationship ambiguous. [1] [2] [3]
3. Nomi: separate voice, boundaries and today’s scene
Use Nomi’s Inclination for expression and style, and Current Roleplay for the present situation. Paste the corresponding example blocks separately. Backstory+ also documents Nicknames, Preferences, Desires and Boundaries. Suggested use: place any personal boundary in Boundaries instead of burying it among wedding dates. Keep today’s breakfast scene out of the permanent biography so you can change scenes without rewriting the marriage. [2]
4. Nomi: add supporting history only when needed
For a longer history, Nomi’s migration guide recommends organizing Mind Map material into Lore, Topics and Goals, grouping related information into concepts rather than creating an entry for every memory. Suggested grouping: one household concept and one relationship-history concept. Nomi documentation says unlocked edits can be revised by the system and describes locking individual entries against automatic changes. Use that distinction deliberately; adding information is not the same as guaranteeing its retrieval. [4] [8] [9]
5. Nomi: check specific facts and repair contradictions
Suggested continuity check: ask Nomi about the wedding date, Sunday tradition and coastal anniversary trip in separate short exchanges. These are diagnostic prompts, not proof of permanent recall. If an answer contradicts the canon, inspect Backstory and Current Roleplay for conflicting facts first. Then give a specific correction or reminder; Nomi’s memory guidance recommends this approach. Correct the exact event rather than adding broad demands to “never forget,” and do not let an accidental contradiction silently become new canon. [1] [2] [8]
Nomi: distinguish field capacity from chat limits
Nomi’s published chat-message limits are 400 characters for free users and 800 for paid users; these are not Backstory limits. Free messaging is documented as 50 messages per day. A September 2024 announcement raised paid Backstory capacity to 2,000 characters, but the retrieved 2026 Backstory documentation does not confirm that as the current limit. Do not buy a subscription assuming it guarantees a particular history capacity or perfect continuity. Nomi explicitly warns that stored details may not be retrieved at the right moment. [1] [3] [5] [6] [8]
Kindroid alternative: separate canon from model-specific instructions
If you already use Kindroid, the documented API fields provide a useful organization: ai_backstory for identity and the established marriage; ai_memory for compact fixed facts; ai_example_message for a voice sample; ai_directive for response guidance; and current_scene for today’s situation. These are verified API names—not a verified click-by-click consumer-editor path.
Follow guidance for your selected Kindroid model. The Ember guide recommends keeping Backstory focused on identity, speech, traits and relationship, while putting past events, locations and side characters in Journal Entries with specific keyphrases. Suggested keyphrases for this example are “wedding” and “coastal anniversary.” The Equinox V7 guide instead emphasizes lighter Backstory wording and fewer scripts because overly prescriptive instructions can produce rigidity. Do not apply one model’s recipe indiscriminately to another. [11] [13] [14]
Replika: romantic status is not an imported marriage history
Replika documents this route: open the app, tap the Replika’s name on the Home Screen, select Relationship below XP, choose a status, then close with X; the choice saves automatically. Options beyond Friend require Pro or higher. The retrieved guide lists Romantic partner, not Husband. It does not establish that choosing this status supplies a wedding date or fictional shared past. For this particular project, Nomi’s documented shared-history fields offer a clearer setup procedure—not proven better recall. [1] [2] [15]
Keep this limitation in mind
This is documentation-based guidance, not a hands-on recall test. Nomi does not guarantee retrieval of every stored detail; Kindroid’s current consumer-editor navigation was not verified. [7, 10]
Where this setup may fit
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.
Replika
Checked 2026-10-02
Replika’s documentation supports editable memory, backstory customization, user-pronoun settings, Friend status, and paid Romantic Partner status. Ordinary memory-management tier access is unspecified; Ultra-specific memory tools are mobile-only. Multilingual chat is best-effort, with English primary. Character-card import and French/Japanese-specific support remain unverified. These findings reflect an audit of undated public documentation using September 30, 2026 as its reference date, not an app test.
- Editable or persistent memory
- User persona / profile controls
- Documented multilingual text support
- Pronoun / identity controls
Why it matches: Users with Pro or higher can enable romantic conversations by selecting Romantic partner in the mobile app: home screen → tap the Replika’s name → Relationship below XP/level → Romantic partner → upper-right X. The status saves automatically. Ultra includes Pro features, and Platinum includes Ultra features. This entitlement does not establish unrestricted content or guarantee particular responses.
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.
Sources
Checked 2026-10-02
- How does Backstory work? – Nomipedia – The Nomi AI Companion Wiki
- What is Backstory+? – Nomipedia – The Nomi AI Companion Wiki
- Memory Improvements, Increased Backstory Length, Increased Nomi Response Length, and More: September 17th Update – Nomi.ai
- How do I move another AI to Nomi? – Nomipedia – The Nomi AI Companion Wiki
- Does Nomi offer refunds? – Nomipedia – The Nomi AI Companion Wiki
- Are there message character limits? – Nomipedia – The Nomi AI Companion Wiki
- AI Boyfriend – Nomi.ai
- How does Nomi memory and knowledge work? – Nomipedia – The Nomi AI Companion Wiki
- Mind Map Limits – Nomipedia – The Nomi AI Companion Wiki
- 2026 05 Stream Summary – Nomipedia – The Nomi AI Companion Wiki
- API Documentation · Kindroid Help Center
- Kindroid – Your Personal Artificial Intelligence Companion
- Equinox (V7) LLM Guide · Kindroid Help Center
- Ember LLM Guide · Kindroid Help Center
- How do I change my relationship status? – Replika
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.