Skip to main content
Use bead GitHub Actions runners to provision a fresh temporary machine for each matching job. GitHub assigns the job; bead bills and deletes the machine for that assignment.

​
Connect selected repositories

Create selection.json with repositories you control and templates available to your account:
The command opens GitHub installation and authorization, then waits for confirmation. You must have installation-management authority: the installation belongs to you, or you are an active organization administrator. Confirm the bead organization and selected repositories. Repository runners require Administration write, Actions read and Metadata read permissions. Install the App only on the repositories you want to run.

​
Select a runner

Configure matching template resources for each label. Explicit selectors such as bead-4x8 and configured custom bead-<name> labels are supported. Append /from=<golden> to choose a matching saved toolchain, or /debug to retain a failed job machine for 30 minutes subject to normal funding. Each job must request exactly one label beginning with bead, and its base selector must have an entry in selection.json.templates, including explicit selectors such as bead-4x8. Put suffixes such as /debug and /from=TOOLCHAIN on that same label. Runner machines are retired when their age reaches six hours. Keep jobs within that lifetime.

​
Inspect jobs and logs

Live logs poll a bounded 1 MiB buffer of masked GitHub job pages. Truncation is explicit. Live sampling is best effort; GitHub keeps the authoritative completed logs. Public repositories are off by default. An administrator can allow selected actors with bead ci public owner on --users alice,bob, allow anyone with --anyone, or disable access with bead ci public owner off. Both the original and triggering actors must be allowed. bead ci disconnect "$INSTALLATION_ID" disables provisioning and retires owned machines. Check limits and funded balance before running jobs. For other CI systems, use portable CI.