Signing in

stechbd auth login prints a short code and opens the panel. You approve the code from a page you are already signed in to. The machine then receives a token scoped to the deploy loop, which is narrower than your own permissions. You can choose a broader scope on the approval screen.

For CI, where nobody can approve a code:

stechbd auth login --token "$STECHBD_TOKEN"

Tokens are created under Settings → API tokens, or with stechbd token create, and revoked in either place. stechbd auth logout forgets the local copy and deliberately does not revoke the token, so signing out on a laptop cannot break a pipeline.

Self-hosting: point the CLI at your own panel with --panel:

stechbd auth login --panel https://panel.example.com

The CLI asks the panel what it can do before it runs anything, so an older installation refuses a command it cannot serve instead of failing halfway through.