Product
What is multAIplayer?+
Native macOS desktop and command-line clients where trusted teammates collaborate around one locally hosted Codex session. Both clients share encrypted rooms, conversation, Codex activity, approvals, and explicit host handoff. The desktop also provides files and diffs, shared terminals, browser previews, and Git/GitHub workflows. Read the desktop guide or CLI guide.
How do I install and start using the CLI?+
On an Apple-silicon Mac, run curl -fsSL https://raw.githubusercontent.com/maddiedreese/multAIplayer/main/apps/cli/install.sh | sh. The signed, notarized CLI installs in your user account without sudo or an administrator password.
Then run multAIplayer auth login --open. GitHub opens for device authorization, the terminal confirms your account, and the CLI prints a walkthrough covering room creation or joining, encrypted chat, Codex hosting, and host handoff. Replay it with multAIplayer walkthrough. See the CLI guide for every command and current limitation.
Does host handoff work between desktop and CLI?+
Yes. Either supported client can hand future host authority to a verified member through the same authenticated room boundary. The incoming host selects its own local project and uses its own credentials and Codex session. Handoff does not transfer filesystem access, credentials, running processes, terminal or browser sessions, or the outgoing host's Codex session.
Who controls the host machine?+
One active host supplies the project, Codex process, tools, credentials, and approval decisions. Teammates can propose actions, but consequential local work crosses host review and native authorization. Approval still carries real risk; see the threat model.
Does multAIplayer replace Codex's system or developer instructions?+
No. The app uses the standard open-source Codex app-server on the active host. For an approved turn, it constructs a bounded ordinary user-turn prompt from attributed room conversation and selected context, with product-authored safety framing that explicitly labels untrusted material.
Trust
How are rooms encrypted, and has this been audited?+
The mechanism uses RFC 9420 MLS through mls-rs, with native-client encryption and exporter-derived protection for relevant payloads. The integration has not received an independent professional security audit. The threat model is the sole normative claims source, and the alpha limitations summarize practical constraints.
What can the relay see and retain?+
The relay authenticates devices, authorizes access, routes encrypted records, and retains bounded operational state and backlog. Some identity, routing, size, timing, and lifecycle metadata is necessarily visible. The exact inventory, retention, deletion, and compromised-participant boundaries live only in the threat model.
How should I handle an invite link?+
Treat the complete HTTPS link as a bearer secret. Send it only through a private channel, never logs, issues, or support requests. If it leaks, invalidate it and do not approve an unexpected device. The user guide explains the universal-link flow.
Operations
Can I self-host?+
Yes. Internet-facing deployments need TLS, exact origins, authentication, persistent SQLite storage, backups, health monitoring, and abuse controls. Official clients pin the hosted relay, so another origin requires a self-built app. Follow the self-hosting guide.
How are desktop updates protected?+
Supported releases are Developer ID-signed and notarized. The desktop updater uses the application repository's pinned update-channel branch and accepts only archives carrying the Tauri release signature. The website's release manifest drives download links; it is not an updater trust root. This site separately publishes the pre-committed updater-key fingerprint so it can be compared outside the GitHub release channel. Releases also publish SHA-256 checksums for manual verification. Follow the verification guide.
Scope
What platforms are supported?+
The public desktop and CLI alphas target Apple-silicon macOS 11 or later. Intel Mac, Windows, and Linux releases are not supported, and Homebrew packages are not currently available. Current Codex compatibility is recorded in the Codex hosting guide; CLI-specific differences are listed in the compatibility table.
Is the alpha appropriate for private work?+
Start with a disposable or public repository, trusted collaborators, dummy credentials, a separate branch, and recoverable backups. Read the threat model and alpha limitations before introducing sensitive code. High-stakes use should wait for independent review and greater operational maturity.