Together CLI 3.1.0 stops saving your API key on new jig deploys (November 3, 2026)

What changed

Together Python SDK 3.1.0 and Together CLI 3.1.0 are out. On new deployments, tg beta jig deploy no longer stores your API key as a TOGETHER_API_KEY secret. Existing deployments keep their secret. Sprocket 0.1.8 or later signs in with the deployment's service token instead.

Other changes:

• tg beta jig deploy works after tg login, so you don't need an API key for it.
• client.beta.jig.secrets.create and update take ttl_seconds (1 to 14 days), and secrets return expires_at. In the CLI, use --ttl on tg beta jig secrets set.
• tg beta jig no longer reads TOGETHER_DEBUG. Pass --debug instead.
• ModelResourcesClient.create takes inactive_timeout. Call extend_expiry to stop a resource from shutting down when idle.
• ModelResourcesClient.create takes ready_timeout, which replaces timeout. timeout still works but raises a FutureWarning.
• client.clusters.create and tg clusters create accept GB200_SXM as a GPU type.
• Line items from client.organization.usage.costs.list() include a typed applied_credit object.

Prerequisites

• A Together account, signed in with tg login. If your container code reads it, also have your key in TOGETHER_API_KEY.