jig formatted status

[dulaj-me]

Eg:

App:
  Name    : sprocket-test-dulaj ┃ ID: f1ae8348-7379-4c34-9004-6cd273d6d644
  Image   : registry.together.xyz/proj_csvnq3lka36nwbncbkkva/sprocket-test-dulaj:v0.0.3
  Status  : Ready
  Created : 2026-02-03 18:51:11 ┃ Updated : 2026-02-06 14:00:53

  Autoscaling: QueueBacklogPerWorker 1.05(target)

  Replicas:
    Min/Max         : 1/10
    Ready/Desired   : 1/1

Configuration:
  Port: 8000
  Command: []
  Args: []
  Health Check Path: /health
  Resources: 4.0 core CPU ┃ 32.0GB Memory ┃ 100GB Storage
  GPU: 1x h100-80gb

  Volumes:
    NAME                         MOUNT_PATH
    my-test-volume-2             /app/my-volume

  Secrets: ['TOGETHER_API_KEY']

  Environment Variables:
    NAME                                     VALUE
    TOGETHER_DEPLOYMENT_REVISION_ID          a6dccc34-ba86-46ba-a597-4605cbdfc551
    TOGETHER_API_BASE_URL                    https://api.together.xyz
    FOO                                      bar

Replica Events:
v0.0.4:
  5c589f4f76-2zm8k: Running, ready since 2026-02-09 17:53:37
v0.0.2:
  6974755b98-hdt4d: Terminated

---

Note

Medium Risk
Touches together beta jig deploy/status flows and error handling; changes are user-facing and could affect CLI output expectations and deployment creation behavior, but are limited in scope and don’t change auth or core SDK transport.

Overview
together beta jig status now defaults to a formatted, human-readable deployment report (with --json to keep raw output), implemented via a new format_deployment_status() helper.

Refactors jig commands to use a shared @jig_command decorator (adds -c/--config consistently and centralizes API error handling), and improves deploy-time errors by computing a config-specific “unique name” tip and surfacing it when the API reports name-collision issues.

Minor updates: README installation docs now use stable pip install together and add uv add together, fine-tuning price estimation now forwards from_checkpoint, and the generated OpenAPI spec pointer in .stats.yml is updated.

^{Written by Cursor Bugbot for commit 7aee2bd. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

Missing f-string prefix on tip string literals

Medium Severity

The tip assignments in the non-pyproject else branch are plain strings, not f-strings. "update \name` in {path}"and"rename your folder or add `name` to {path}"will include the literal text{path}instead of the actual file path. Compare with the pyproject branch which correctly hardcodes the path. This surfaces in the user-facing error message"Deployment name must be unique. Tip: ..."`.

 

[cursor]

Crash when API error body is None

Low Severity

getattr(e, "body", {}).get("error", "") will raise AttributeError if e.body is None. Since body is typed object | None on APIError, getattr returns None (the attribute exists), and calling .get() on None fails. This masks the original APIStatusError with a less informative generic error from the outer handle_api_errors handler.