Contribute a machine
Contribution is voluntary. A machine advertises only the resources and compute mode selected in the application, and contribution can be paused without leaving the account or uninstalling the client.
Choose a participation method
| Method | Best for | Availability |
|---|---|---|
| Desktop application | Persistent contribution and local diagnostics | Runs independently of a browser tab |
| Browser worker | Short tests and mobile devices | Runs while the session remains visible |
| Source worker | Runtime development and controlled deployments | Requires a source checkout |
Enable desktop contribution
- Open This machine.
- Review the detected CPU, memory, GPU, and runtime state.
- Enable contribution.
- Choose the compute preference shown by the application.
- Keep the application running while the machine is available.
The coordinator may leave a connected machine idle. The scheduler selects a node only when its memory, execution backend, topology, and current availability improve a real route.
Pause safely
Use the contribution control in This machine or the tray menu. Pausing stops new work from being assigned. An active task may enter a draining state so the network can finish or move it without silently losing the request.
What is shared
The worker reports the hardware and deployment information required for scheduling. Model activations are visible to a node that processes them; transport encryption does not make activations anonymous to that node.
Use a private network or a set of trusted nodes for sensitive prompts and model data. Do not assume that an untrusted compute provider cannot inspect the data it must process.
No earnings promise
The current product does not expose a live token economy or guaranteed compensation. Any future incentive system remains separate from today's contribution controls and must be introduced with auditable accounting and explicit terms.