- Dashboard: a “View in W&B” button on the job page.
- API / SDK: the
wandb_run_urlfield on the training job object.
Connect your account
Grab an API key from wandb.ai/authorize, then connect it one of three ways:- CLI
- Dashboard
- SDK
What gets logged
Once connected, managed LLM training jobs (grpo, sft_text, dpo) report to W&B automatically:
- Project: your configured default, or
veri-trainingif you didn’t set one. - Run name: the job’s
output_name. - Run ID: the Veri job ID, so runs and jobs correlate one-to-one.
- Metrics: everything the trainer emits per step (loss, reward, grad norm, learning rate, tokens/s).
Custom scripts
For custom-script jobs, Veri injectsWANDB_API_KEY, WANDB_PROJECT, and WANDB_RUN_ID into your container’s environment. A bare wandb.init(), or any framework with W&B support (verl, OpenRLHF, slime, TRL), lands in your account with no code change. Your script’s own env values take precedence if you set the same variables yourself.
After the run, Veri scans the script output for the W&B run link and attaches it to the job as wandb_run_url, same as managed jobs.
How your key is handled
- Stored encrypted at rest, scoped to your account. The API never returns it.
- Delivered to the training machine at runtime over a job-scoped authenticated channel; it is never written into job config files or logs.
veri wandb removedisconnects immediately: jobs submitted afterwards no longer receive the key.

