My cofounder Hudson and I already had our Macs connected with Tailscale, but our Codex and Claude Code sessions were still isolated. If one of us was 40 turns deep, the other got a summary, a screen share, or a finished commit not the conversation itself.
We built mpai around a narrower bet: do not replace the terminal or the native agent. Let a trusted teammate enter an explicitly shared session, arrive with its real context, and add an attributed turn from their own Mac.
The public alpha works with Claude Code and managed-mode Codex. The host stays in control, and standalone Codex remains view-only by default.
Where should the trust boundary land for teams? Is an owner-controlled shared session meaningfully better than moving everyone into a hosted collaborative IDE, or does it still feel too close to remote access?
mpai
PRISM by Block Convey
mpai
Yes—if you mean mpai, it is MIT-licensed, so commercial use is allowed. For a client environment today, I’d run it only on a client-owned Mac and tailnet the client controls, have them explicitly invite you and share the exact session, and start with a non-sensitive pilot. The host keeps execution authority; mpai exposes no arbitrary shell and cannot bypass approvals. It is still a macOS public alpha, not an enterprise SLA product yet. If you test it, I’d love your install-to-first-room time and where the flow breaks.