The most useful controls are the ones with a defined purpose. We distinguish editable inputs from outcome promises: a documented memory tool does not establish perfect recall, and an instruction field does not mean every instruction will be obeyed.
Persona and scenario definition
The official Quick Start names personality, appearance, scenario and example conversation fields. These are useful because a reader can decide where each detail belongs before starting a chat. Put a stable manner in personality, the immediate setting in scenario, and a short demonstration of voice in examples. Keep the character explicitly adult. Avoid repeated descriptions that spend the available context without adding new guidance.
Character visibility is also documented: public, unlisted and private are separate choices, and definition visibility can be controlled. These settings concern how a character is shared, not whether the provider can process your conversations. Choose the least public setting that serves your purpose. If you intend to share a character, remove identifying details and inspect which parts of the definition a viewer can see.
Reply editing and custom instructions
The Chat Features guide describes editing character replies. The Instructions Guide explains guidance for tone and behavior, while warning that instructions may be ignored or resisted by model defaults. This is a meaningful limitation. Editing a reply can repair the text you see, but it does not prove that the underlying system will preserve the correction in every later exchange.
For our CrushOnAI review, the distinction supports a controlled setup process. Change one instruction, check a small sequence and keep the version that behaves more consistently. A request such as “Use two short paragraphs and let me choose my own actions” gives you something observable. If a response ignores it, simplify the request before assuming that adding more description will help. Our persona editing guide develops this approach.
Memory pins and saved conversations
The wiki documents editable memory pins and a saved-memory workflow. Selected messages can be saved with visibility settings, reloaded and summarized. Those are useful tools for carrying chosen facts forward. They are also operations a reader must understand: a manually pinned detail, a saved conversation and automatic recall are not interchangeable capabilities.
We have not measured how reliably the system retrieves those details during a long exchange. We also did not verify the detailed branching procedure, even though branching appears in feature navigation. If continuity is your priority, try a neutral fact that you can check after a topic change. Consult the short conversation setup for a small evaluation sequence rather than committing to an elaborate story first.