The best way to control Claude Code, Codex and more from any computer or phone
Mirrored from https://github.com/Camo67/t3code.git
Synced Nov 21, 03:37 UTC
| 1 | # Product usage data |
| 2 | |
| 3 | The T3 Code server sends product usage events to T3 Code's own endpoint at `ingest.t3.codes`, |
| 4 | associated with a hashed account or installation identifier. To count how many installations one person |
| 5 | uses, the server also sends hashed account identifiers: your T3 Connect account, your OpenAI and |
| 6 | Claude accounts when you are signed in, and a random identifier for each device that connects. The endpoint keeps a copy of each |
| 7 | event and forwards events to PostHog. Events include the provider, model, reasoning effort, |
| 8 | permission mode, turn and request results, duration, release channel, and token counts when |
| 9 | available. Child-agent token counts are reported separately from the main agent's. Model names |
| 10 | are sent only when they appear in a provider's public model list. |
| 11 | |
| 12 | Product events do not include prompts, responses, file contents, authentication tokens, conversation IDs, |
| 13 | raw provider events, or child-agent output. |
| 14 | |
| 15 | ## Relay connection diagnostics |
| 16 | |
| 17 | T3 Code sends relay connection traces to Axiom to diagnose T3 Connect connectivity. These are |
| 18 | separate from product events. Depending on the client version, traces can include connection |
| 19 | timings, environment identifiers and the connected machine's name. Failed spans can include error |
| 20 | messages and stack traces; error text can quote a value the app was handling. |
| 21 | |
| 22 | To disable product events and relay tracing from the server, set |
| 23 | `T3CODE_TELEMETRY_ENABLED=false` in its environment before starting it. Relay tracing also stops |
| 24 | when `T3CODE_OTEL_SDK_DISABLED` or `OTEL_SDK_DISABLED` turns OpenTelemetry export off. |
| 25 | |
| 26 | An administrator can turn product events and relay tracing off in the server and desktop app with |
| 27 | a [managed policy](./managed-policy.md#other-capabilities). This does not control traces sent by |
| 28 | separate browser or mobile clients. |
| 29 | |
| 30 | The desktop app reads `T3CODE_TELEMETRY_ENABLED` from your shell profile (for example `~/.zshrc`) on macOS and |
| 31 | Linux, so export it there and restart the app. On Windows, set it as a user environment variable. |
| 32 | |
| 33 | The web app in a browser, including one the `t3` CLI opens, does not read these environment |
| 34 | variables. When its build has relay tracing configured, it sends its own connection traces even |
| 35 | if the server has opted out. The browser app has no relay tracing toggle. |
| 36 | |
| 37 | ## Mobile app diagnostics |
| 38 | |
| 39 | When the iOS or Android app crashes or hits an error, it sends a report to T3 Code: the error |
| 40 | message, the stack trace, the app version, and the device model and OS version. Each launch also |
| 41 | sends startup timings, and every report carries a random ID for the install. Reports go through |
| 42 | the T3 Connect relay to Axiom. They do not include your threads, prompts, or connection details, |
| 43 | but an error message can quote a value the app was handling. |
| 44 | |
| 45 | To stop sending them, turn off **Send crash reports** in **Settings > About T3 Code > Diagnostics**. |
| 46 | |
| 47 | The mobile app also sends relay connection traces when its build has tracing configured. These |
| 48 | carry an identifier for the current app session. **Send crash reports** does not control these |
| 49 | traces, and the mobile app has no separate relay tracing toggle. Server environment variables and |
| 50 | managed policy do not disable mobile tracing. |
| 51 | |
| 52 | ## Agent activity for mobile notifications |
| 53 | |
| 54 | When **Publish agent activity** is enabled on a host, it sends project and thread titles, model |
| 55 | names, activity status, and environment and thread identifiers to the T3 Connect relay for |
| 56 | [mobile notifications and live activities](./mobile-notifications.md). This is separate from |
| 57 | product events and relay diagnostics. The telemetry opt-out does not disable it. |
| 58 | |
| 59 | To stop publishing, turn off **Publish agent activity** under **Settings > Sharing & access** on |
| 60 | the host. Turning off notifications on a phone controls that phone's alerts, not the host's |
| 61 | publishing setting. |
| 62 | |
| 63 | ## Export diagnostics to your own receiver |
| 64 | |
| 65 | To send traces, metrics, or logs to an OpenTelemetry receiver, open |
| 66 | **Settings > Maintenance > Diagnostics**, select an environment, and enter each signal's OTLP HTTP |
| 67 | endpoint under **OpenTelemetry export** (for example `http://localhost:4318/v1/traces`). Save, then |
| 68 | restart that environment's server. The receiver must be reachable from the server's machine. |
| 69 | **Test** sends an empty export from the server to check an endpoint before or after you save it; |
| 70 | saved endpoints are checked when the section opens. Checks send authentication headers only to |
| 71 | the signal's currently running endpoint and do not follow redirects. To check a new endpoint |
| 72 | that requires authentication, save it and restart the server first. |
| 73 | |
| 74 | `T3CODE_OTLP_*_URL` and standard `OTEL_EXPORTER_OTLP_*` environment variables override the saved |
| 75 | settings. An overridden signal shows **Set by environment** and names the variable that set it, and its |
| 76 | **Test** checks the running endpoint instead of the field. For endpoints saved here or set with `T3CODE_OTLP_*_URL`, set `T3CODE_OTLP_HEADERS` for |
| 77 | receivers that need authentication and `T3CODE_OTLP_PROTOCOL=http/protobuf` for receivers that do |
| 78 | not accept JSON. An endpoint set with `OTEL_EXPORTER_OTLP_*` takes its headers and protocol from |
| 79 | `OTEL_EXPORTER_OTLP_HEADERS` and `OTEL_EXPORTER_OTLP_PROTOCOL` instead. |