multAIplayer

Build with Codex. Together.

Multiplayer Codex for trusted teams: discuss the work, steer one shared local Codex session,
review what it changes, and hand hosting between teammates.

Website · User guide · CLI · FAQ · Threat model · Contributing

Command-line client

Install the Apple-silicon macOS CLI with one command:

curl -fsSL https://raw.githubusercontent.com/maddiedreese/multAIplayer/main/apps/cli/install.sh | sh

After sign-in, the CLI prints a walkthrough covering room creation or joining, encrypted chat, Codex hosting, and authenticated host handoff. See the CLI guide for the complete flow, compatibility, limitations, updates, and uninstalling.

The product

Start a private project room, invite people you trust, and work with Codex as a team. Everyone can follow the conversation, propose the next turn, inspect structured progress, review changes, and use room-scoped files, diffs, terminals, browser previews, Git, and GitHub workflows. One active host supplies the project, local tools, credentials, and Codex account; an explicit handoff can move that responsibility to another verified member.

multAIplayer does not provide or replace Codex's system or developer instructions. It connects to the standard open-source Codex app-server running on the active host. An approved room turn becomes ordinary user-turn input: the app formats the selected conversation and attachments, and explicitly labels teammate, file, terminal, browser, and tool material as untrusted context.

Independent project

multAIplayer is an independent open-source project. It is not an official OpenAI or Codex product and is not affiliated with, endorsed by, or sponsored by OpenAI. OpenAI and Codex are trademarks of OpenAI.

Security posture

Rooms use RFC 9420 MLS through mls-rs; the relay routes encrypted records while observing the metadata required to operate the service. The integration is unaudited. The threat model is the sole source for security properties, assumptions, metadata exposure, and residual risks; SECURITY.md explains private reporting.

Build locally

The Apple-silicon terminal client has a separate installation and quickstart guide. Its binary, version, checksums, signing, and release process are independent from the desktop updater and artifacts.

Prerequisites are Node.js 24.x, npm 11.16.0, Rust 1.89.x/Cargo, Xcode command-line tools, and Codex:

npm install --global npm@11.16.0 --ignore-scripts
npm ci
cp .env.example .env
npm run doctor

Then run the native app:

npm run tauri:dev

Tauri starts the local relay and Vite process for this command. The example environment uses an intentionally unauthenticated loopback relay, so GitHub identity sign-in is unavailable in this local mode. An authenticated or custom relay requires a self-built client as described in Self-hosting; production startup rejects the local auth opt-out.

Run focused checks for the area you change; CI runs the complete repository gates:

npm run check
npm test

Pull requests run workspace checks and product journeys when executable code changes. Scheduled workflows provide focused fuzz, supply-chain, container, and Codex-compatibility checks. Releases rerun supply-chain checks against the exact tag before verifying signing, notarization, authenticated updater metadata, the required release asset set, and checksums. Workflow definitions are the source of truth for the current gates.

Repository map

Path	Responsibility
apps/desktop	React/Tauri desktop, host workflows, native capabilities
apps/cli	Rust terminal client and independent CLI packaging
apps/desktop/src-tauri/crates/mls-core	MLS, invite cryptography, exporters, encrypted state
apps/relay	Authenticated transport, SQLite persistence, and quotas
packages/protocol	Shared wire records and runtime validation
e2e	UI contracts and multi-process journeys
docs/decisions	Normative architecture decisions

The architecture guide maps product flows to code. Durable relay behavior and its deliberately single-node boundary are documented in the single-node relay ADR.

Releases and operations

Release verification is documented in Verifying releases. Relay operators should follow Self-hosting; the free hosted relay has no uptime or recovery guarantee.

Contributions are welcome; start with CONTRIBUTING.md. Apache-2.0 licensed. Third-party notices are in THIRD_PARTY_NOTICES.md.