product

Multiplayer Docking

How a machine becomes a Node on a project.

What docking is

dock is the verb a machine uses to attach itself to a project as a Node.

manifoldone dock ./my-game-prototype

After docking, the machine:

1. Registers its hostname, OS, and available tooling (CC version, Git or Perforce, etc.) with the project.
2. Opens a long-lived WebSocket to the relay.
3. Announces itself in the project’s Node list.

Why “dock” instead of “join” or “connect”

Because a Node is not just present — it is a working surface. The dock metaphor captures: arrive, attach, and become available for cargo. A docked Node is a place the project can route work to.

In Phase 1 (today): one owner, many devices

In the current single-user phase, only the owner of the docked machine connects to it. The “multiplayer” is between the owner’s many devices — phone, tablet, hotel browser. From any of them, the owner can chat with their agent and watch the work stream live.

In Phase 2 (next): N Nodes, M users

When license virtualization is in place (roadmap), the same dock command exposes the Node to permitted teammates. Multiple Nodes can be docked to the same project, and each can serve multiple users with a viewer or contributor role.

What’s parked

Docking today uses npx. Easier installation (single binary, drag-and-drop, OS service registration) is on the path to Phase 1 launch.