Get started

You can use the Together CLI to manage your Together AI resources from your terminal, or using automated systems. Use the Together CLI to deploy endpoints, fine-tune models, manage your GPU clusters, and more.

Install the Together CLI

Requires Python 3.10+ and uv.

Run the following command to install the CLI:

# Install
uv tool install "together[cli]"

# Upgrade
uv tool install "together[cli]" --upgrade

# List commands
tg --help

The [cli] extra target includes additional dependencies used by the CLI. The extra target prevents the Python SDK from being bloated with dependencies it does not use.

The CLI is also installed as together, an alias of tg that’s identical in behavior. Examples throughout these docs use tg.

Migrating from a pip-installed CLI? An earlier pip install together can pin the CLI to an older Python interpreter and leave a stale tg binary earlier on your PATH, which shadows the uv-managed install. Commands that need a newer CLI (such as OIDC SSH into clusters, which requires 2.40+) then fail even after you upgrade. To switch to the uv-managed install:

Uninstall the pip package: pip uninstall together.
Reload your shell (or run hash -r) so PATH resolves to the uv-managed binary.
Reinstall: uv tool install "together[cli]".
Confirm the version: tg --version.

Upgrade notices

The CLI checks PyPI in the background for a newer release and caches the result for 24 hours. When one is available, it prints an upgrade notice at most once per day. In an interactive terminal it also offers to run the upgrade for you, using the command that matches your install (uv, pipx, or pip). With --json or --non-interactive, it prints the upgrade command instead. To disable the check entirely (for example, in CI), set:

Shell

export TOGETHER_DISABLE_VERSION_CHECK=1

Authenticate

tg login

The CLI opens a browser window where you approve the login, then scopes the CLI to one of your projects. To work in a different project, run tg switch.

Authenticate with an API key

For CI/CD, scripts, and other environments where you can’t log in with a browser, authenticate with an API key instead. Find your API key in your account settings, then set it as an environment variable:

Shell

export TOGETHER_API_KEY=<your_key>

While you’re logged in with tg login, the CLI uses your login instead of TOGETHER_API_KEY. To use the API key, pass --api-key or run tg logout.

Use the CLI in a CI/CD environment

uvx is a helper utility from uv that downloads and runs a Python binary without a separate install step. In a CI/CD environment, invoke the CLI directly with uvx:

uvx "together[cli]" COMMAND [ARGS]...

In CI/CD, set TOGETHER_API_KEY instead of passing --api-key so the key doesn’t appear in process lists or logs. If both are provided, --api-key takes precedence over the environment variable.

Available commands

tg login
tg switch [PROJECT_ID]
tg logout

Learn more about the login commands.

`models`

Manage the models you deploy with dedicated model inference. Browse supported models, or register your own models and adapters and upload their weights.

tg models public
tg models create
tg models upload

Learn more about the models command.

`endpoints`

Deploy models to dedicated endpoints, then manage each endpoint’s deployments, traffic, and rollouts.

tg endpoints deploy
tg endpoints ls
tg endpoints update

Learn more about the endpoints command.

`files`

Upload and manage datasets for use in fine-tuning, evals, and batch inference.

tg files check ./dataset.jsonl
tg files upload ./eval-data.jsonl --purpose eval
tg files list

Learn more about the files command.

`fine-tuning`

Create and manage fine-tuning jobs, then download the model weights they produce.

tg fine-tuning create
tg fine-tuning model-limits
tg fine-tuning list-checkpoints
tg fine-tuning download

# Shorthand alias
tg ft create

Learn more about the fine-tuning command.

`evals`

Manage model evaluation jobs.

tg evals create 
tg evals status [EVAL_ID]

Learn more about the evals command.

`batches`

Submit and manage batch inference jobs.

tg batches submit ./requests.jsonl chat.completions
tg batches ls
tg batches get [BATCH_ID]
tg batches download [BATCH_ID] --output ./out
tg batches cancel [BATCH_ID]

Learn more about the batches command.

`clusters`

Reserve, manage, and interact with GPU clusters.

tg clusters create
tg clusters get-credentials [CLUSTER_ID]
tg clusters list-regions

Learn more about the clusters command.

`jig` (beta)

Build, deploy, and manage dedicated containers.

tg beta jig init
tg beta jig deploy
tg beta jig secrets set HF_TOKEN $HF_TOKEN

Learn more about the jig command.

`projects`

List the projects your current credentials can access.

tg projects ls

Learn more about the projects command.

`whoami`

Show the project and organization your current credentials belong to.

tg whoami

Learn more about the whoami command.

Beta commands

The beta namespace provides access to experimental features and new capabilities before they become part of the standard API. Features in the beta namespace are largely considered stable. However, these features are subject to change and may be modified or removed in future releases.

Command aliases

Several commands and subcommands have shorthand aliases:

Alias	Full command	Available on
`ft`	`fine-tuning`	`tg ft …` (e.g. `tg ft create`, `tg ft ls`)
`ls`	`list`	`tg files ls`, `tg fine-tuning ls`, `tg models ls`, `tg endpoints ls`, `tg projects ls`, `tg evals ls`, `tg batches ls`, `tg clusters ls`, `tg clusters storage ls`, `tg beta jig ls`, `tg beta jig secrets ls`, `tg beta jig volumes ls`
`-c`	`create`	`tg fine-tuning -c`, `tg models -c`, `tg evals -c`, `tg clusters -c`, `tg clusters storage -c`
`-d`	`rm`	`tg models -d`, `tg endpoints -d`
`-d`	`delete`	`tg files -d`, `tg fine-tuning -d`, `tg clusters -d`, `tg clusters storage -d`, `tg beta jig secrets -d`, `tg beta jig volumes -d`

Global parameters

The following parameters are available on every command:

Flag	Description
`--help`	Print help for the prefixed command.
`--json`	Return the response as JSON. Useful for scripting.
`--non-interactive`	Disable interactive prompts and manual input.
`--api-key [string]`	Your Together API key. When omitted, the CLI uses your `tg login` session, then the `TOGETHER_API_KEY` environment variable.
`--project [string]`	Together project ID for project-scoped commands. Falls back to the `TOGETHER_PROJECT_ID` environment variable, then to your `tg login` project. With an API key, read-only commands use the project associated with the key. Mutating commands may prompt for confirmation or require an explicit project in `--json` or `--non-interactive` mode.
`--timeout [number]`	Request timeout, in seconds.
`--max-retries [number]`	Maximum number of HTTP retries.
`--version`	Print the CLI version.
`--debug`	Enable debug logging.

TOGETHER CLI

COMMANDS

Install the Together CLI

Upgrade notices

Authenticate

Authenticate with an API key

Use the CLI in a CI/CD environment

Available commands

`models`

`endpoints`

`files`

`fine-tuning`

`evals`

`batches`

`clusters`

`jig` (beta)

`projects`

`whoami`

Beta commands

Command aliases

Global parameters

​Install the Together CLI

​Upgrade notices

​Authenticate

​Authenticate with an API key

​Use the CLI in a CI/CD environment

​Available commands

​login, switch, and logout

​models

​endpoints

​files

​fine-tuning

​evals

​batches

​clusters

​jig (beta)

​projects

​whoami

​Beta commands

​Command aliases

​Global parameters

Install the Together CLI

Upgrade notices

Authenticate

Authenticate with an API key

Use the CLI in a CI/CD environment

Available commands

`login`, `switch`, and `logout`

`models`

`endpoints`

`files`

`fine-tuning`

`evals`

`batches`

`clusters`

`jig` (beta)

`projects`

`whoami`

Beta commands

Command aliases

Global parameters