offloadlisted

# Offload: how a Claude session uses it Offload is a daemon on the owner's GPU box. It takes a job spec, clones the repository on the box, plans with Claude, executes step by step with a local model inside a sandbox (tests after every step), reviews with Claude, commits once, pushes a branch `offload/<job id>` to the repository it was given, and writes `REPORT.md`. The code never leaves the box. Only the report (a diff stat, the reviewer's notes, times, cost) comes back. One job runs at a time. A job that waits for the owner, a rate limit or the budget is parked and the next job runs. ## 0. Reach it The command is `offload`. On the box it is installed. On a laptop it is the SSH wrapper `bin/offload-remote` symlinked as `offload`; it reads the box's SSH name from `OFFLOAD_HOST` or from `~/.config/offload/host`. Every path in a spec is a path **on the box**. A spec file must be on the box too (`scp` it first). ```bash offload doctor # Docker, sandbox image, proxy, token, budget: all [ok] means ready offload status # every job, its state, cost, last event offload repo list # the repositories Offload may work on ``` If `doctor` is not ready, stop and tell the user what is missing. Do not try to fix the box. ## 1. Register the repository once ```bash offload repo add <path-or-url-reachable-from-the-box> "one line on what it is; tests are <command>" ``` `repo add` runs `git ls-remote` first and refuses a target the box cannot reach. Give the canonica