Skip to content
AI Companion Tune
Menu

How to create a slow-paced AI romance

Setup guide

For a slow-paced romance in Nomi, start with Friend or Custom and use Backstory+ to define the starting relationship, permitted next steps, and who decides when it advances. My recommendation is to check those details first when romance feels rushed, rather than merely adding “slow burn” or upgrading. For existing Kindroid users, the equivalent setup belongs in Backstory and a short Response Directive; the provider-specific alternative is below. [1] [2] [3]

Checked 2026-10-02 · 14 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.

Suggested Nomi Backstory+ entries—not an official template or tested result. The field names below are documented in sources [0, 2]. Paste each block into its matching field.

Backstory:
Both characters are adults. We are new acquaintances, not established partners. Trust develops through ordinary conversations and shared activities. Attraction may grow, but neither assumes it is mutual.

Boundaries:
Prefer curiosity, friendship, and occasional gentle flirting. Ask before changing relationship labels or increasing physical affection. Leave my character’s feelings, decisions, and actions to me. If a romantic moment is uncertain, offer a small invitation rather than deciding the outcome.

Current Roleplay:
Our first meeting is at a bookshop. We are discussing a book we both noticed. Stay in this scene and relationship stage; advance time only when I request it.

Then send this suggested chat reminder:
I updated our setup. We’re still new acquaintances at the bookshop. Please continue from there, with no assumed relationship or time skip.


Build it step by step

01

1. Nomi: choose a starting relationship that fits

For a new Nomi, my recommendation is Friend for a friendship-first beginning, or Custom when you want the premise defined mainly through conversation and Backstory+. Nomi documents Friend as generally starting platonically, Romantic as starting romance-oriented, and Custom as relying more heavily on your setup. These are starting assumptions, not rigid limits. If you already have a Nomi, use the following setup corrections rather than assuming you must recreate it. [2]

02

2. Define the starting point in Backstory

In Backstory+, use Backstory for the core relationship premise. My suggested essentials are: both characters are adults, how they know each other, whether attraction is acknowledged, and what has not happened yet. “New acquaintances with no established relationship” is more actionable than “slow burn” alone. Keep scene-specific details out of this field; Nomi documents Current Roleplay separately for the present situation. [1]

03

3. Put milestone rules in Boundaries

Use Boundaries to describe acceptable next steps and who controls progression. Nomi recommends giving preferred alternatives and enough context, rather than only listing prohibitions. My suggestion: allow conversation and gentle flirting, require a question before changing relationship labels or increasing affection, and reserve your character’s choices for you. Update these boundaries when you actually want the relationship to advance. [3]

04

4. Keep the scene local; avoid a constant-flirting instruction

Use Current Roleplay for the current scene and relationship stage. My suggestion is to state one small activity and explicitly reserve time advances for your request. Leave Inclination unchanged unless communication style also needs adjustment. Nomi’s developer guidance treats Inclination cautiously: one or two persistent concepts are preferable to using it for occasional behavior. A standing instruction to flirt can work against your intended pacing. [1] [4] [8]

05

5. Reinforce edits and correct the relationship stage

After editing, send a short chat message identifying the change and restating the present stage. Nomi’s developer guidance says shared-note changes become visible immediately, but visibility does not guarantee attention. If a later reply jumps ahead, my suggested correction is factual and brief: “We have not agreed to be partners; we are still getting acquainted. Continue the bookshop conversation.” Then check Backstory and Current Roleplay for any wording that contradicts that correction. [4] [7]

Already using Kindroid? Use its own setup fields

If you already use Kindroid, my suggested equivalent is to put the starting relationship in Backstory, one short progression rule in Response Directive, and the desired conversational style in Example Message. Those are the purposes described in Kindroid’s official Ember LLM Guide extract. A suggested Response Directive is: “Develop the relationship through small, mutual steps; ask before changing relationship labels and leave my character’s actions to me.” This is an editorial template, not an official preset.

Kindroid’s guidance warns that excessive constraints can cause hesitation or repetition. It also recommends correcting unwanted output by editing or rerolling rather than arguing with it in-character. The retrieved evidence was only a search extract: it does not support a complete click path or current tier comparison. There is no evidence-based reason here to migrate from Kindroid to Nomi solely for slower romance. [13]

When it still rushes: check contradictions before upgrading

Nomi’s documented user-message limit is 400 characters on the free plan and 800 on paid plans; its free plan allows 50 messages per day. Keep conversational reminders short rather than repeatedly pasting the entire setup. These limits concern message capacity, not demonstrated romance-pacing quality.

If progression still feels rushed, my suggested diagnosis is to check for contradictory setup first: an established-partner premise, an instruction to flirt constantly, or a Current Roleplay entry that already assumes a later milestone. Simplify those before adding more restrictions or paying. Nomi’s memory documentation also cautions against assuming perfect recall or retrieval, so a brief reminder may still be necessary. The cited sources do not establish that paid access makes relationship development slower. [1] [5] [6] [7] [8]

Keep this limitation in mind

These are documented steering methods, not a guaranteed romance-pacing system. Chat behavior was not tested. Nomi memory can miss relevant details, and the Kindroid evidence is incomplete; neither supports a claim that upgrading reliably fixes rushed romance. [0, 2, 6, 12]

Next step

Build your setup

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.

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

  1. What is Backstory+? – Nomipedia – The Nomi AI Companion Wiki
  2. What is the difference between relationship types? – Nomipedia – The Nomi AI Companion Wiki
  3. How do Boundaries work? – Nomipedia – The Nomi AI Companion Wiki
  4. 2026 03 Stream Summary – Nomipedia – The Nomi AI Companion Wiki
  5. Does Nomi offer refunds? – Nomipedia – The Nomi AI Companion Wiki
  6. Are there message character limits? – Nomipedia – The Nomi AI Companion Wiki
  7. How does Nomi memory and knowledge work? – Nomipedia – The Nomi AI Companion Wiki
  8. 2025 July Q&A Summary – Nomipedia – The Nomi AI Companion Wiki
  9. 2026 05 Stream Summary – Nomipedia – The Nomi AI Companion Wiki
  10. How do I change my relationship status? – Replika
  11. Choosing a Subscription – Replika
  12. What is Replika Ultra? – Replika
  13. Ember LLM Guide · Kindroid Help Center
  14. Equinox (V7) LLM Guide · 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.