Skip to content

Assistant ​

The assistant can look up anything you may see in the family and suggest changes: new events, list items, routines, meals, reminders and more.

It asks first ​

Every change appears as a card. Nothing is saved until someone taps Save. The assistant uses the same permissions as you: a read-only member cannot save changes through it either.

Use Review and edit to inspect a draft's fields before confirming. Saving the editor updates only the pending draft; the separate card confirmation applies it to family data. Nested action fields use JSON. The action and target IDs stay fixed; dismiss and request a new draft to change the target. Deletion cards show the action and target IDs and require a second confirmation.

Memory and context ​

  • The chat remembers earlier messages. Older parts are summarised automatically.
  • After 12 quiet hours a fresh chat starts. The summary carries over, and lasting facts and open tasks are kept as memories.
  • See, pin and delete memories from the memory sheet in the assistant.

Reminders from documents ​

Attach a PDF or a photo of a school letter and ask "remind me of the deadlines". The assistant reads it once, proposes reminders on the right days and does not keep the file.

You can also attach plain text, CSV or Word .docx files. Word intake reads the main document paragraphs and tables, without opening links, embedded objects, macros or images. Headers, footers and legacy .doc files are not supported. Files are limited to 10 MB; Word's main XML is limited to 2 MB after decompression and assistant text to 30,000 characters. Review the extracted dates and drafts before confirming them.

The in-app assistant can also draft member invitations and profile/role changes, member removal and external calendar subscriptions. Live location and arrival alerts are disabled. The confirmation card shows the action, target IDs and complete fields; review them before saving. Existing administrator and visibility checks apply again when you save. These actions are excluded from public API tokens and MCP. Family closure/ownership transfer, sharing-link issuance, BYOK consent, account credentials and billing remain in their dedicated settings flows. The assistant can propose calendar-link enablement and maximum lifetime settings with administrator confirmation; it cannot change BYOK consent or ownership-recovery opt-in. Uploading new binary media still uses the upload picker; the assistant manages existing media metadata and deletion.

Voice ​

Plans with voice (or your own OpenAI key) can speak a question and hear the answer. Audio is never stored.

Your own AI key ​

On iOS and Android you can use your own OpenAI, Anthropic or Mistral key:

  • The key is stored only in the phone's Keychain/Keystore and goes straight from the phone to the provider. It never reaches Fellesly.
  • A family administrator must allow it first, because the questions and the family data the assistant looks up go to the provider you picked.
  • Not offered on the web: a browser cannot keep a secret safe.

Fellesly: the family, in one place.