Installations and fleet scope

Two boundaries

A GitHub installation is the dashboard and configuration tenant. The Mirage owner is the physical scheduling boundary. One owner can connect a personal account and several organizations without merging their repository data.

Installation-scoped state

• repository access, visibility, and routing consent;
• installation mode and lifecycle status;
• CI job definitions, routes, experiments, and provider runs;
• dashboard runs and GitHub API rate limits; and
• device target membership and the visible machine view.

The installation selector is URL-stable, so a copied dashboard link keeps its tenant.

Owner-scoped state

• physical Mac identity and live device sessions;
• the fleet Durable Object, commands, reservations, and replay locks;
• one atomic slot pool shared across targeted installations; and
• owner infrastructure such as Cloudflare backend configuration.

Target a machine

Every Mac has an explicit one-or-more-installation allowlist. A machine targeted to multiple installations appears in each view and shares its physical slots, but it never accepts work from an installation outside that allowlist.

Open the machine from Machines, then use Available to to add or remove GitHub installations. Mirage applies the assignment immediately.