#How to read updates
Each entry identifies the release date and the part of the product that changed. On long guides, use On this page in the screenshot below to jump to Exact clicks or Common questions without scrolling.
The changelog is not a roadmap — a feature appears here after it is live.
Publication rule: Only released features belong here
A changelog note records what can be used or observed in the live product, not an internal plan.Navigation addition: Keyboard-first Wiki search
Use Cmd/Ctrl + K in the Wiki to find a named feature, action, or error phrase.#July 2026: Help Center launch
Mistress.to now has a public wiki for onboarding, chat, memory, custom characters, visuals, tokens, billing, and support.
Press Cmd/Ctrl + K in the screenshot below to search by control name, then open the linked guide when a workflow changed.
Latest documented release: July 2026: Help Center launch
The initial release covers onboarding, chat, memory, creation, billing, account controls, and support guidance.Verification rule: Confirm the live screen
If a guide and a visible control differ, trust the live product and report the mismatch with the exact screen details.How to use a release note
A useful note says what changed, where it changed, and how a reader can verify it. This makes old notes less likely to be mistaken for current workflow instructions.
| Release entry | What changed | How to verify |
|---|---|---|
| July 2026: Help Center launch | A public wiki with focused guides across five product areas, structured article metadata, and image-ready walkthroughs. | Open the Wiki, use search, then follow a guide's exact-click path to the live screen. |
| Future feature note | A user-visible capability, control change, or resolved issue after release. | Open the linked guide and confirm the named control is present in the product. |
| Older note | Historical behavior at the time it was published. | Do not rely on it for pricing, eligibility, or labels without checking the current live flow. |
#What a useful release note contains
A useful entry names the user-facing change, identifies the affected screen, and links to the detailed Wiki guide. It should say what a user can click or observe, not repeat an internal label. That format also gives search and AI systems a clearer way to distinguish current behaviour from an older product state.