Editing replies and pinning messages

Edit changes a message. Pin keeps a useful detail available to the conversation. Saving an exchange keeps a scene you can return to.

Correcting a reply

  1. Open the actions for the reply you want to change. On desktop, right-click the message to find Edit.
  2. Correct the wording, factual detail or point of view.
  3. Save the edit, reread the exchange and continue from the corrected version.

If the reply assigns a decision to your persona, replace that sentence with an observation or question. Keep the character's own response intact.

Adding and managing a pin

Open a message and choose Pin. Use Pinned Messages in the chat to review or change what is pinned. Keep each note brief; around 800 characters or fewer is a useful target, not an invitation to fill the space.

Updating or removing a pin changes the stored reminder without rewriting the original message. More about context and saved scenes.

A correction that leaves the scene intact

Suppose the reply places your meeting at the south gate, but both characters agreed on the west gate. Correct the location, then keep the conversation moving. You do not need a new character biography to fix a place name.

A focused reminder would be: The courier is waiting at the west gate with the unopened case. Remove it after the handoff so it does not compete with a later destination.

Continuing in another direction

When you want to explore a different decision, keep the last agreed facts and start a separate continuation. If the chat provides a Branch action, review its starting point before adding another reply.

For a scene you want to revisit, use Save Memory. For text layout rather than story facts, use message formatting.

Frequently asked questions

Does removing a pin delete the original message?

No. Managing the reminder and editing the original message are separate actions.

Should I pin every message?

Pin the facts the next scene needs, such as a current promise or destination. Keep a longer exchange as a saved scene instead.