Triss sits between an agent, your filesystem, and your credentials.
This page is the short version for a vendor security review. SECURITY.md is the normative document.
Four answers before the details.
Selected code and task context may be sent to the model provider you selected, when you invoke a model-backed command. Repository content can leave your machine — this is not a "never leaves your machine" product.
The local CLI has no developer telemetry. The one automatic network path is a credential-free passive update check, which you can disable.
No. A Git worktree separates delegated changes from your checkout; it is not confinement of the host filesystem, and it does not block absolute-path or same-UID access.
No. A completed process is not acceptance. Inspect the changes and run the project's checks yourself before using the result.
Once context reaches an external provider, its retention, training, residency, and access policies apply — Triss does not control external provider policy. Review yours before sending confidential code. The complete per-command table lives in docs/data-flows.md.
Three default destinations — plus any URL you ask Triss to fetch.
Prompts and the selected context go to the resolved endpoint of your selected canonical provider. Triss uses the transport required by that provider/model route.
Tracker commands talk to the Jira/Linear/GitHub instance you configured — only when a credential exists.
A credential-free GET to a fixed public Release endpoint when the cache is due.
