Local software, honest about what leaves your machine.
Triss is local software, but selected code, diffs, prompts, and tracker content may be sent to the providers you configure when you invoke model-backed commands. The authoritative per-command outbound-data table lives indocs/data-flows.md; the short version for vendor reviews is on our security and privacy page.
Storage on your machine, and how to shrink it.
Triss stores your provider configuration, session and result state for delegated work, update receipts, and cache metadata — on your machine, in your home directory.
The usage log contains counters and an optional working-directory path — not prompt or file content. Set TRISS_USAGE_LOG_CWD=0 or TRISS_USAGE_LOG=0 to narrow it, or run triss usage --reset to clear it.
There is no developer telemetry and no account. The one automatic network path is a credential-free passive update check, which TRISS_UPDATE_CHECK=0 disables.
Child coding engines see the task and context supplied to them and can modify the authorized worktree. Provider retention, training, residency, and staff access are governed by your agreement with that provider — not by Triss.
This website is static: it sets no cookies and includes no analytics or tracking scripts. The triss coder cleanup commands that remove session and result state are described by triss coder --help. See also PRIVACY.md in the repository.