stn.
Get Started Free

Overview

Integrations connect read-only so that live ticket, PR, and CI status shows up next to the work it relates to in your context graph. You connect them once per team from the web dashboard; the CLI then reads the enriched data.

Connecting

Open Dashboard → Integrations (/dashboard/integrations/). You must be a team admin to connect or disconnect anything. Each provider has a one-click connect button per team:

  • GitHub — enrich PR/issue links and map GitHub identities to people.
  • Jira — pull projects and work items into the graph (other trackers surface via links/webhooks).
  • Slack — mirror block alerts to a channel, link ticket/PR mentions, and capture decisions via /stndp or a 📌 reaction.

Once connected, list what's wired up from the terminal:

stn integrations   # provider, display name, scope, and status of each connected integration

Status & lifecycle

Each integration shows a status: active, or expired (a token lapsed — reconnect from the dashboard). Re-connecting a provider is idempotent: it updates the existing connection in place and preserves settings like a Slack alert channel.

Security

Provider tokens are encrypted at rest and only decrypted in the background worker, never on the web request path. OAuth install flows use signed, expiring state and re-check that the caller is a team admin on the callback. See Security & privacy.