Authentication

The CLI needs a token whenever it touches the hosted side: provisioning ephemeral DBs, reading or writing the seed cache, serving mock APIs. Local-only work (seedkit preview, seedkit seed --url ... against your own DB) doesn't need a token.

Interactive login

seedkit login

Opens a browser to authenticate against your seedkit account. The token is stored in ~/.seedkit/credentials with mode 0600. You won't be asked to log in again on this machine.

Programmatic / CI

Set the SEEDKIT_TOKEN environment variable. The CLI prefers env-var tokens over the credentials file when both are present.

export SEEDKIT_TOKEN=skk_live_...
seedkit seed --seed my-fixture --from-cache

In GitHub Actions:

- name: Seed
  run: npx seedkit-cli seed --seed my-fixture --from-cache
  env:
    SEEDKIT_TOKEN: ${{ secrets.SEEDKIT_TOKEN }}

Getting a token

Create one in the dashboard at app.seedkit.dev/tokens. Tokens are scoped to your org and revocable individually. Token actions are audit-logged.

Logout

seedkit logout

Removes the credentials file. CI runs that read SEEDKIT_TOKEN from env are unaffected.