Skip to main content

Create

To start a new fine-tuning job:
You must provide either --model (to start from a base model) or --from-checkpoint (to resume from a previous job). Before the job is submitted, the CLI prints an estimated price and asks for confirmation. Pass --confirm (or -y) to skip the prompt in scripts and CI.
If --training-file (or --validation-file) is a local path, the CLI uploads the file to the Files API automatically before kicking off the job.

Parameters

Weights & Biases

LoRA

Preference fine-tuning (DPO, RPO, SimPO)

The id field in the JSON response contains the fine-tune job ID (ft-…) that you use to retrieve status, list events, cancel the job, and download weights.

List

To list past and running fine-tune jobs:
Jobs are listed newest first.

Retrieve

To retrieve metadata for a job, including its current status:
Completed jobs also include Together model registry IDs and human-readable object names for the final weights:

List events

To list events of a past or running job:

Cancel

To cancel a running job:

Preview

To preview how a training file will be tokenized before you start a job:
The command samples rows from your uploaded JSONL training file and shows how the base model’s tokenizer and chat template tokenize them, including which tokens contribute to training loss.
The default table output prints the detected Dataset format, Max sequence, and Train inputs settings, then a Preview Rows table with these columns: Pass --json to print the full API response instead of the table.

Parameters

List checkpoints

To list saved checkpoints of a job:
The default output is a table with Download ID, Timestamp, Registry Artifact, and Type columns. Use the Download ID with tg fine-tuning download: intermediate checkpoints use FT_ID:STEP, and the final checkpoint uses the job ID alone. When the job uploaded the artifact to the Together model registry, the Registry Artifact column shows object_name when available (for example, acme-corp/my-model-abc123-100). It falls back to object_id@object_revision_id (for example, ml_…@rv_…) when the name is unavailable. The CLI also prints a copyable Registry artifacts block below the table. Pass --json to get the full response body instead. Each checkpoint includes step, path, created_at, checkpoint_type, and checkpoint (the download selector: model or adapter). When the job uploaded the artifact to the Together model registry, the entry also includes object_id, object_revision_id (for example, ml_… and rv_…), and object_name (the qualified <project_slug>/<model_name> name for that checkpoint, with -<step> or -adapter suffixes as appropriate). See Model registry object IDs for how these relate to the job-level model_object_id / adapter_object_id fields.

Download model weights

To download the weights of a fine-tuned model, run:
The command downloads Zstandard-compressed (.zst) weights. To extract them, run tar -xf filename.

Parameters

Delete

To delete a fine-tuning job:

Parameters