I'm siGit, running on siGit Code & Deploy platform, browsing siGit Code coding agent repo.
main
| 1 | # Telemetry |
| 2 | |
| 3 | siGit Code itself collects no usage analytics. On-device models run on |
| 4 | [Onde Inference](https://ondeinference.com), and Onde can report model timing to its own |
| 5 | dashboard. That reporting only switches on in builds where Onde's credentials were embedded at |
| 6 | compile time. When it is on, siGit Code sends: |
| 7 | |
| 8 | - one event when an on-device model finishes loading: the model's Hugging Face repo ID, its |
| 9 | display name, and how long the load took; |
| 10 | - one event per on-device response: the model ID, a per-process request ID, the response time, |
| 11 | the time to first token when it was measured, and whether it succeeded, errored, or was |
| 12 | cancelled. |
| 13 | |
| 14 | Nothing from your conversation goes with them: no prompts, responses, file paths, or code. |
| 15 | siGit Code doesn't set a machine identifier, so every install reports as the same |
| 16 | `onde-unknown` edge, and it sends no location. Models you run through siGit Code Cloud or your |
| 17 | own endpoint send no Onde events. |
| 18 | |
| 19 | To see whether your build reports, load an on-device model and check the log for |
| 20 | `ChatEngine: pulse telemetry enabled` or `ChatEngine: pulse telemetry disabled`. siGit Code logs |
| 21 | to stderr, which an editor shows in its agent log. Terminal mode writes it to |
| 22 | `$TMPDIR/sigit.log`. |
| 23 | |
| 24 | To turn it off, set `ONDE_DISABLE_PULSE=1` in the environment siGit Code runs in. For an |
| 25 | editor, put it in the agent's `env` block: |
| 26 | |
| 27 | ```json |
| 28 | "env": { "ONDE_DISABLE_PULSE": "1" } |
| 29 | ``` |