Browser-farm orchestration for Flow workers.

Global v0

Caps ready accounts offered per worker poll. Current effective value is 4.

Hard cap on accounts running a job AT ONCE on one box (unlike claim groups/tick, which only limits new claims per poll). Lower it to cut the box's aggregate request rate to Google and dodge captchas. Current effective value is 4.

Low end of the randomized upscale batch. Each claim draws a size between min and max (1-8). Set equal to max for a fixed batch. Current effective value is 4.

High end of the randomized upscale batch (must be ≥ min, 1-8). Current effective value is 4.

Min gap per account between job starts. Raise during big jobs to avoid captchas. Current effective value is 120s.

Min gap between job starts anywhere on the box (jittered ±10%), so the busy cap refills gradually instead of bursting from the shared IP. 0 disables it. Current effective value is 4s.

Pause between worker passes (VPN check, account sync, heartbeat, claim). Was a boot-time env value; now applied on the next heartbeat. Current effective value is 5s.

Hard cap on image jobs started per account in a rolling 24h window, enforced at claim time. Flow allows ~100/day, so ~95 trips ours before the provider benches the account. Current effective value is 200.

While an account sits on a captcha cooldown its tab performs this many read-only page actions (credits poll, page view, project reads) per hour, scattered at random through each hour, so the session never falls silent. 0 disables it. Current effective value is 5.

Eventual-success SLA stamped on jobs at enqueue; recoverable failures retry until it expires. Global only - a queued job has no worker yet, so this knob is hidden for per-worker overrides. Current value is 24h.

Bench applied on the first auth failure. Effective: 1m.

Backoff never climbs past this. Effective: 1m.

Backoff grows the bench with repeat failures up to the cap; constant re-benches the base every time.

Bench applied on the first captcha failure. Effective: 30m.

Backoff never climbs past this. Effective: 360m.

Backoff grows the bench with repeat failures up to the cap; constant re-benches the base every time.

Bench applied on the first rate limit / daily quota failure. Effective: 4m.

Backoff never climbs past this. Effective: 4m.

Backoff grows the bench with repeat failures up to the cap; constant re-benches the base every time.

Expected public egress IP for VPN health checks.

Wipes each account's cookies after every generation via the privileged relay userscript, resetting reCAPTCHA/device reputation. Needs the relay installed per account.

When full-key low-priority video may run on credit-spending lite instead. Auto switches once an account's low-priority renders average over 4 minutes, and lets accounts without low-priority access help while every low-priority account is slow. The low-priority-only API key never spends credits.