@scrydon/cli

The Scrydon developer CLI. Authenticate against a Scrydon installation and point your tools at it.

bunx @scrydon/cli login https://app.example.com

or install it so the scrydon command is on your PATH:

bun add -g @scrydon/cli
scrydon login https://app.example.com

Commands

| Command | What it does | | --- | --- | | scrydon login <url> | Device-flow (RFC 8628) login; stores a token in ~/.scrydon/credentials.json (mode 0600) | | scrydon logout [url] | Forget stored credentials — one installation, or all of them | | scrydon whoami | List installations this machine holds credentials for |

In CI, set SCRYDON_API_KEY instead of logging in. It takes precedence over every stored credential, which whoami will tell you.

Why this package is separate from @scrydon/sdk-authoring

They serve different people. Authoring packs and integrations is a specialist task; logging in is something every developer does. @scrydon/sdk-authoring is 32 MB across 21 packages installed (it bundles esbuild); this package is 52 KB in 1 package with zero runtime dependencies.

So the dependency points heavy → thin: @scrydon/sdk-authoring consumes the auth kernel from @scrydon/cli/auth, never the reverse. Keep it that way — a runtime dependency added here is paid by every developer who only wanted to log in.

@scrydon/cli/auth

The device-flow and credential-store kernel, exported for @scrydon/sdk-authoring so there is exactly one implementation of each in the fleet.

import { deviceLogin, loadCredentials } from "@scrydon/cli/auth";