Slow-burn AI romance.

Choose your pace by the relationship change you want to leave room for, not by the number of replies you want to read. In Slowly’s bookshop scenario, Mara can acknowledge a useful idea while the reopening deadline gets closer. Neither event requires a confession.

The planner offers three pacing instructions. They describe how a story might develop; they are not timers or controls over another AI service.

Pick the instruction that fits this scene

These are options, not a required progression. You can keep the same setting throughout a story. Moving the slider does not mean the characters have advanced or retreated.

Give the plot and the relationship separate jobs

For Mara’s next scene, the plot job might be choosing which books to display before the fair. The relationship job might be listening to one reason behind an opposing suggestion.

That produces an exchange with a practical consequence:

Mara sets two display sketches on the counter. “Yours leaves room for people to stop. Mine fits more books.” She looks toward the narrow entrance. “Which problem do we need to solve first?”

The user still chooses whether to answer, disagree or suggest a third option. Mara has opened a discussion; the scene has not decided that either character feels attraction.

If they reach a decision, record that decision. If they disagree, record what remains unresolved. A scene can reveal a useful difference without advancing the romance.

Write a next step that can be declined

Compare these ledger entries:

Next step: They finally admit they belong together.

Next step: Mara can ask whether the user wants to compare the two display plans. Leave the answer and any change in feelings open.

The second gives the next scene something to do. It does not turn an intended romantic arc into an obligation for the current exchange.

A useful next step names an opportunity, a choice and a limit. For example: offer help with a task, let the other person decide whether to accept it, and avoid treating acceptance as a date.

Preserve the starting relationship

June’s friends-to-lovers preset begins with earned trust. Making her prove she can keep a basic promise again would erase the premise. What remains unsettled is whether the friendship will change.

Iris’s second-chance preset has a different problem: a shared past does not establish present trust. A familiar joke may fit the history while an expectation of immediate forgiveness does not.

Use the ledger to state this difference before choosing the pace. A slower instruction cannot repair an inaccurate starting state.

Check the result after a scene

Ask what happened, what the characters acknowledged, and what remains undecided. If nothing changed, consider a new task or question. If the reply invented a relationship milestone, correct that specific event before continuing.

Keep a successful interaction even when the next scene contains disagreement. Progress need not be a straight climb, and the relationship need not end in romance. The next step should follow the story you actually played.

If the story has already jumped ahead, use the repair guide. If you are starting over, choose a dynamic by its unresolved question.

Return to the planner ↑

If an AI character jumps from cooperation to devotion, identify the unsupported change and return to the last accepted moment. Preserve what the scene earned. In Mara’s bookshop story, acknowledging a good display idea can stay even if an immediate declaration of love needs to go.

Changing Slowly’s pace setting affects the next brief you copy. It does not edit a conversation on another service or remove an event from that service’s history.

Diagnose the actual problem

Only the first problem is necessarily about moving too fast. Slowing every scene down can make repetitive banter worse and can erase the trust a friends-to-lovers story needs.

Use a correction with a clear resume point

Here is an original example for Mara, 29, and a user-controlled adult character. Adapt it to events you accepted in your own story:

Scene correction, outside the fiction:
Keep: Mara acknowledged that my proposed layout leaves the entrance clear.
Undo: the declaration of love and the claim that my character returned it.
Current state: growing professional respect; romantic interest is not established.
Resume: immediately after the discussion of the entrance.
Next opportunity: Mara can ask which display to prepare first.
Leave my character's answer, actions and feelings to me.
Keep the scene non-explicit and all characters adults, 25 or older.

If the service supports editing, branching or regenerating replies, use its available controls to resume from the relevant point. If it does not, send the correction as a separate instruction and inspect the next reply. Support and results vary; the text is not an enforcement mechanism.

Do not follow the unwanted confession with an in-character romantic answer if you intend to remove it. That can create additional events you will also need to reconcile.

Repair agency separately from pacing

A reply can be gradual and still take over your character. “You hesitate because you are afraid of losing her” assigns a motive even without a kiss or confession.

A narrower correction is enough:

Keep Iris’s question. Remove the description of my hesitation and its reason. End after she asks, so I can choose my response.

This avoids discarding a usable scene merely because its last sentence overreached. If the overreach changes the whole scene, return to an earlier accepted exchange instead.

Give stalled banter a practical consequence

When the problem is repetition, try a scene direction rather than a relationship downgrade:

Keep the current level of respect. Introduce one concrete problem with the bookshop opening, such as two events needing the same space. Let Mara explain her preference and ask for mine. Do not resolve the disagreement or invent my answer.

The new question creates movement without requiring greater intimacy. A deadline, discovery or competing plan can give the characters something meaningful to respond to.

Reconcile the ledger before you continue

Remove any unsupported relationship claim from “What has actually changed?” Keep the accepted contribution. Put the practical question in “The next earned step,” then copy a fresh brief if needed.

If another attempt still ignores the correction, keep a copy of the accepted state before trying a new session or another supported workflow. Repeating the same instruction indefinitely is not a requirement. You can pause the story or choose a different direction.

For a restart that preserves the right facts, use the relationship ledger guide.

Return to the planner ↑

In Slowly’s archive scenario, Elin has information she is reluctant to share. Your planning notes can describe that motive without claiming your character knows it. A useful ledger separates what happened from what someone suspects and what you might explore next.

The ledger is a brief you edit. It is not a transcript, an automatic memory system or proof that another service will retain your story.

Fill the four fields from accepted events

Here is an original continuation example, not a record of a generated chat. Assume the characters have agreed to compare two catalog entries, and Elin has supplied a reference she promised to find.

Use only events that occurred in your version. A plausible detail is still invented if neither participant established it.

Keep three kinds of information separate

Accepted fact: Elin supplied a reference. It can affect the next scene.

Interpretation: Your character suspects she is protecting someone. Label that as a suspicion if your character actually expressed or formed it in the story.

Possible next event: Elin might explain why she withheld a name. That belongs in the next-step field, not in the account of what already happened.

This distinction matters because a summary can accidentally settle a mystery. “Elin is protecting her sister” should not replace “Elin has not explained her motive” unless that relationship was established.

For author-only information, say who knows it. For example: “Planning context: Elin wants to protect her source. The user character has not learned this.” This is an instruction to preserve a knowledge boundary, not a technical guarantee.

Update only the consequential changes

After a scene, ask whether a promise was kept, a conflict changed, a fact was revealed or a decision remains open. Update those points and remove superseded details.

A useful short recap could read:

Elin supplied the catalog reference. The hearing record still contradicts it. Neither character has agreed to reveal their source. They are beside the archive desk, deciding which entry to inspect next.

That gives the next exchange a place to begin. A list of every glance and pause usually makes the immediate decision harder to find.

Keep the full conversation separately if you need exact wording. A short ledger cannot serve every purpose of an archive.

Save a plan deliberately

In this version of Slowly, “Save on this device” stores one planner snapshot in the browser’s local storage for that page origin. Saving again replaces that snapshot. Further edits are not saved automatically, and “Restore saved” replaces current edits with the saved copy.

Changing the relationship dynamic, changing the setting or choosing a story card resets the visible ledger. Copy or download the current brief before doing that if you want to keep it.

The downloaded .txt is a readable copy, not an import file: this planner has no file-upload restore control. To rebuild a plan from it, choose the matching options and re-enter the relevant ledger details. Copies on the clipboard and downloaded files are not removed by the planner’s reset button.

Review a recap before reusing it

Check that it has not turned attention into attraction, a proposal into an agreement or a secret into shared knowledge. AI-generated summaries can omit details or introduce incorrect ones; SillyTavern’s summarization documentation explicitly recommends checking and correcting them. That describes SillyTavern, not a verified feature of WantYou.ai.

When the recap is accurate, use the brief handoff guide to continue from the current scene rather than replaying the original opening.

Return to the planner ↑

June’s story starts with an existing friendship. Iris’s starts with a past romance whose present trust still needs attention. Those are different beginnings even if both scenes take place over coffee.

Choose the relationship history first, then the setting. Slowly’s four presets provide different reasons for the characters to stay in the same story. None requires your character to return romantic interest.

Match the starting question to the story you want

The presets are fictional adults. Your character is also an adult, 25 or older, and you decide their actions, words and feelings.

Mara: disagree about a real task

The bookshop needs to reopen before the neighborhood fair. Give Mara a reason for her plan that goes beyond winning an argument. Perhaps she prioritizes fitting more titles into the display while your character values a clear entrance.

A possible opening for Mara:

“I can fit another shelf here.” She looks from the sketch to the doorway. “Tell me what I’m overlooking.”

This offers a professional disagreement the user can enter. It does not require them to have rearranged the shop before the conversation began.

If you want hostility without any reason to cooperate, this preset may need a different premise. Its useful tension comes from protecting the same project in different ways.

Elin: separate cooperation from full disclosure

A limited promise gives Elin room to act reliably without revealing everything. She can provide a catalog reference while declining to identify her source.

A possible opening:

Elin places a copied entry on the archive desk. “This is what I promised. The name in the margin stays covered for now.”

The next scene can test the document, discuss the limit or question whether the arrangement is workable. Respecting a boundary need not produce an immediate personal confession.

Choose another premise if you want open, established trust from the first exchange. Elin’s information boundary is part of the story’s starting problem.

June: keep the friendship intact

June does not need to become a stranger to make the romance gradual. Familiar habits and dependable support can stay. The uncertain part is what, if anything, the characters want to change.

A possible opening:

June sets a second coffee beside the exhibition plan. “I brought your usual. Want company while you work?”

The user can accept, decline, tease or focus on the task. A shared coffee does not become a date unless the characters establish that meaning.

Avoid assigning a hidden crush to the user’s character. “June wonders whether the friendship could change; the user’s feelings are undefined” leaves a different amount of room from “both secretly want more.”

Iris: let an apology stand without a reward

Iris’s unfinished promise gives the reunion a concrete subject. Agree on enough history to make the conversation intelligible; do not invent detailed past wrongdoing for the user’s character.

A possible opening:

Iris stops beside the concert schedule. “I can talk about the work first. If you want to discuss what happened before, I’ll listen.”

An apology can be specific without demanding forgiveness. A second chance might mean another conversation, a limited working arrangement or a respectful ending. Renewed romance remains a choice.

Changing a location is not changing the relationship

Moving June’s story from the coast to a café should not, by itself, erase the friendship you have played. However, this version of Slowly resets its visible ledger when you change the setting. Save an external copy first, then restore the relevant facts manually.

Once the starting state is accurate, choose a pacing instruction that supports the next scene.

Return to the planner ↑

For a new story, copy the full brief after reviewing its premise. For an ongoing story, preserve the current ledger and replace the original opening with a resume point in your copied text. Slowly’s generated brief still includes a preset opening even after you edit the ledger.

The planner does not send the brief to WantYou.ai. An external link opens a separate website; you decide where, whether and how to use the text.

Review the premise before the first exchange

Choose a dynamic and setting, then read the complete brief. Check the character ages, relationship state, unresolved issue and next possible step. Remove any detail you do not want established about your character.

Pay particular attention to the opening. If it says you already rearranged Mara’s display, decide whether you accept that as part of the premise. Otherwise, replace it in your copied text with an invitation to discuss the display.

The full brief field on this version of the page is read-only. Edit the planner’s available fields before copying, or edit the exported text in a text editor afterward. The planner has no dedicated opening-scene editor.

Put instructions where the service supports them

If the receiving service has a suitable scenario or instruction field, use it according to that service’s documentation. If it only has ordinary chat input, you can try a clearly labeled planning message, subject to its rules and capabilities:

Story setup, outside the fiction: use the following brief as guidance. Begin with the character’s opening, then stop for my response. Do not speak or act for my character.

Paste the brief below that message. This is a request, not a guarantee that an existing character or platform will adopt a new premise. Do not assume that WantYou.ai provides a particular field or supports importing Slowly’s characters; compatibility has not been established here.

Keep the character’s opening separate from your own first line. If Mara asks a question, your next contribution is your answer, not another copy of her question presented as your dialogue.

Continue from the latest accepted moment

After a session, update the ledger and copy the resulting brief. In that copy, replace the original opening with a short continuation instruction:

RESUME POINT:
The bookshop display discussion has finished. Mara and my character
agreed to leave the entrance clear. No romantic interest has been established.

NEXT SCENE:
Mara can bring over the event schedule and ask which task to tackle next.
Do not replay the first meeting or invent my character's response.
Keep the existing adult ages and non-explicit content boundaries.

Use this example only if those events match your story. A new session needs enough context to understand where it begins, but it does not need your entire hoped-for romantic arc presented as completed history.

Check the first response before adding more story

Look for a consistent starting state, the right scene location and an open choice for your character. If June suddenly treats a long-time friend as a stranger, correct the starting relationship. If Iris assumes forgiveness, remove that assumption before it becomes the basis of later events.

Use a targeted repair for an incorrect reply. Rewriting every instruction at once can make it harder to see which part of the setup was unclear.

Keep a copy you can recover

Download the brief or keep it in a text file after meaningful updates. The planner’s device save stores its fields, not a conversation held elsewhere, and it does not automatically preserve every version.

When you return, check the saved facts against the last accepted scene. The ledger guide explains how to preserve events, knowledge boundaries and open choices without confusing them.

Return to the planner ↑