Triss is maintained in the open — talk to us on GitHub.
There is no support desk or sales team behind Triss; the repository is the channel. Everything arrives in the public tracker atgithub.com/ayleen/triss-coworker/issues, where maintainers and contributors respond in the open.
Pick the right door.
Open a GitHub issue with the command you ran, the version (triss status prints it), and what you expected. Never paste credentials or provider keys.
Do not open a public issue. Follow SECURITY.md — it describes the coordinated disclosure path, including how to request a private contact channel when one is needed.
Pull requests are welcome under the Developer Certificate of Origin. Read CONTRIBUTING.md first: behavior changes ship with tests, and npm run check must pass.
Start with the documentation and the command reference; triss agent-help prints the full delegation cookbook locally. If the docs are wrong or unclear, that is a bug — file it.
Response times are best-effort: this is an open-source project maintained by volunteers, not a commercial SLA. For security reports, the disclosure policy in SECURITY.md applies.