trajectory-sdk and import Client from trajectory.
Configuration
Resources
trajectory.lib provides two forms of the same spec upload workflow:
push() calls start_push() and waits with operation.result() internally. Both accept
the same arguments. start_push() is a regular Python function; background processing
happens on the server. See the spec guide.
To edit tasks within an existing spec version, use client.benchmarks.tasks.append(...)
followed by client.benchmarks.tasks.commit(...) with that version’s spec ID.
Training and evaluation
Both resources acceptcreate(agent_name=..., benchmark_name=..., base_model_slug=..., options=...)
to select the latest spec version under that agent. Pass bench_id instead of the name
pair to select a specific version. Finish a baseline/checkpoint comparison before publishing
another version under the same name.
Use parent_checkpoint_id to resume training or evaluate a checkpoint. Request
options dictionaries follow the shared RunOptionsParam type; run responses expose
typed RunOptions values. Omitted, null, and empty options preserve defaults.
client.training.list_options(...) or client.evals.list_options(...) with
bench_id and an optional base_model_slug to discover supported settings for that
mode. Each model has base_model_slug and an options map with types, bounds,
descriptions, and fixed or computed defaults. Training and evaluation may have
different bounds for the same setting.
Pagination
.items is the current page. Iterating the page fetches the rest.
.has_next_page() and .get_next_page() request the next page yourself.