Tutorial · Task guide

Create a Companion with Editable Memory and Safe Proactive Messages

Updated · 2026-08-10Public document
Direct answer: Create a Companion from Home or convert an imported character card, then review its persona and memory before chatting. Keep proactive messages off until the text/lightweight-task model, enabled message slots, quiet hours, daily limit, notification permission, and spending channel are correct. After enabling, inspect the first generated message and keep an exported Companion backup outside the app.

Before you start

  • A connected text model; image/TTS providers are optional for selfies or voice.
  • A clear persona/relationship boundary, or an imported card you are allowed to use.
  • Notification permission if you want messages outside the app.

Where to find it

  • Home > Companion
  • Companion > Memory
  • Companion profile > Let them reach out
  • Companion profile > Promises with them
  • Companion profile > Export companion backup

Step-by-step

  1. Create or import the Companion

    From Home, choose Companion creation or create from an imported character card. Set the displayed name, persona, relationship style, and confirmed reference image only if you want visual generation.

  2. Check the initial home and memory

    Open the Companion, read the profile/style, then open Memory. Add one stable fact manually and remove anything you do not want used later.

  3. Have a short grounding conversation

    Send a few messages that establish a real preference or plan. After memory extraction runs, review the new memory item for accuracy, duplication, and privacy.

  4. Configure proactive messaging before enabling

    On the Companion profile, review Let them reach out and the individual morning, evening, miss-you, anniversary, battery, and weather slots. Open Promises with them to set quiet hours and the daily maximum. Confirm Android notifications and the text/lightweight-task model under AI Models & Services, read the cost disclosure, and only then enable the master switch.

  5. Verify and prepare portability

    Wait for a normal eligible slot, then inspect the notification and saved message. Use Companion profile → Export Companion backup, store the zip somewhere private, and verify Restore Companion backup can select it before deleting anything.

How to know it worked

  • Persona and relationship style match what you intended.
  • Memory shows only accurate, editable facts and no accidental secret.
  • Message slots, quiet hours, daily limit, and the master switch reflect your choices after reopening settings.
  • A proactive message opens the correct Companion conversation.
  • A Companion-backup zip exists outside the app.

Cost, data, and irreversible-risk notes

  • Creating/editing the local profile is free. Conversations, memory extraction, proactive messages, selfies, TTS, and other generated media may use separate model calls.
  • When proactive messages are enabled, the app may call the selected text/lightweight-task model while you are away. Use individual slots, quiet hours, a daily limit, and a suitable low-cost model; turning the master switch off prevents future scheduled generation.
  • Memory is editable local relationship data, but selected context is sent to the chosen provider during generation. Do not store passwords, API keys, OTPs, or information you would not send to that provider.
  • A Companion backup can contain intimate profile, memory, chat history, and assets. Treat it as sensitive personal data.

Troubleshooting

No proactive message arrives

Likely cause: Master switch or that message slot is off, no slot is due, quiet hours/daily limit applies, notifications are denied, background work is restricted, no usable model exists, or generation failed.

What to do: Check the master switch, enabled slots, next eligible window and daily limit; allow notifications, remove battery/background restrictions where appropriate, verify the text/lightweight-task model, then inspect request records rather than repeatedly toggling.

A message arrives during quiet hours

Likely cause: Device time zone/clock or configured window differs from expectation, or it is a delayed notification for an earlier generated message.

What to do: Confirm device time zone and the displayed quiet-hour range, inspect message/task time, and report a reproducible mismatch without changing system time.

Memory is wrong or duplicated

Likely cause: Extraction inferred too much, the same fact was phrased differently, or an old conflicting item remains.

What to do: Edit/delete the wrong item, merge duplicates into one plain fact, and correct the Companion in chat. Keep only durable facts, not every passing mood.

Restored Companion is missing assets

Likely cause: The backup was incomplete/corrupt, referenced files were unavailable, or the package came from an older incompatible state.

What to do: Keep the source Companion, export again with assets available, verify file size, and restore into a test copy before deleting the original.

Frequently asked questions

Are proactive messages on by default?

No. The creation flow asks once; if you decline or dismiss it, proactive messages stay off. Enable them only after reviewing message slots, quiet hours, the daily limit, notifications, and the model/spending channel.

Can I edit what the Companion remembers?

Yes. Long-term memory is visible and editable; remove mistakes, duplicates, or private facts you no longer want used.

Will turning proactive messages off delete memory?

No. The switch controls future proactive generation, not the Companion profile, chat, or memory. You can export those separately.

Sources and verification

  1. Agent and Companion guide · Foreverse · Verified

Coverage and verification

PlatformAndroid Companion
App versionv76+
Path verified

Tutorials & Help