smolgym

Where a run lives

Your code. Our GPUs.

The training data stays in your script. The weights stay on the GPUs until you download them.

01

In your script

You hold this

The loop runs on your machine. A laptop is enough. The script sends the batch. It does not hold W.

  1. 01

    Prompts and tasks

    The data, the traces, and the sandbox those tasks run in.

  2. 02

    Rewards

    An exact match, a unit test, a rubric, or a judge you call.

  3. 03

    The loss

    Supervised, reinforcement, preference, or a loss you write.

02

On the GPUs

Two copies of W

SmolGym loads the model and keeps both copies. The sampler reads one. The trainer writes the other.

  1. 01

    Sampler

    Reads the last synced weights. Does not train.

  2. 02

    Trainer

    Writes W when you call optim_step(). That is the only place W changes.

  3. 03

    Sync

    Copies the written weights onto the sampler, so the next sample() sees them.

  4. 04

    save_state()

    The checkpoint. Optimizer state stays, and the weights are yours to download.

03

On this website

No account

The site has no sign-in and no analytics, and it does not set cookies. The only personal data is an email you choose to send to swapnil@rycerz.es. That message is the request for a session.

What happens to that email is on the privacy page.