blodemd login

Authenticate with Blode.md using browser OAuth or an API key.

Authenticate your CLI session so you can deploy documentation with blodemd push.

blodemd login

Authentication modes

Browser OAuth (default)

When you run blodemd login, the CLI opens your browser to complete a Supabase OAuth flow using PKCE. After you authorize, the CLI receives an access token and stores it locally.

blodemd login

The CLI starts a temporary local server on port 8787 to receive the OAuth callback. If the browser does not open automatically, you can copy the printed URL manually.

API key

Use the --token flag to authenticate with a project-scoped API key instead of browser login. This is the recommended approach for CI/CD pipelines.

blodemd login --token

You will be prompted to paste your API key. The key is stored locally and never echoed to the terminal.

You can generate API keys from the Blode.md dashboard or when a project is auto-created during blodemd push.

Options

Field	Type	Description	Required	Default
`--token`	boolean	Paste an API key instead of using browser login.	Yes	false
`--port <port>`	number	Port for the local OAuth callback server.	Yes	8787
`--timeout <seconds>`	number	How long to wait for browser authorization before timing out.	Yes	180
`--no-open`	boolean	Print the authorization URL instead of opening the browser.	Yes	false

Examples

blodemd login

Credential storage

Credentials are stored at ~/.config/blodemd/credentials.json. OAuth sessions include a refresh token so the CLI can renew your session automatically. Run blodemd logout to remove stored credentials.

You can also skip blodemd login entirely by setting the BLODEMD_API_KEY environment variable.