Skip to main content
One command does all of it: create the project, validate configs locally, pack and submit jobs, follow logs, and manage datasets, volumes, models, plugins and environments. The entry point installs under both names, tuneplane and tp. Every page here writes tp.
Every flag table on these pages is generated from the CLI itself by scripts/gen_cli_docs.py, and CI fails if it drifts. What you read here is what tp --help prints.

Set up

Experiments

Train

Artifacts and evaluation

Resources

Administration

Conventions

  • -h / --help works everywhere. tp job logs --help is faster than finding the page.
  • The project root is found by tuneplane.yaml. Run commands from anywhere inside the project.
  • State lives in ~/.tuneplane/ — the access token and the server address. Nothing else.
  • tp job logs defaults to your most recent job. The other job commands take an id.
  • References are <owner>/<name>, with @version where versions exist: alice/gsm8k-zh@v2. A Volume is the exception and never carries a version.

Shell completion

Installs completion for your current shell. --show-completion prints the script instead, if you would rather place it yourself.