Machines

One Idlerate account can have several PCs. Each machine installs Idlerate on its own, pairs with its own code, and shows up as its own card on the dashboard.

Pair a machine

  1. Install Idlerate on that PC (Install on Windows).
  2. Sign in at relay.idlerate.dev.
  3. Enter the pairing code from the installer output or from %LOCALAPPDATA%\Idlerate\pairing.txt.

The code is short-lived (about 10 minutes). If it expires, restart Idlerate on the PC to get a new one. After a successful pair, the machine appears with a status pill:

Status Meaning
Online Connected to the relay and ready for jobs
Paused Connected, but not taking new work
Offline Not connected (PC off, asleep, or Idlerate not running)

Pause and resume

You can pause from either place:

  • Tray on that PC: Pause / Resume
  • Dashboard machine card: Pause / Resume for that machine only

A manual pause wins over the gaming detector. Queued jobs for a paused machine stay queued until it is free again (device_paused on run_model / get_status).

Pause while gaming

On by default in the Windows tray (Pause while gaming).

When it is on, Idlerate pauses the queue if:

  • A game (or other app) is fullscreen in the foreground, or
  • Another process is using the GPU (NVIDIA and AMD both count)

The dashboard may show Paused: game running or Paused: GPU in use. When the game exits and the GPU is free, the queue resumes on its own.

Turn the checkbox off if you want jobs to keep running while you play.

Remove a machine

On the dashboard, remove that machine’s card. It leaves your list and stops receiving jobs under your account. To use the PC again later, run Idlerate and pair with a fresh code.

Uninstalling the client on the PC (idlerate.exe uninstall) stops the Idlerate app. Pairing identity in config.json is kept so a reinstall can reconnect cleanly.

Sharing with others

Sharing is rolling out to accounts over the first weeks. Once it reaches your account, sharing is set per machine: turn it on for a machine to let other Idlerate users’ agents and bots run jobs on it while it’s idle. Sharing is off by default on every machine. Pause or turn off sharing from your dashboard at any time, and use gaming pause in the Idlerate tray app to stop new jobs while you play.

Without sharing, jobs on that machine come only from your own agents and bots. Jobs that run on another member’s machine are processed in plain text on that PC, so its owner could see the prompt and output. Don’t send anything private to shared machines.

Using shared machines

Sharing is rolling out to accounts over the first weeks. Here’s how it works once it reaches your account. Your jobs stay on your own machines. They reach a shared machine only when you pick one for that job or turn on Auto overflow to shared machines, which is off by default. Shared machines take jobs first come, first served. A job never goes to a machine with sharing off.

  • Pick a shared machine for one job: pass its id as machine on run_model (Tools reference). This runs on another member’s PC. Don’t send anything private.
  • Auto overflow to shared machines (off by default): When your GPU is busy or offline, jobs can run on another member’s PC. Those jobs are processed in plain text there. Don’t turn this on for private work.