together command-line tool. It is separate from the Python SDK’s behavior unless you invoke the CLI.
How to opt out
Telemetry tracking can be opted out via an environment variableTOGETHER_TELEMETRY_DISABLED or via together telemetry disable which saves a local configuration file on disk.
| Command | What it does |
|---|---|
telemetry status | Prints whether telemetry is enabled or disabled (and notes when the environment variable below is forcing it off). |
telemetry disable | Disables telemetry via updates the config file. |
telemetry enable | Enables telemetry via updates to the config file. |
- macOS / Linux:
$XDG_CONFIG_HOME/together/cli.jsonifXDG_CONFIG_HOMEis set, otherwise~/.config/together/cli.json. - Windows:
%APPDATA%\Together\cli.json.
The same file also stores a generated UUID as a stable, pseudonymous device identifier. An example of the config file may look like this:
What is tracked?
The following below is a list of the type of data we collect for all events:timestamp | Millisecond timestamp when the event was built. |
session_id | Identifier for this CLI process (stable for the lifetime of the process). |
device_id | Stable pseudonymous ID: a UUID stored in cli.json when first needed. We do not use any host hardware fingerprinting for this. |
metadata | Various runtime metadata such as the together CLI version, operating system, and CPU architecture. |
is_ci | true if the CI environment variable is set. |
agent_detection | From detect_agent - we track if the command was invoked by an agent and which known agent. |
command | The name of the command invoked, for example clusters create |
arg_names | The name of any cli args passed in. We do not collect the values. For example, if you do --secret FOOBAR, we will record that a command was invoked with an argument secret, and we will not record the value FOOBAR. |