Skip to help content
Remembud HelpOpen journal in a new tab

Next-release help preview. These guides are being checked before publication. Availability depends on the release and account you use.

Candidate guidance

How do sources and memory work?

Eligible earlier owner-authored writing may support a specific useful connection when memory is enabled. Similar topics alone are not enough. The current-entry reflection stays intact; supported memory may add an ending with the earlier date and link. No useful result, insufficient time or an error should leave the complete current-entry reflection. AI recall and relevance are not guaranteed. Public source packs and private writing have different permissions. Memory is not reserved for a paid plan: whenever free reflections are offered, some memory-assisted reflections must be free too. No allowance amounts or prices have been set. Where limits are configured, the entry shows how many reflections are left, and Refresh only re-checks.

What to do

  1. Follow a cited entry link to check the source.
  2. Exclude source writing or switch memory off to restrict future reuse.
  3. A prior AI interpretation is not proof that an event happened.

Related questions

Can I pin five messages for memory?

The pilot does not inherit another service’s five-message pinning control. Eligible memory uses permitted owner writing under Remembud’s current controls. A private context-pinning editor needs its own released behavior and must preserve exclusions.

Why might a character not recall something?

Available context is bounded. Relevance, permission, time and output space can all prevent a memory connection. A current-entry reflection still stands on its own, and recall is not guaranteed.

Does a new response style change memory or share my writing?

Response style, remembered context and public sharing are separate choices. Check actual request context and memory controls before asking for a reflection. A competitor announcement does not activate a new model, public profile or media-sharing feature here.

Does going back to an earlier point remove later writing?

Moving through history must preserve the original record and its versions. An alternative reply or conversation branch is separate from deleting later writing. Do not apply another service’s destructive rewind instructions to a Remembud archive. Model choices and excluded words need their own visible controls.

Do automatic memory and image attachments share the same permission?

No. Remembered context, excluded answers, attached media and public sharing each need their own controls and actual request preview. A competitor’s image quota, automatic-memory behavior or model experiment does not enable those features here. Use the controls and availability labels in the released Remembud app.

Will importing another tool’s lorebook preserve all of its rules?

No lorebook importer is generally available in this pilot. A future importer must preview its supported fields, limits and any omitted activation rules before applying changes. Keep the original file, validate titles and keywords, and preserve source identity. A lorebook import is separate from restoring a private journal and must not publish or activate material silently.

Do tags, pins or memory improvements change the information sent for a reflection?

Organisation and request context are separate controls. Check the actual context and exclusions for your request. A pin or favourite should not publish writing or silently add it to another character’s request. New model, media and memory features need actual release evidence; competitor announcements do not activate them here.

What makes character guidance useful and safe?

Keep guidance specific, relevant and sourced. Correct a known fictional detail or describe a consistent response style without presenting an invented fact about the writer. Name facts that belong to one character instead of applying them to every speaker. Guidance can shape a response but cannot override exclusions, permissions or the actual request preview. A general lorebook editor is not available in this pilot.

Does linking shared character guidance share my personal memories?

No. Reusable character guidance and personal journal context are separate. Linking a portrayal to source material must retain its author and exact version, without granting another creator access to your writing. Draft edits must not silently replace a version used by an earlier request. A general public lorebook builder and linking workflow are not available in this pilot.

Was this guide useful?

Prepare feedback to copy or download, or review a metadata-only support request in your journal when contact is available. Nothing is sent from this guide.