Quickstart

uv tool install tuneplane
tp init my-lab --yes && cd my-lab
tp login --server https://tuneplane.your-company.com
tp new my-grpo --method nemo-rl/grpo
git add -A && git commit -m "first grpo run"
tp submit my-grpo --profile h200:8

​

Before you start

• An account on a TunePlane deployment, and its URL. An administrator creates it, or the deployment uses single sign-on.
• Quota, and at least one hardware profile you are allowed to use. tp status prints both after you log in. Every profile name on this site is an example — use the ones tp status gives you.
• The cluster must be able to reach Qwen/Qwen2.5-1.5B, which is what the scaffold trains. On an air-gapped network an administrator points the deployment at an internal mirror. Without one the job starts, stalls downloading weights, and times out. See air-gapped deployments.

1

Install the CLI and create a project

uv tool install tuneplane     # or: pip install tuneplane
tp init my-lab --yes
cd my-lab

tp init writes experiments/, configs/ and common/, plus a tuneplane.yaml marker that tells tp where your project root is. It also makes a git repository and one commit.Do not clone the platform repository. tp init is what creates your project. Upgrade later with tp update, not by reinstalling by hand.

2

Log in

tp login --server https://tuneplane.your-company.com

Opens a browser. On an SSH session add --device-flow. In CI pass --token. Credentials land in ~/.tuneplane/.

tp status

Prints your account, your quota, and the profile names this deployment has. Note one — the submit step needs it.

3

Create an experiment

tp new my-grpo --method nemo-rl/grpo

Writes experiments/my-grpo/ holding config.yaml, README.md and recipe.lock.json. The lock file pins the method version, so the run is reproducible even after the catalogue moves on.

tp methods                 # every method this deployment offers
tp methods nemo-rl/grpo    # what you can tune, with ranges and defaults

4

Tune and validate

Edit experiments/my-grpo/config.yaml. Learning rate, prompts per step and generations per prompt are at the top.

tp validate my-grpo

Checks types, ranges and batch-size divisibility against the method declaration. A typo fails here in seconds instead of after a queue wait.

5

Submit

git add -A && git commit -m "first grpo run"
tp submit my-grpo --profile h200:8

Prints a job id. --profile is the only resource flag: h200 takes the registry’s default shape, h200:4 asks for four GPUs, h200:16 for two full nodes.A dirty working tree is refused. Pass --allow-dirty to submit anyway.

tp job logs        # omit the id to follow the latest job

Status moves QUEUED → SUBMITTED → PENDING → RUNNING. QUEUED means admitted but not yet on the cluster. See job states.

6

Watch it in the console

Open the console, go to Jobs, and click your run.

Tab	What it shows
Charts	Loss, reward, KL, gradient norm, step by step
Logs	The full stream, searchable and downloadable
Validation	Sample conversations and reward histograms
System	GPU utilisation, memory, network
Diagnosis	On a failure or an odd curve, a report and the knobs worth trying

​

Check it worked

​

Next