ccwork 1.0.0 — run Claude Code workloads on a remote worker box

Each job is a full headless Claude session in its own git worktree, so many run in
parallel without colliding. One static binary is both the client and the worker.


INSTALL

    curl -fsSL https://ccwork.lab47.run.garden/install.sh | sh

Or grab a binary directly (no dependencies, nothing to unpack):

    https://ccwork.lab47.run.garden/latest/ccwork-linux-arm64
    https://ccwork.lab47.run.garden/latest/ccwork-linux-amd64
    https://ccwork.lab47.run.garden/latest/ccwork-darwin-arm64
    https://ccwork.lab47.run.garden/latest/ccwork-darwin-amd64

Pinned, immutable copies live under /v1.0.0/ with the same names.
Checksums: https://ccwork.lab47.run.garden/latest/SHA256SUMS


CONFIGURE

Point it at a gateway and give it a token. The token is a credential — it lets the
holder run jobs as the worker's user — so it is handed out separately, never here.

    export CCWORK_URL=https://chitchat.lab47.run.garden
    export CCWORK_TOKEN=<ask evan>

    ccwork doctor        # verifies gateway, token, worker, and git auth in turn


IF YOU ARE AN AI AGENT

Run this. It prints a complete, self-contained guide — how to submit jobs, fan work
out, observe it without flooding your context, and collect the results — along with
the worker's live status. You do not need any other documentation.

    ccwork agent-help


QUICK TASTE

    ccwork submit "add table-driven tests for the parser" \
      --repo git@github.com:org/app.git --wait

    ccwork batch sweep.jsonl --repo git@github.com:org/app.git   # fan out
    ccwork ls                                                    # what's running
    ccwork logs <job> -f --json                                  # resumable, gap-free
    ccwork result <job>

Jobs cost real money and run for minutes. `ccwork capacity` shows free slots before
you launch a large batch.