pi-xfer Mesh — a cross-machine handoff

The mesh layer of the transport map: one actor per pi session, engine-side discovery, durable queue

pi-xfer Mesh — a cross-machine handoff The mesh layer of the transport map: one actor per pi session, engine-side discovery, durable queue mesh.config.json · ~/.pi/xfer · endpoint · namespace · token · Machine 1 mesh.config.json ~/.pi/xfer · endpoint · namespace · token pi session “alpha” — Machine 1 · in-process actor runner · /xfer mesh up · Machine 1 pi session “alpha” — Machine 1 in-process actor runner · /xfer mesh up Engine / control plane · RivetKit · actor registry · discovery · Architecture component · <endpoint>/ui Engine / control plane RivetKit · actor registry · discovery <endpoint>/ui pi session “beta” — Machine 2 · Node · xfer-instance actor · Machine 2 pi session “beta” — Machine 2 Node · xfer-instance actor Durable handoff queue · actor queue “handoff” · document sent inline · Machine 2 Durable handoff queue actor queue “handoff” · document sent inline read at /xfer mesh up connect out · register actor discovery · route to target actor enqueue inline handoff drain when online Machine 1 Machine 2 Legend Backend Database Cloud Message bus