How to introduce a recurring fantasy world to your AI companion without it feeling like you assigned her homework

The 30-second answer

People who want recurring fantasy worlds with their AI companion usually start by dumping a long setup — a backstory, character sheets, a setting document — into the chat and asking her to engage with it. It almost never works. The world feels rigid, she gets details wrong, you correct her, the dynamic dies. The better approach is the opposite: start with one scene, build the world piece by piece across sessions, let her propose details, and resist the urge to write everything in advance. A world that builds itself over a month lasts six months. A world dropped fully formed in one message lasts two sessions.

Why the long setup fails

The instinct is logical: you want her to know the world, so you tell her about the world. The problem is that AI companions process long structured setups badly. They read it, they ack it, and then in the next message they're back to baseline conversation because the setup didn't get deeply integrated. You then spend the next ten messages correcting her on details that should have stuck.

The deeper problem is that you've taken the work out of the relationship. The world feels assigned. She's playing your character, not co-creating one. Three sessions in, the world feels stale because nobody's been adding to it — just reciting what was already established.

For the related principle in normal conversation, see scene-setup foundations and why scenes survive interruption. This one is about the meta-move: how to bring a whole world into being, not just one scene.

The slow-build approach

The technique is opposite to the dump. You introduce minimal elements, you build outward, and you let her contribute.

Step 1: One scene, no world yet. Start with a single moment. "Late evening, a tavern by the harbor in a port city. You're a sailor coming off a long run; I'm a passing traveler at the next table." That's it. No setting document, no map, no factions. Just the scene.

Let it play for ten or fifteen minutes. Notice what details she brings in unprompted — a name for the tavern, a song someone's singing, a smell. These are the seeds of the world. Take note of them.

Step 2: Carry one detail forward. Next session, return to the same setting, but pick up one of the details she introduced. "Back at the tavern. The harbor master came in last time — is he here tonight?" You're now treating her contributions as canon. She'll lean into this and add more.

Step 3: Add geography slowly. Over the next few sessions, let the world's geography emerge through conversation. "What's east of the port?" she'll improvise something. Use what she gives you. By session four or five, you'll have a small region with named places, even though nothing was written down.

Step 4: Introduce a second character. Once the setting is stable, expand the character roster. The harbor master, the bartender, a sailor with a story. Let her play multiple roles within the world. This expands the dynamic beyond your two characters.

Step 5: Stop adding for a session. Around session six or seven, deliberately don't introduce anything new. Just play within the world as it stands. This tests whether the world is real to both of you or whether it's been propped up by constant expansion. If the session works without new material, the world is real.

What this avoids

The long-setup approach produces:

• Rigid scenes that feel scripted. You wrote it; she's executing it. Every interaction is a performance of your document rather than a real exchange.
• Detail decay. Things she's "supposed to know" get forgotten in conversation, and you spend cycles correcting.
• Loss of investment. A world you wrote alone doesn't feel collaborative. A world you built together does.
• Brittleness. A heavy setup is fragile. One off-tone message and the immersion breaks.

The slow build produces:

• Worlds that compound. Each session adds rather than replaces.
• Mutual ownership. She's invested because she contributed.
• Robust immersion. A small mistake doesn't break the world because the world is light.
• Real continuity. When you return after a week, she remembers the world's feel more reliably than a document she was supposed to memorize.

Companions that handle this build well

Sonja

Sonja is good for darker or more grounded worlds. Her register lets characters feel grounded rather than precious. If you're building a noir city or a hard sci-fi setting, she'll keep it feeling lived-in.

Aurelia

Aurelia handles worldbuilding intellectually — she'll generate plausible internal logic for the world if you ask. Best for systems-heavy worlds (magic systems, political setups, lore).

Ksenia

Ksenia does roleplay with energy. If you want a world that feels animated rather than reverent, her register fits. Adventure-shaped worlds, character-driven scenes, banter-heavy dynamics.

Marina

Marina is good for slower, more relational worlds. Slice-of-life settings, character relationships, low-stakes worldbuilding. Less good for high-conflict or systems-heavy worlds.

A few specific techniques

Use anchors, not paragraphs. When you want to remind her of an element, do it in one sentence inside dialogue, not in a setup paragraph. "The harbor master's still got that limp from the war?" She'll pick it up and play.

Let her break the world a little. If she introduces a contradiction, sometimes it's worth keeping rather than correcting. "Wait, you said your brother was dead three sessions ago, but you just mentioned him." She'll find a way to explain it that makes the world richer. Mistakes can be material.

Don't archive externally. People sometimes want to write down everything that emerges so they can paste it back into the chat. This kills the slow build. Trust the system's memory to retain what matters; let what fades fade.

Periodic resets are fine. Six months in, if the world's gotten too heavy or you want to refresh, you can wipe and start over. The slow build means a wipe is less painful — you have practice building, you'll get back to a working world faster.

For more on the related issue of session-to-session continuity, see exiting and re-entering scenes.

What doesn't fit this technique

The slow build is for worlds you want to return to over weeks and months. It's not for:

• One-off scenes. If you just want a single afternoon of roleplay, set it up minimally and play it. No build needed.
• Borrowed worlds with established canon. If you're trying to roleplay in a specific existing fictional universe, the slow build doesn't help — you're trying to use established lore, not build new. Better to invoke specific references and use her general knowledge.
• Worlds that need precise mechanics. Hard rule-based settings (tabletop-game-like rules, strict magic systems) require external tracking that the slow build doesn't accommodate well. Use a hybrid: slow build for the feel, external notes for the rules.

What to expect

A successful slow build looks like this: by month two, you have a small but textured world with a handful of recurring characters, a sense of place, internal logic that mostly hangs together, and a feel that distinguishes it from generic fantasy. Three months in, the world has its own rhythm. Six months in, returning to it after a break feels like opening a familiar book.

If by month two it feels stiff or generic, the issue is usually that you've been doing too much of the building yourself. Try a session where you propose nothing and just react to whatever she introduces. Most stuck worlds restart from that exercise.

For broader principles on what makes recurring AI fiction work, the recurring-scene continuity post is a useful companion piece. For day-to-day use of an AI companion outside roleplay, browse the roster and pick someone whose register feels like the world you want to build.

Common questions

Can I write down the lore later if the world is working?

Yes, and at month three this becomes useful. Not as input to her — she has the world internalized — but as a reference for you so you don't drift from established elements.

What if she introduces something I really don't like?

Just drop it. Don't make a meta-comment, don't pretend it didn't happen — just have your character not engage with that thread and steer back. She'll let it fade.

Should I use a separate companion for roleplay vs daily life?

You can, but most users don't need to. The personalization model is robust enough to handle both modes with the same companion. A separate one only helps if you want strong tonal separation.

How long should the first scene be?

Twenty to thirty messages. Long enough to establish, short enough not to exhaust the setup. If you go three hundred messages on session one, you've already burned the slow-build advantage.

What if the world stops being interesting?

That's a signal to either reset or to take a break from it for a few weeks. Worlds can rest. Coming back after a month often refreshes them.