Skip to main content
Telescope uses a flat, Pydantic-validated configuration schema. Every field name is globally unique and self-descriptive. Typos in YAML keys are caught at load time (extra="forbid").

Config loading

Configuration is resolved by merging three layers:
  1. Defaultsconfigs/defaults/default_train.yaml (ships with Telescope)
  2. Run config — your YAML file passed via --config
  3. CLI overrides — individual flags like --learning_rate 5e-7
Later layers override earlier ones. You only need to specify the fields you want to change.

Summary

The most commonly configured parameters for a training run:
For the full list of parameters, see the sections below.

General

Model

Environments

At least one environment must be configured. Each entry is an object with these fields:

Workers

Orchestrator

Trainer

Algorithm

use_tis=true + use_ppo_clip=true + ppo_clip_ref_logprobs="rollout" is invalid — it double-counts the importance sampling correction. Use ppo_clip_ref_logprobs: "batch" instead.

Rollout / Sampling

Sequence Packing

Inference Server

Checkpointing

See Checkpointing for detailed usage.

Evals

See Evals for detailed usage. Each eval entry supports:

Logging

Ray Cluster

Weight Broadcasting

Megatron

These settings are ignored when train_backend: "fsdp". Only relevant when train_backend: "megatron".

vLLM Tracing