Share
The Share studio lets you pair a device and share memories peer-to-peer with a teammate — a direct, encrypted hand-off of what you choose to share, device to device. It’s the close-range counterpart to the org-wide team layer: a one-to-one bridge between two people’s local memory.
Peer to peer, by your choice. Zimac keeps memory on your machine; Share is how a specific memory crosses to a specific teammate — you pair, you pick what goes, and it syncs directly. It’s deliberate sharing between two devices, not a post to the whole org.
⇄ Pair a device
Connect directly to a teammate’s device to share.
⇄ Share memories
Hand over the notes or insights you choose — nothing more.
⇄ Peer-to-peer
A direct, encrypted sync between the two of you.
⇄ You decide
Sharing is opt-in and scoped to what you select.
What it is#
Share is the studio for one-to-one exchange. Where the Team hub broadcasts distilled conclusions to your whole org, Share is a direct link between two devices — you pair with a teammate and share specific memories peer-to-peer. It’s for the moment when the person who needs a piece of context is one person, and you want to hand it to them directly.
Pairing & sharing#
You pair with the other device, then share the memories or insights you choose — the sync is direct and encrypted, and scoped to exactly what you select. Nothing enters the sharing channel except what you deliberately hand over; model calls still follow the model route you configured.
Share vs the team layer#
Two ways to reach teammates, for two situations. Share is peer-to-peer — one-to-one, direct, for handing a specific memory to a specific person. The team layer (Signals, Broadcasts, Asks) is org-wide — for status, directives and questions across everyone. Use Share when the audience is one person; use the team layer when it’s the org.