Set up your Mac
Install the add-on, approve the Mac, choose work disks, and set the slots, cache and schedule.
Check your Mac's status
Every status state, the free-disk floor, and what to do when a job waits or the Mac stops taking work.
What your Mac runs
CI jobs. These are GitHub Actions jobs from public repositories that Darkbloom reviewed and approved. Each job gets its own Linux or macOS VM, created for that job and deleted when it ends. A Linux VM has 4 or 8 cores and 16 or 32 GB of memory; a macOS VM has 8 or 12 cores and 16 or 32 GB. The repository’s approval sets the size. Jobs are placed only on Macs with room for them, so a larger job needs more free cores, memory and disk. Agent sandboxes. These are interactive Linux and macOS VMs that accounts on Darkbloom’s alpha list start, connect to with SSH or a screen (VNC), and use for coding agents such as Codex. Agent sandboxes are on by default from add-on 1.3.0, and you can turn them off. A sandbox has 4 to 12 cores and 8 to 32 GB, as its user chooses. A run stops after at most 24 hours, and earlier when nobody is connected and it moves no traffic for its idle limit (at most 2 hours). Its workspace stays on your Mac while the sandbox is stopped, so its user can resume it. macOS sandboxes run only on Macs that also run macOS jobs, in their macOS slots. Darkbloom deletes a sandbox that stays stopped for 30 days by default, and its workspace with it.What a VM can reach
- A VM has no network card and no shared folders. It cannot see your files, your apps or your home network.
- Its only connection to your Mac is a virtual socket to the worker process that runs it. The VM’s traffic leaves through Darkbloom’s gateway in an encrypted tunnel that your Mac relays but cannot read.
- The gateway connects only to hosts on the VM’s list, on port 443. For a CI job, that is GitHub’s Actions hosts plus hosts Darkbloom reviewed for that repository. For an agent sandbox, it is Darkbloom’s list for coding tools or the hosts its user named.
- The traffic still uses your Internet connection, and the servers see the gateway’s address, not yours.
- A job or sandbox cannot open a port on your Mac or your router. Agent sandbox users connect through the gateway.
How it works with the inference provider
Both run on the same Mac and take turns:- Before a VM starts, the agent asks the inference provider to pause. The provider stays connected, finishes the requests in flight, unloads its models and takes no new requests. This takes seconds to minutes.
- Darkbloom counts the memory your models use as free for jobs, so a busy provider can still be paused for a job. You earn nothing from inference while it is paused.
- Shortly after the last VM exits, the agent releases the provider and it serves again.
- If the provider refuses to pause, or does not pause in time, the Mac turns the job down, and Darkbloom places it on another Mac.
The change applies at once, without a restart. A job that already paused inference keeps it paused until it ends. With
never, no new job joins it. Your choice stays on the Mac, in the same settings file as your schedule.
What you need
Recommended Macs
The tiers fit Darkbloom’s own CI jobs: Linux VMs of 4 cores and 16 GB, and macOS VMs of 12 cores and 32 GB. Slot sizing leaves you a quarter of the cores and of the memory, and the inference provider another quarter of the memory, so a macOS job of that size needs a Mac with at least 16 cores and 64 GB.- Tier 1 runs a macOS job and Linux jobs at the same time.
- Tier 2 usually runs one job at a time, macOS or Linux. With 128 GB, a Linux job can run beside a macOS one.
- Tier 3 runs Linux jobs only; a macOS job does not fit.
df -H ~ shows it (Avail). Finder can show more, because it counts purgeable space. Set up your Mac explains the floor and what each job needs.
Every Mac
You can keep using the Mac. Darkbloom’s VMs together never get more than three quarters of the memory: a quarter (at least 8 GB) stays yours, and a VM starts only when the Mac reports enough free memory for it. A VM larger than the Mac’s memory less your quarter never starts: on a 36 GB Mac, no 32 GB VM. CI slots also leave you at least a quarter of the cores. To keep more cores, set Cores you keep on the Mac’s page in the console; the default is 0, which leaves the slots to limit the cores.
What you earn
Darkbloom keeps a 10% platform fee, so you earn 90% of each CI job’s charge and 90% of each agent sandbox’s charge. The rates below are as of November 2026. A busy hour means the job or sandbox uses the Mac for the whole hour; earnings depend on demand, and no utilisation is promised.CI jobs
Rates are stored per minute and shown in the console under Billing → Rates. Billing is per second, from when the job starts on its runner to when it finishes, with a one-minute minimum and a 60-minute maximum. Queue, boot and teardown time are not billed. A slot sized for the smaller class earns the first row of its platform; a larger job runs only where the Mac has room for it.
Agent sandboxes
These are the 4 to 12 vCPU sizes a provider Mac hosts, as its user chooses.
darkbloom-sandbox-cli sizes lists them and which sizes your account may boot. A sandbox bills per second from the moment it is ready, with a one-minute minimum per charge (each boot, and each further hour a long boot runs), and a stopped sandbox costs nothing. It earns for the time it runs, whether or not its user is connected, within its idle and maximum limits.
When you are paid
- Each CI job settles on its own after it finishes. Your share goes to the withdrawable balance of the Darkbloom account that approved the Mac, as sandbox earnings. Agent sandbox charges earn the same 90% and are credited to that account. You withdraw the balance the same way as inference earnings.
- A job lost to the Mac or the VM is neither charged nor paid. That covers a Mac that went offline, slept or crashed, and a VM that failed to start.
- Jobs your own account pays for are free on your own Macs. They settle at $0: no charge and no payout. Darkbloom prefers your Macs for those jobs.
- Billing → Earnings in the console lists the settled jobs on your Macs.
Waitlist and approval
Your account must be approved to host Macs. Depending on how you install, you meet that approval in one of two places.- The Darkbloom Sandbox waitlist. With the Darkbloom provider CLI,
darkbloom waitlist sandboxputs your account on the waitlist and shows your place in line. Run it again to see where you stand; it keeps your place. The waitlist is per account, not per Mac, and Darkbloom reviews accounts in the order they joined.darkbloom sandbox setupalso offers to join when your account is not on the waitlist, then stops until Darkbloom approves it. - The owner waitlist. If you install with the add-on’s installer, the approval page asks you to sign in. If your account is not approved as a Mac owner, your request joins the owner waitlist and the Mac waits up to 7 days for Darkbloom to decide. From add-on 1.2.0 you can close the setup window: the Mac keeps waiting, also across restarts and macOS updates, and enrolls by itself once approved. Running the installer again shows the same code.
darkbloom login session cannot approve a Mac. If the Mac hosted before, its code replaces the old host, and the approval page asks you to confirm the replacement.
Next steps
- Set up your Mac: install, approve, choose work disks, size the cache and schedule the Mac.
- Check your Mac’s status: read every state and fix the common problems.
- Inference provider earnings: withdraw the balance that sandbox jobs pay into.

