← ClaudeAtlas

flowleap-authlisted

Authenticate the FlowLeap CLI — OAuth 2.0 device flow login (user code + verification URL), long-lived fl_pat_ personal API tokens for headless agents, status checks, and targeted logout. Trigger when a FlowLeap command fails with 401/unauthenticated, when setting up credentials for an agent or CI, or when the user asks to log in to FlowLeap or mint, list, or revoke API tokens.
flowleap-ai/flowleap-plugins · ★ 0 · API & Backend · score 68
Install: claude install-skill flowleap-ai/flowleap-plugins
# FlowLeap Auth Global flags and configuration: see `flowleap-shared`. ## Commands ### Login via OAuth device flow ```bash flowleap auth login ``` Starts the OAuth 2.0 device flow: the CLI requests a device code from the backend, prints a user code plus verification URL (and opens the browser), then polls until the login is approved. The resulting session JWT is stored in `~/.config/flowleap/credentials.toml` (mode 0600). No local callback server is involved, so it also works when the browser runs on another machine — open the printed URL and enter the user code there. When stdout is not a TTY, the browser auto-open and spinner are suppressed automatically. ### Structured login for agents (--json) ```bash flowleap --json auth login ``` With `--json`, `auth login` becomes a blocking process that speaks NDJSON on stdout — one compact JSON object per line, nothing else. It emits the device-authorization event immediately, then polls until the human approves and emits exactly one terminal event before exiting: ```json {"event":"device_authorization","verification_uri":"https://flowleap.co/device","verification_uri_complete":"https://flowleap.co/device?code=ABCD-1234","user_code":"ABCD-1234","expires_in":900,"interval":5} {"event":"authorized","stored":true} ``` Terminal events: `authorized` (exit 0 — the session token is stored, same as the human flow) or `failed` with an `error` description (nonzero exit per the standard exit-code table — denied, expired, or another er