Handovers · all pages

TEAMS AND ORGANISATIONS

Handovers

Send a frozen brief from one person to another — the recipient picks it up in any AI, without starting over.

A handover is a brief from one person to another. It carries the context, what was decided and why, what was tried and ruled out, what remains and the next step. The recipient reads it from any connected AI with handover_inbox, or in the console’s Inbox, and continues the work without being handed a wall of chat logs to decipher.

Sending a handover

Ask your assistant: "Create a handover to <name or email>, summarise where things stand with <project>, and include the relevant memories." Your assistant calls handover_create with the recipient, a subject, the brief, and optional refs — the ids of the memories behind it. The brief is encrypted under the recipient’s own key; you cannot read it back.

Receiving a handover

  1. Check the inbox. handover_inbox lists briefs addressed to you, with sender, subject and date. The same list is under Inbox in the admin console.
  2. Read it. handover_get <id> shows the full brief: subject, context, decisions, what was rejected, what remains and the next step. Any attached memories can be followed with flow get <ref-id>.
  3. Accept it. handover_accept <id> marks it done. Idempotent — running it again has no effect.

What a handover is not

  • It is not a workspace memory. It is excluded from recall, never enters the Soul, and is not searchable.
  • It is not email. An email notification is sent (sender, subject, that a handover is waiting) — never the brief itself, which stays in Flow.
  • It is not for ongoing shared work. For that, use a project box.

A handover lives in the personal scope of the recipient, encrypted under their key. If the recipient deletes their account, it is destroyed — that is their right.

Docs version 1.3 · Something unclear or missing? Tell us.