Triss mascottrisscoworker
GitHub ↗
integrations

Project context, on explicit terms.

Read project context and perform explicit operations with GitHub, GitLab, Jira, Linear, and Confluence through Triss. Read context when you need it. Make external changes only through explicit operations.

01 — two design rules

Reads get summarised. Writes stay literal.

read --question
The model reads the API response, not your agent

Every read command accepts --question. Instead of dumping raw JSON, Triss runs it through the selected provider and returns a focused answer you can inspect against the source.

create · update · post · apply
No model anywhere near a mutation

Write commands make the HTTP call directly. The model is never asked to invent a request body. Creating, updating, or commenting is an explicit operation you or your host agent decide to run — not an automatic ticket-to-code loop.

02 — setup and readiness

Five services, one readiness check.

Each service is configured independently. Run the setup once, then confirm with triss status — it shows which integrations are ready and where each credential was read from.

Scope and token details live in each setup guide — follow the links above rather than guessing token scopes at creation time.

03 — per service