feat(cli): Add Analytic tracking to CLI commands

[blainekasten]

This adds analytics to the CLI. Here is an example of logs going through via the --debug flag:

(together) ➜  sites together --debug beta jig list   
[2026-03-19 15:31:48 - together:45 - DEBUG] args="{'command': 'jig list', 'arguments': {}}" event_name=cli_command_started message='Analytics event sending'
[2026-03-19 15:31:48 - together._base_client:484 - DEBUG] Request options: {'method': 'get', 'url': '/deployments', 'headers': {'X-Stainless-Raw-Response': 'raw'}}
[2026-03-19 15:31:48 - together._base_client:999 - DEBUG] Sending HTTP Request: GET https://api.together.xyz/v1/deployments
[2026-03-19 15:31:48 - together:45 - DEBUG] args="{'url': 'https://api.together.xyz/v1/deployments', 'method': 'GET', 'body': ''}" event_name=cli_command_api_request message='Analytics event sending'
[2026-03-19 15:31:48 - httpx:1025 - INFO] HTTP Request: POST https://api.together.ai/together/gateway/pub/v1/httpRequest "HTTP/1.1 200 OK"
[2026-03-19 15:31:48 - httpx:1025 - INFO] HTTP Request: POST https://api.together.ai/together/gateway/pub/v1/httpRequest "HTTP/1.1 200 OK"
[2026-03-19 15:31:48 - httpx:1025 - INFO] HTTP Request: GET https://api.together.xyz/v1/deployments "HTTP/1.1 200 OK"
[2026-03-19 15:31:48 - together._base_client:1037 - DEBUG] HTTP Response: GET https://api.together.xyz/v1/deployments "200 OK" Headers({'date': 'Thu, 19 Mar 2026 20:31:48 GMT', 'content-type': 'application/json; charset=utf-8', 'transfer-encoding': 'chunked', 'connection': 'keep-alive', 'content-encoding': 'gzip', 'x-trace-id': '20e67c94-8196-44a3-ad5b-5f30811b215d', 'cf-cache-status': 'DYNAMIC', 'strict-transport-security': 'max-age=15552000; includeSubDomains', 'server': 'cloudflare', 'cf-ray': '9def3e286c8da1e5-MSP', 'alt-svc': 'h3=":443"; ma=86400'})
[2026-03-19 15:31:48 - together:45 - DEBUG] args="{'command': 'jig list', 'arguments': {}}" event_name=cli_commmand_completed message='Analytics event sending'
[2026-03-19 15:31:49 - httpx:1025 - INFO] HTTP Request: POST https://api.together.ai/together/gateway/pub/v1/httpRequest "HTTP/1.1 200 OK"

Notably see the lines with event_name in them.

We are currently sending the following events:

1. cli_command_started for every command start
2. cli_command_user_aborted if the user aborts the command before it finishes
3. cli_command_failed if the command fails with any other exception
4. cli_commmand_completed for successful completions
5. cli_command_api_request for any api request that is fired within the command

Users can opt out with:

TOGETHER_TELEMETRY_DISABLED=1 or together telemetry disable

together telemetry has the following help output:

Usage: together telemetry [OPTIONS] COMMAND [ARGS]...

  Together collects usage data by default and can be controlled with this
  command, or by setting TOGETHER_TELEMETRY_DISABLED=1

Options:
  --help  Show this message and exit.

Commands:
  disable  Explicitly Disable telemetry
  enable   Enable telemetry
  status   Check to see if telemetry is enabled or disabled.

[zainhas]

should we cache the id in the config file?

if "device_id" in config:
    _cached_device_id = cast(str, config["device_id"])
    return _cached_device_id

[zainhas]

should this be:

@handle_api_errors("Clusters Storage")
@auto_track_command

[zainhas]

ooh good find here - this sends full pre-signed URLs:

commands like files upload/multipart uploads in src/together/lib/resources/files.py. Those URLs include bucket/object paths and temporary query credentials (for example X-Amz-* signatures), and custom --base-url values would leak internal hostnames as well.

[zainhas]

only records failures for Exception, but several decorated commands still abort with sys.exit(1) on common validation paths (for example files upload, files check, endpoints create, and endpoints update). Because sys.exit() raises SystemExit, these error cases skip both CommandFailed and CommandCompleted, so telemetry will show commands that merely “started” with no outcome.